以下为ORA-600[1112]内部错误的相关诊断信息:
ERROR: ORA-600 [1112] [a] [b] [c] [d] [e] VERSIONS: versions 7.3 to 9.2 DESCRIPTION: ORA-600 [1112] is getting raised while trying to add a row cache enqueue to a transaction state object during lookup of the default tablespace number during table creation. FUNCTIONALITY: STATE OBJECT MANAGEMENT IMPACT: PROCESS FAILURE NON CORRUPTIVE - No underlying data corruption. Bug 2489130 - OERI:1112 can occur while dumping PROCESSSTATE informatio (Doc ID 2489130.8) Bug 4126973: ORA-600[504] AND ORA-600[1112] OCCURED WHEN GETTING "ERRORSTACK" Base Bug 2489130 Bug 3954753: ORA-600 [1112] AND SESSION CRASH The cause for the ORA-00600 [1112] appears due to Bug 2489130 This error can occur on dumping of process state which is what occurred here. The primary issue is the WAITED TOO LONG FOR A ROW CACHE ENQUEUE LOCK! This then triggers a system state and process state to be dumped due to nature of the problem. The ORA-00600 [1112] gets dumped out when process state is done. Stack for trace very similar to Bug 2489130 and this is only known bug on 9.2 like this with a fix. A fix for bug 2489130 is included in the 9.2.0.7 patchset. Recommend applying 9.2.0.8 patchset to have this and other bug fixes. This would only prevent the ORA-00600 [1112] from occurring on state dumps. The primary row cache issue still to be investigated by performance team.
© 2009 – 2011, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.
相关文章 | Related posts:
- PMON: TERMINATING INSTANCE DUE TO ERROR 600 on 8i
- ORA-600 quick reference guide
- Oracle内部错误ORA-07445: [ACCESS_VIOLATION] [unable_to_trans_pc][UNABLE_TO_READ]
- Cannot Restart Oracle After Setting Global Name to NULL
- How to trigger ORA-00600,ORA-7445 by manual
- FAQ Memory Corruption
- Summary of Bugs Containing ORA – 00600 [KCBNEW_3]
- ORA-00600 [kcblasm_1] May Occur After Applying The Patch 7523755
最新评论