Wednesday, October 19, 2016

ORA-600's due to Memory Corruption - Potential Causes/Solutions

In certain instances, the following ORA-600 errors can arise on Oracle 11.x or later - Possible Causes/Solution are mentioned below - please check for relevance in your particular scenario.
ORA-600 [kghfre2]
=================
DESCRIPTION:
A failed attempt to free a chunk of memory results in this ORA-600 error. Further investigation reveals that, this chunk header is neither "recreatable" nor "freeable".
and therefore generate this exception.

ORA-600 [17402]
===============
DESCRIPTION:
ORA-600[17402] is indicative of a Memory Heap Corruption.

ORA-600 [17183]
===============
DESCRIPTION:
Memory is checked to ensure that it is "freeable". If doing so causes a failure, this shall geenerating this ORA-600 exception. This also results in Memory Corruption and causes no Data Corruption.

Possible Causes - Require further investigation and RCA:
  1. Improper/Unpatched OS Stack
  2. Improper/Incorrectly configured VM/LPAR Memory Configuration
  3. Hardware Memory Issues
  4. SGA/PGA/UGA Memory Shortage/Exhaustion
Potential Solutions:
  1. Increase the SGA/PGA Memory Areas
  2. Perform full hardware diagnostics on the Memory Hardware
  3. Check the OS Stack for latest Patch levels