Oracle Database error Instance immediate crash after open Solution

Source: Internet
Author: User
Tags rollback oracle database


A friend's company's database encountered an exception and there was no backup. After the database is opened, crash will be quickly cleared. The following alert log information:


Tue Jul 08 22:53:03 2014
SMON: enabling cache recovery
[2, 13803] Successfully onlined Undo Tablespace 2.
Undo initialization finished serial: 0 start: 7751194 end: 7751284 diff: 90 (0 seconds)
Verifying file header compatibility for 11g tablespace encryption ..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56461 ):
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56461/xxxx_smon_13788_i56461.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
No Resource Manager plan active
Replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Tue Jul 08 22:53:04 2014
QMNC started with pid = 70, OS id = 13956
Completed: alter database open
Tue Jul 08 22:53:05 2014
Db_recovery_file_dest_size of 4977 MB is 0.00% used. This is
User-specified limit on the amount of space that will be used by this
Database for recovery-related files, and does not reflect the amount
Space available in the underlying filesystem or ASM diskgroup.
Tue Jul 08 22:53:05 2014
Dumping diagnostic data in directory = [cdmp_20140708225305], requested by (instance = 1, osid = 13788 (SMON), summary = [incident = 56461].
Block recovery from logseq 2855, block 100 to scn 104606896
Recovery of Online Redo Log: Thread 1 Group 5 Seq 2855 Reading mem 0
Mem #0:/backup/oradata/xxxx/redo05.log
Block recovery completed at rba 2855.131.16, scn 0.104606897
ORACLE Instance xxxx (pid = 32)-Error 600 encountered while recovering transaction (14, 2) on object 15113.
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc:
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Tue Jul 08 22:53:05 2014
Starting background process CJQ0
Tue Jul 08 22:53:05 2014
CJQ0 started with pid = 73, OS id = 13984
Dumping diagnostic data in directory = [cdmp_20140708225306], requested by (instance = 1, osid = 13788 (SMON), summary = [abnormal process termination].
Exception [type: SIGSEGV, SI_KERNEL (general_protection)] [ADDR: 0x0] [PC: 0x97EE385, kghrst () + 1835] [flags: 0x0, count: 1]
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56462 ):
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56462/xxxx_smon_13788_i56462.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56463 ):
ORA-00600: internal error code, arguments: [kghfrempty: ds], [0x2B4E2EB8D790], [], [], [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56463/xxxx_smon_13788_i56463.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56464 ):
ORA-00600: internal error code, arguments: [kghfrempty: ds], [0x2B4E2EB8D790], [], [], [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56464/xxxx_smon_13788_i56464.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Setting Resource Manager plan SCHEDULER [0x32DA]: DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Jul 08 22:53:09 2014
Starting background process VKRM
Tue Jul 08 22:53:09 2014
VKRM started with pid = 69, OS id = 13988
Dumping diagnostic data in directory = [cdmp_20140708225309], requested by (instance = 1, osid = 13788 (SMON), summary = [incident = 56463].
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56465 ):
ORA-00600: internal error code, arguments: [kghfrempty: ds], [0x2B4E2EB8D790], [], [], [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56465/xxxx_smon_13788_i56465.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory = [cdmp_20140708225310], requested by (instance = 1, osid = 13788 (SMON), summary = [incident = 56465].
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56466 ):
ORA-00600: internal error code, arguments: [kghfrempty: ds], [0x2B4E2EB8D790], [], [], [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56466/xxxx_smon_13788_i56466.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Dumping diagnostic data in directory = [cdmp_20140708225311], requested by (instance = 1, osid = 13788 (SMON), summary = [incident = 56466].
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56467 ):
ORA-00600: internal error code, arguments: [kghfrempty: ds], [0x2B4E2EB8D790], [], [], [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Incident details in:/home/oracle/diag/rdbms/xxxx/incident/incdir_56467/xxxx_smon_13788_i56467.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Tue Jul 08 22:53:12 2014
Begin automatic SQL Tuning Advisor run for special tuning task "SYS_AUTO_ SQL _TUNING_TASK"
Tue Jul 08 22:53:13 2014
Errors in file/home/oracle/diag/rdbms/xxxx/trace/xxxx_smon_13788.trc (incident = 56468 ):
ORA-00600: internal error code, arguments: [kghfrempty: ds], [0x2B4E2EB8D790], [], [], [], [], [], [], [], [], [], [], [], []
ORA-07445: exception encountered: core dump [kghrst () + 1835] [SIGSEGV] [ADDR: 0x0] [PC: 0x97EE385] [SI_KERNEL (general_protection)] []
ORA-00600: internal error code, arguments: [17182], [0x2B4E2EB8D7A0], [], [], [], [], [], [], [] [], []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
PMON (ospid: 13666): terminating the instance due to error 474
System state dump requested by (instance = 1, osid = 13666 (PMON), summary = [abnormal instance termination].
System State dumped to trace file/home/oracle/diag/rdbms/xxxx/trace/xxxx_diag_13684_20140708225315.trc
Tue Jul 08 22:53:16 2014
Dumping diagnostic data in directory = [cdmp_20140708225315], requested by (instance = 1, osid = 13666 (PMON), summary = [abnormal instance termination].
Tue Jul 08 22:53:17 2014
Instance terminated by PMON, pid = 13666
It can be seen that the smon process cannot recover a transaction, and the Pmon process forcibly terminates the Instance.
Specifically, the transaction cannot be recovered: transaction (14, 2) on object 15113
According to the information, there is an exception in the smon rollback transaction. Let's analyze the trace file of the smon process and confirm why the transaction cannot be recovered.
Based on the transaction (), search: 000e. 002 to locate the following information:


<Pre class = "brush: plain"> ************ dump undo block **********
Dump of buffer cache at level 3 for tsn = 2 rdba = 12630748
BH (0x1d9ef41a48) file #: 3 rdba: 0x00c0badc (3/47836) class: 44 ba: 0x1d84096000
Set: 322 pool: 3 bsz: 8192 bsi: 0 sflg: 2 pwc:
Dbwrid: 1 obj:-1 objn: 0 tsn: 2 afn: 3 hint: f
Hash: [0x2425e3c4e0, 0x2425e3c4e0] lru: [0x1d9ef41c70, 0x1d9ef41a00]
Ckptq: [NULL] fileq: [NULL] objq: [0x1d9ef43b10, 0x2110560590] objaq: [0x1d9ef41f18, 0x2110560580]
St: XCURRENT md: NULL fpin: 'ktuwh23: ktubko 'tch: 1
Flags:
LRBA: [0x0. 0.0] LSCN: [0x0.0] HSCN: [0xffff. ffffffff] HSUB: [65535]
Buffer tsn: 2 rdba: 0x00c0badc (3/47836)
Scn: 0x0000. 06382fde seq: 0x05 flg: 0x04 tail: 0x2fde0205
Frmt: 0x02 chkval: 0x5fc6 type: 0x02 = KTU UNDO BLOCK
Hex dump of block: st = 0, typ_found = 1
Dump of memory from 0x0000001D84096000 to 0x0000001D84098000
Some content is omitted.
**************************************** ****************************************
Undo blk:
Xid: 0x000e. 002.00034175 seq: 0x35dc cnt: 0x5 irb: 0x1 icl: 0x0 flg: 0x0000
 
Rec Offset
---------------------------------------------------------------------------
0x01 0x1f28 0x02 0x1ec8 0x03 0x1e38 0x04 0x1db8 0x05 0x1d1c
 
*-----------------------------
* Rec #0x1 slt: 0x02 objn: 15113 (0x00003b09) objd: 15555 tblspc: 56 (0x00000038)
* Layer: 11 (Row) opc: 1 rci 0x00
Undo type: Regular undo Last buffer split: No
Temp Object: No
Tablespace Undo: No
Rdba: 0x00c0badb
*-----------------------------
KDO undo record:
KTB Redo
Op: 0x02 ver: 0x01
Compat bit: 4 (post-11) padding: 1
Op: C uba: 0x00c0badb. 35dc. 2f
KDO Op code: IRP row dependencies Disabled
Xtype: XA flags: 0x00000000 bdba: 0x468069a2 hdba: 0x46800c91
Itli: 2 ispac: 0 maxfr: 4858
Tabn: 0 slot: 108 (0x6c) size/delt: 64
Fb: -- H-FL -- lb: 0x0 cc: 16
Null:
01234567890123456789012345678901234567890123456789012345678901234567890123456789
------ NNNNN--NN-
Col 0: [12] 33 35 38 30 34 36 33 32 36 30 36
Col 1: [1] 20
Col 2: [9] 64 65 6c 69 76 65 72 65 64
Col 3: [5] 30 32 31 30 30
Col 4: [4] c9 cf ba a3
Col 5: [1] 30
Col 6: * NULL *
Col 7: * NULL *
Col 8: * NULL *
Col 9: * NULL *
Col 10: * NULL *
Col 11: [7] 78 72 04 11 23 02
Col 12: [7] 78 72 04 11 23 02
Col 13: * NULL *
Col 14: * NULL *
Col 15: [0]
 
*-----------------------------
* Rec #0x2 slt: 0x02 objn: 15113 (0x00003b09) objd: 15555 tblspc: 56 (0x00000038)
* Layer: 11 (Row) opc: 1 rci 0x01
Undo type: Regular undo User Undo Applied Last buffer split: No
Temp Object: No
Tablespace Undo: No
Rdba: 0x00000000
*-----------------------------
KDO undo record:
KTB Redo
Op: 0x02 ver: 0x01
Compat bit: 4 (post-11) padding: 1
Op: C uba: 0x00c0badc. 35dc. 01
KDO Op code: IRP row dependencies Disabled
Xtype: XA flags: 0x00000000 bdba: 0x468069a2 hdba: 0x46800c91
Itli: 2 ispac: 0 maxfr: 4858
Tabn: 0 slot: 107 (0x6b) size/delt: 9
Fb: -- H ----- lb: 0x0 cc: 0
Nrid: 0x468069b9. 7
Null:
 
*-----------------------------
* Rec #0x3 slt: 0x02 objn: 15404 (0x00003c2c) objd: 15556 tblspc: 4 (0x00000004)
* Layer: 10 (Index) opc: 22 rci 0x02
Undo type: Regular undo User Undo Applied Last buffer split: No
Temp Object: No
Tablespace Undo: No
Rdba: 0x00000000
*-----------------------------
Index undo for leaf key operations
KTB Redo
Op: 0x04 ver: 0x01
Compat bit: 4 (post-11) padding: 1
Op: L itl: xid: 0x000e. 00f. 00034021 uba: 0x00c07ed9. 35d5. 18
Flg: C --- lkc: 0 scn: 0x0000. 0635da5a
Dump kdilk: itl = 2, kdxlkflg = 0x25 sdc = 2 indexid = 0x00008a block = 0x01002052
(Kdxlre): restore leaf row (clear leaf delete flags)
Number of keys: 2
Key sizes:
18 18
Key 36 ):
05 30 32 31 30 ff 0a 00 00 3c c3 46 80 69 a2 00 6c 05 30 32 31 30 30 ff
0a 00 00 3c c3 46 80 69 a2 00 6e
Selflock: (1): 00
Bitmap: (1): fc
 
*-----------------------------
* Rec #0x4 slt: 0x02 objn: 15139 (0x00003b23) objd: 15559 tblspc: 57 (0x00000039)
* Layer: 10 (Index) opc: 22 rci 0x03
Undo type: Regular undo User Undo Applied Last buffer split: No
Temp Object: No
Tablespace Undo: No
Rdba: 0x00000000
*-----------------------------
Index undo for leaf key operations
KTB Redo
Op: 0x04 ver: 0x01
Compat bit: 4 (post-11) padding: 1
Op: L itl: xid: 0x000e. 00e. 0001da74 uba: 0x00c144ff. 2156.16
Flg: C --- lkc: 0 scn: 0x0000. 04d6e213
Dump kdilk: itl = 2, kdxlkflg = 0x25 sdc = 2 indexid = 0x474000a2 block = 0x47400ffe
(Kdxlre): restore leaf row (clear leaf delete flags)
Number of keys: 2
Key sizes:
9 9
Key 18 ): 01 20 06 46 80 69 a2 00 6c 01 20 06 46 80 69 a2 00 6e
Selflock: (1): 00
Bitmap: (1): fc
 
*-----------------------------
* Rec #0x5 slt: 0x02 objn: 15134 (0x00003b1e) objd: 15560 tblspc: 57 (0x00000039)
* Layer: 10 (Index) opc: 22 rci 0x04
Undo type: Regular undo User Undo Applied Last buffer split: No
Temp Object: No
Tablespace Undo: No
Rdba: 0x00000000
*-----------------------------
Index undo for leaf key operations
KTB Redo
Op: 0x04 ver: 0x01
Compat bit: 4 (post-11) padding: 1
Op: L itl: xid: 0x000d. 002.000287af uba: 0x00c1b5ce. 37e8. 1f
Flg: C --- lkc: 0 scn: 0x0000. 05e39111
Dump kdilk: itl = 2, kdxlkflg = 0x25 sdc = 1 indexid = 0x47400082 block = 0x47800db3
(Kdxlre): restore leaf row (clear leaf delete flags)
Number of keys: 2
Key sizes:
13 13
Key 26 ):
0c 33 35 38 30 34 36 33 32 35 38 0c 33 35 38 30 34 36 33 32 36 30
36
Keydata/bitmap: (20): 00 00 3c c3 46 80 69 a2 00 6e 00 00 3c c3 46 80 69 a2 00 6c
Selflock: (1): 00
Bitmap: (1): fc
 
Kcra_dump_redo_internal: skipped for critical process
ORACLE Instance xxxx (pid = 32)-Error 600 encountered while recovering transaction (14, 2) on object 15113. </pre>
As you can see, () this transaction contains five undo records, that is, five operations are required and cannot be performed at the end of record 1.
Is that true?
Let's first look at the dump information of the undo block:
Xid: 0x000e. 002.00034175 seq: 0x35dc cnt: 0 × 5 irb: 0 × 1
From this we can see that this undo block contains five undo records. However, for this transaction, the starting point is irb: 0 × 1, that is, the first undo record.
Here is obviously a problem. We can see that the rci values of the following undo recor are: 0x04 0x03 0x02 0x01 0x00
Therefore, judging from the rci value of undo record, this transaction should be rollback from undo record 5 to undo record 1.
But the irb value mentioned in the undo block is actually 0 × 1? Here, irb: 0 × 1 is the first undo record, and its rci value itself is 0. How to roll back?
Therefore, it is obvious that there is a problem.
Therefore, if you want to temporarily solve the problem of no crash after the database is opened, you can directly modify the undo block. Modify the irb or rci value.
Note: the library and other files with bad blocks are not discussed here. Because there is no other information.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.