My Oracle Support Banner

ORA-00600[KSMLSGE1] Seen in Conjunction With 'Unable to attach to VLM' Messages (Doc ID 437746.1)

Last updated on APRIL 06, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.8 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

a) The following messages are seen in the alert log :-
ERROR: Unable to attach to VLM segment at (nil): window size=0x20000000 size=0x100000000
ORA-00600: internal error code, arguments: [KSMLSGE1], [], [], [], [], [], []
The 'window size' and 'size' values for the VLM attach error can vary depending on the way VLM has been implemented.

b) The ORA-00600 will show 'no SGA' when trying to report the 'Current SQL Statement' i.e. :-
Current SQL information unavailable - no SGA.

c) The ORA-00600[ksmlsge1] call stack will typically show hex values as opposed to meaningful function names.  However (A) and (B) are sufficient for this article to be considered as a potential solution.
This issue is sometimes observed whereby the alert log defined in BACKGROUND_DUMP_DESTINATION is not the one that is written to and instead we somehow see these messages written into an alert log that is located in $OH/rdbms/admin.  When this is the case the normal alert location still is written to normally for general database activities (shutdown/startup etc)

Changes

 NONE

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.