So, you found this error?
Well, I received this in a client environment. After checking MOS ORA-02056: 2PC: K2gCheckGlobalCommit: Bad Two-phase Command Number 1 From Coord (Doc ID 2498134.1), which points to a known issue when dealing with committing transactions as per Bug 22016049 I noticed my problem could be different…
My real root cause is my transaction being done on a remote object and when checking on remote database I found pending distributed transactions.
For more informations about distributed transactions, please check: https://docs.oracle.com/database/121/ADMIN/ds_txns.htm#ADMIN12211
So, if you getting this situation, before planning and applying the patch I suggest you:
- Check if your process is not working on remote databases.
- Check for any possible distributed remote transactions.
How? Easy check (on remote db):
select * from dba_2pc_pending;
I hope it helps!
PS NOTE: I just found this very good and complete post by Rodrigo Mufalani on the same topic: ORA-01591: lock held by in-doubt distributed transaction
Have a look for an Action Plan!
Pingback: ORA-01591: lock held by in-doubt distributed transaction – Mufalani – DBA (OCM)