Document 1234083.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-sta...

ORA-600 [13310] Reported When Obtaining An OS Unique Identifier (Doc ID 1234083.1)

Modified: 13-Jun-2013

Type: PROBLEM

In this Document
Symptoms
Changes
Cause
Solution
References

APPLIES TO:
Oracle Database - Enterprise Edition - Version 8.1.7.4 to 11.2.0.3 [Release 8.1.7 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 11-Mar-2013***

SYMPTOMS
ORA-600 [13310] reported in alert.log and shown in client application.

CHANGES
A likely change will be that more memory/swap is in use by existing and/or newly created databases.

CAUSE
An ORA-600 [13310] occurs when Oracle is not able to obtain an OS unique identifier.
In most cases the failing statement will be one of the following:

select sys_guid from dual;

or
insert into mgmt_severity(target_guid,metric_guid,....);

The error does occur at a moment in time when the OS call made fails to provide an OS unique identifier, in most cases due to a lack of
system resources (memory, swap, etc/...).
It will be likely that at the same moment in time other (network) errors are observed which are likely triggered as well by the lack of system
resources.
The ora-600 [13310] can occur at process creation but as well in an existing connection.
The ora-600 [13310] is more likely to be hit at Windows platforms compared to other platforms.

SOLUTION
The problem is resolved by freeing up and/or increasing system resources such as memory and swap.

REFERENCES
NOTE:798402.1 - Query Failing With ORA-00600 [13310]

1 of 1

12/19/2013 7:13 AM