Re: ORA-00600, What is it?

In <32861E30.22D0_at_kmv.msk.ru> max <max_at_kmv.msk.ru> writes:
>We've been having problems with ORA-00600 (internal error code).

ORA 600 errors are "internal errors" that are basically Oracle trapping "should never happen" or "had better not happen" errors. There's also a class of errors where it's "better not to proceed" to avoid database corruption. I forget if these are reported as ORA 600 or ORA 603.

>System is ALR REVOLUTION Q-SMP with 2 Pentium 90 and 128 MB
>SCO Unix 3.0 & ORACLE 7.1.3
 

>Sometimes, our database is crashed. Here is piece of logs:
 

> PMON LOG:
> *** SESSION ID:(1.1)
> error 471 detected in background process
> OPIRIP: Uncaught error 447. Error stack:
> ORA-00447: fatal error in background process
> ORA-00471: DBWR process terminated with error

Okay. The problem is in DBWR.

> DBWR LOG:
> Cursor Dump:
> End of cursor dump
> ksedmp: no current context area
> error 600 detected in background process
> OPIRIP: Uncaught error 447. Error stack:
> ORA-00447: fatal error in background process
> ORA-00600: internal error code, arguments: [512], [], [], [], [], [],
>[], []

And this is the key error> 512 is the error number. There are no parameters associated with internal error 512.

Oracle Support can for sure tell you what a Ora-600[512] error is, were there an clues in the dbwr.trc file as to what was happening in the database prior to this?

Andy

-- 
Andrew Finkenstadt, The Printing House Ltd, Also a GEnie Sysop

"By the time they had diminished from 50 to 8, the other dwarves began
to suspect 'Hungry' ..."                -- Gary Larson, "The Far Side"