本文详细解释了Oracle数据库中出现的内部错误ORA-600[[17182]]的含义、可能的原因以及可能的解决方案。包括检查内存块头中的魔法数是否被篡改、查看操作系统日志、运行低级内存测试等步骤。
got this from metalink.
Doc ID: Note:34779.1
Subject: ORA-600 [[17182]] "Heap chunk header BAD MAGIC"
Type: REFERENCE
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 29-FEB-1996
Last Revision Date: 28-FEB-2003
Note: For additional ORA-600 related information please read [[NOTE:146580.1]]
PURPOSE:
This article discusses the internal error "ORA-600 [[17182]]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance.
ERROR:
ORA-600 [[17182]][[a]][[b]][[c]][[d]][[e]] VERSIONS: versions 7.3.X, 8.1.X and 9.X DESCRIPTION:
Oracle has detected that the magic number in a memory chunk header has been overwritten. This is a heap (in memory) corruption and there is no underlying data corruption. The error may occur in the one of the process specific heaps (the Call heap, PGA heap, or session heap) or in the shared heap (SGA).
FUNCTIONALITY: HEAP MANAGEMENT IMPACT: PROCESS FAILURE MEMORY CORRUPTION, POSSIBLE INSTANCE FAILURE. NON DATA CORRUPTIVE - No underlying data corruption.
SUGGESTIONS: Check to see if the issue is reproducable. Check the OS system logs (/var/adm/messages on Solaris, for example) for any memory corruption and run low level memory tests on the system. If reproducable, send alert.log and trace files to support. Known Issues: Bug 2686597 ORA-600 [[17182]] OCCURS IN SELECT OF LARGE TABLES WITH USING AUTOMATIC PGA Fixed in 9.2 Bug 2228280 CUSTOMER RECEIVING A NUMBER OF ORA-7445 ORA-600 ERROR Private memory corruption possible with OPTIMIZER_MODE=RULE Fixed in releases 9.0.1.4 and 9.2.0.2 Bug 1542218 OCCASIONAL ORA-600 [[17182]] Fixed in releases 8.1.7.3, 9.0.1.2 and 9.2.0.1
Doc ID: Note:34779.1
Subject: ORA-600 [[17182]] "Heap chunk header BAD MAGIC"
Type: REFERENCE
Status: PUBLISHED
Content Type: TEXT/PLAIN
Creation Date: 29-FEB-1996
Last Revision Date: 28-FEB-2003
Note: For additional ORA-600 related information please read [[NOTE:146580.1]]
PURPOSE:
This article discusses the internal error "ORA-600 [[17182]]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance.
ERROR:
ORA-600 [[17182]][[a]][[b]][[c]][[d]][[e]] VERSIONS: versions 7.3.X, 8.1.X and 9.X DESCRIPTION:
Oracle has detected that the magic number in a memory chunk header has been overwritten. This is a heap (in memory) corruption and there is no underlying data corruption. The error may occur in the one of the process specific heaps (the Call heap, PGA heap, or session heap) or in the shared heap (SGA).
FUNCTIONALITY: HEAP MANAGEMENT IMPACT: PROCESS FAILURE MEMORY CORRUPTION, POSSIBLE INSTANCE FAILURE. NON DATA CORRUPTIVE - No underlying data corruption.
SUGGESTIONS: Check to see if the issue is reproducable. Check the OS system logs (/var/adm/messages on Solaris, for example) for any memory corruption and run low level memory tests on the system. If reproducable, send alert.log and trace files to support. Known Issues: Bug 2686597 ORA-600 [[17182]] OCCURS IN SELECT OF LARGE TABLES WITH USING AUTOMATIC PGA Fixed in 9.2 Bug 2228280 CUSTOMER RECEIVING A NUMBER OF ORA-7445 ORA-600 ERROR Private memory corruption possible with OPTIMIZER_MODE=RULE Fixed in releases 9.0.1.4 and 9.2.0.2 Bug 1542218 OCCASIONAL ORA-600 [[17182]] Fixed in releases 8.1.7.3, 9.0.1.2 and 9.2.0.1
扫一扫
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
