Home » RDBMS Server » Server Administration » Unexpect Instance termination
Unexpect Instance termination [message #57184] Tue, 27 May 2003 01:50 Go to next message
rajmukesh
Messages: 14
Registered: March 2003
Junior Member
hi!
For the last two days the oracle instance terminates unexpectedly. THe oracle service stops.
The oracle needs to be restarted.
ORA-00600: internal error code, arguments: [[17182]], [[0x1BFFFF4]], [[]], [[]], [[]], [[]], [[]], [[]]
Internal heap ERROR 17182 addr=01BFFFF4
This is the message I get in the alert log.
The database has been recently migrated from 9i release1 to oracle9i release2.
Do suggest me the solution.

Mukesh
Re: Unexpect Instance termination [message #57186 is a reply to message #57184] Tue, 27 May 2003 04:16 Go to previous message
psmyth
Messages: 81
Registered: October 2002
Member
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
Previous Topic: Multiple of Oracle database versus 4 large oracle database
Next Topic: Oracle 9i on Slave Hard Disk
Goto Forum:
  


Current Time: Thu Mar 28 10:41:50 CDT 2024