ORA-00600: [k2srec: Should Be Another Instance]/ ORA-00600: [18301] Reported By A Foreground Process
(Doc ID 1549515.1)
Last updated on FEBRUARY 26, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.3 [Release 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - 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 distributed transaction has been put into a pending committed state and a foreground process then reports ORA-00600: [k2srec: should be another instance] as per the following alert.log entry
Tue Feb 19 09:30:28 2013
DISTRIB TRAN MR004.6cd4846b.31.15.126052
is local tran 1770.11.364260 (hex=6ea.0b.58ee4)
insert pending committed tran, scn=7816324298699 (hex=71b.e13bb7cb)
Tue Feb 19 09:30:28 2013
Errors in file /oracle_trazas/diag/rdbms/mr01/MR011/trace/MR011_ora_13494.trc (incident=5138087):
ORA-00600: código de error interno, argumentos: [k2srec: should be another instance], [1], [], [], [], [], [], [], [], [], [], []
Incident details in: /oracle_trazas/diag/rdbms/mr01/MR011/incident/incdir_5138087/MR011_ora_13494_i5138087.trc
Tue Feb 19 09:31:15 2013
with the following stack
k2srec <- k2serv <- opiodr <- ttcpip
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 |