Re: Severity 01

  • From: Madhu Sreeram <madhusreeram@xxxxxxxxx>
  • To: ozgur.ozdemircili@xxxxxxxxx
  • Date: Sat, 29 May 2010 11:23:39 -0500

On Fri, May 28, 2010 at 6:06 PM, Ozgur Ozdemircili <
ozgur.ozdemircili@xxxxxxxxx> wrote:

> Hi,
>
> Well not good news. It seems one of our tables got corrupted, causing all
> RAC instances restart.We have opened a Severity 1 SR and waiting.
>
> Please share your experiences on this:
>
> -Service provider talks about a table getting corrupted and says that it
> causing the problem?Is it even possible ?
>
> -How long does it take normally the Oracle technics to respond ?
>
>
>
> Özgür Özdemircili
> http://www.acikkod.org
> Code so clean you could eat off it
>

It's possible. It's usually for logical corruptions, where SMON is trying to
apply some recover and freaks out, crashing the instance. But you should see
a ora-00600 or ora-7445 in the alert.log, it just can't happen silently.
We recently encountered the error ORA-600 [kddummy_blkchk], that caused
instance crashes. Initially it seemed ok (happened about midnight), just one
crash in two-three hours during batch loads, but as the morning work load
started, the crash was almost every couple of minutes. This was on a 3node
RAC. We did have a sev1 SR, but the support was disappointing. We put the
tablespace in offline mode to get stability.We have someone responding, but
so far none of their suggestions has worked. It's been about 3weeks , it's
still unresolved. Still waiting on a patch.

On a side note, if you use the "allocate extent",  consider  applying the
patch#6647480 or you could potentially cause corruptions.


-Madhu Sreeram.

Other related posts: