Error 2056 Trapped In 2PC On Transaction / ORA-600 [18201]/ORA-600 [18203]
(Doc ID 2073878.1)
Last updated on SEPTEMBER 11, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.4 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
1. Alert log file shows the following error messages:
...
Error 2056 trapped in 2PC on transaction 68.2.98031. Cleaning up.
Error stack returned to user:
ORA-02056: 2PC: k2lcom: bad two-phase command number rdonly from coord
...
ORA-00600: internal error code, arguments: [18203], [], [], [], [], [], [], [], [], [], [], []
2. Incident trace file shows no failing sql (no cursor) as well as failing function stack information, similar to the below
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
ktc_die k2send kpotxcap kpotxen opiodr
Changes
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 |