Hello,
First of all, let me explain what the difference between ora-7445 and ora-600:
We know ora-600 is oracle internal errors. ora-7445 is internal error, too.
But ora-600 is catched by Oracle server. If Oracle server can not catch its
internal errors, OS may catch and returns exception sign
Here are the error messages:
ORA-07445: exception encountered: core dump [11] [0] [0] [0] [] []
Mon Jul 2 08:03:19 2001
Thread 1 advanced to log sequence 304
Current log# 8 seq# 304 mem# 0: /u035/oradata/prod/redo08.log
Mon Jul 2 13:55:26 2001
Thread 1 advanced to log sequence 305
Current lo
Hello,
What was the first parameter of ora-600 ? We should unserstand if your ora-600
are cause or consequence. if it's consequence( I guess it's in your case),
ignore it.
24/7/01 06:10:53, "Lord, David - C&S" <[EMAIL PROTECTED]> wrote:
>Try upgrading to 8.1.6, its great at throwing 600's ;-)
Try upgrading to 8.1.6, its great at throwing 600's ;-)
-Original Message-
Sent: 24 July 2001 15:31
To: Multiple recipients of list ORACLE-L
I had a production database become corrupt after an ORA-07445 and an
ORA-0600 occurred. The instance would not come back up and had to be
recover
I had a production database become corrupt after an ORA-07445 and an
ORA-0600 occurred. The instance would not come back up and had to be
recovered. I can reproduce and correct the ORA-07445 (bad block) but it
doesn't create the ORA-0600 or corrupt the database. I have tried adding
rows, deleti
