ORA-00600: Internal Error Code, Arguments: [17285], [0x9FFFFFFFBDBC1038], [2], [0xC00000036D06E7C0],
(Doc ID 1638330.1)
Last updated on MAY 13, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterOracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
The following error is found in the alert log:
The ORA-600[17285] is raised when trying to remove an instantiation object but that object currently resides in the PLSQL stack (level != 0).1
We need to find the instantiation object which is indicated in the first argument [in square brackets] of the ORA-17285 error. In our example above, it is '9FFFFFFFBD953A30'.
We need to check that it is a PLSQLl object and that the level != 0
type="PL/SQL"[0] lock=c000000267661178 pn=0000000000000000 handle=c00000036d06e7c0 lkhandle=c00000036d06e7c0 spec=9fffffffbdab3208 level=2
flags=SHR/BDY/NST/[447] executions=1
kgiobses=c00000036941f948 kgiobuse=c00000036941f948
DEPENDENCIES: size=12
You may find some or all of the following function codes in the 'Call Stack' section of the incident trace file:
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 |
| Cause |
| Solution |
| References |