ORA-600 [17182], ORA-07445 [kghrst () + 1567]

Today, a single point library of 11.2.0.2 on CentOS5.8 x86-64 has a problem. The specific phenomenon is that every time the alter database is opened, the alert Log will be automatically crash (crashed) within 10 seconds, as shown in the following warning SMON: slave died unexpectedly, downgrading to serial recovery
Errors in file/cvms/app/Oracle/diag/rdbms/hncvms/HNCVMS/trace/HNCVMS_smon_11203.trc (incident = 187832 ):
ORA-00600: internal error code, arguments: [17182], [0x2B7C8E7CD7A0], [], [], [], [], [], [], [], []
Incident details in:/cvms/app/oracle/diag/rdbms/hncvms/HNCVMS/incident/incdir_187832/HNCVMS_smon_11203_i187832.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Doing block recovery for file 12 block 470173
Resuming block recovery (PMON) for file 12 block 470173
Block recovery from logseq 31163, block 68 to scn 70921364289
Recovery of Online Redo Log: Thread 1 Group 1 Seq 31163 Reading mem 0
Mem #0:/cvms/app/oracle/oradata/HNCVMS/redo01.log
Block recovery completed at rba 32.163.135.16, scn 16.2201887554
ORACLE Instance HNCVMS (pid = 14)-Error 600 encountered while recovering transaction (11, 3) on object 75050.
Errors in file/cvms/app/oracle/diag/rdbms/hncvms/HNCVMS/trace/HNCVMS_smon_11203.trc:
ORA-00600: internal error code, arguments: [17182], [0x2B7C8E7CD7A0], [], [], [], [], [], [], [], []
Exception [type: SIGSEGV, SI_KERNEL (general_protection)] [ADDR: 0x0] [PC: 0x90890C3, kghrst () + 1567] [flags: 0x0, count: 1]
Errors in file/cvms/app/oracle/diag/rdbms/hncvms/HNCVMS/trace/HNCVMS_smon_11203.trc (incident = 187833 ):
ORA-07445: exception encountered: core dump [kghrst () + 1567] [SIGSEGV] [ADDR: 0x0] [PC: 0x90890C3] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B7C8E7CD7A0], [], [], [], [], [], [], [], []
Incident details in:/cvms/app/oracle/diag/rdbms/hncvms/HNCVMS/incident/incdir_187833/HNCVMS_smon_11203_i187833.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Feb 17 10:44:11 2014
PMON (ospid: 11177): terminating the instance due to error 474 failed by observing the log, see Part

Doing block recovery for file 12 block 470173
Resuming block recovery (PMON) for file 12 block 470173
Block recovery from logseq 31163, block 68 to scn 70921364289
Recovery of Online Redo Log: Thread 1 Group 1 Seq 31163 Reading mem 0
Mem #0:/cvms/app/oracle/oradata/HNCVMS/redo01.log
Block recovery completed at rba 32.163.135.16, scn 16.2201887554
ORACLE Instance HNCVMS (pid = 14)-Error 600 encountered while recovering transaction (11, 3) on object 75050.

Then, based on the principle analysis, we can find that the problem occurs during Instance recovery. When an error is reported, it can be determined that it is a block in file12 block 470173, that is, the block where the object id is 75050. If a problem (Bad block) occurs, the instance recover encounters a 600 error and the Pmon ends, when Pmon is terminated and the entire instance is down, we can take two steps: Step 1: Start the instance, query the types of objects in file 12 block 470173 and object 75050. 1. When an Instance is started, Instance recovery is executed, and recovery is used to crash the database, so we need to temporarily stop the action of instance recovery to create a pfile based on the current spfile, and then follow the following message after the pfile: event = "10513 trace name context forever, level 2"
2. query object (the system will not crash now, but the database status is abnormal because there is no instance recovery) 1) SQL> SELECT owner, object_name, object_type FROM dba_objects WHERE object_id = 75050;
2) SQL> select segment_type, owner, segment_name from dba_extents where file_id = & file_id and & block between block_id and block_id + blocks-1;
Check the object type based on the feedback above.

1 2 Next Page