ANBOB™

Oracle is undoing an index leaf key operation. If the key is not found, ORA-00600 [6006] is logged.

ORA-600[6006] is usually caused by a media corruption problem related to either a lost write to disk or a corruption on disk.

You will need to get with your Hardware
vendor and check the hardware/Operating system with extensive diagnostics.

Solution of the Problem

1) Review the trace files and look for the object(s) involved. If the trace file does not have a SQL statement, search on the following: “block dump header”

2) In the block header there will be a seg/obj = hex value. Convert the hex to dec and this will give you the data_object_id.

3) The alert.log may also show the affected object, for example:

ORACLE Instance ORCL (pid = 8) – Error 600 encountered while recovering transaction (9999, 36) on object 45879.

SQL>select owner, object_name from dba_objects where data_object_id = object#;

This will be the object you need to work with.

To implement the solution:

1. shutdown the oracle instance.
SQL> shut immediate

2. set event – event=”10513 trace name context forever, level 2″ (this event and setting disables transaction recovery which was initiated by SMON). Open the pfile and add the following line inside pfile.

event=”10513 trace name context forever, level 2″

Tip:

If there is still a transaction rollback after the set   10513 event starts and the instance crashes, you can set the 10517 event, which is an internal event that has not disclosed too much information for the time being.

3. startup instance
SQL> startup

4.
– If the object is an index – drop and recreate.
– If the object is a table – drop / export / Create Table as Select (CTAS) to change the object ID

5. shutdown the instance
SQL> shut immediate

6. remove the event
Open the pfile and remove the event line that was added.

7. startup the instance
SQL> startup

如果您不能自己解决请联系 www.anbob.com 首页上的联系方式。

打赏

微信扫一扫，打赏作者吧～