ORA-600: , , [space Leak] After ORA-2050 and ORA-2063
(Doc ID 1615507.1)
Last updated on OCTOBER 11, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 and later
Information in this document applies to any platform.
Error 3114 trapped in 2PC on transaction 100.23.1050. Cleaning up.
Error stack returned to user:
ORA-02050: transaction 100.23.1050 rolled back, some remote DBs may be in-doubt
ORA-03114: not connected to ORACLE
ORA-02063: preceding line from NPD_DA
Wed Jan 01 21:32:36 2014
Errors in file /opt/app/oracle/admin/NP9D/diag/rdbms/np9d/NP9D/trace/NP9D_s001_19868.trc (incident=168517):
ORA-00600: internal error code, arguments: , , [space leak], , , , , , , , , 
Other errors are also reported after the distributed transaction rollback such as ORA-7445 [kglpur()+16] and ORA-600 [kpndbcon-svchpnotNULL].
The trace files written by the ORA-600  errors show that the memory being leaked is labeled as 'oper caps':
EXTENT 0 addr=3d9c7f2c8
Chunk 3d9c7f2d8 sz= 28072 free " "
Chunk 3d9c86080 sz= 33288 freeable "oper caps "
There are no errors written to the remote alert.log (a loopback link in this case).
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