Merge or Insert is Failing with ORA-3137 [12333]
(Doc ID 2039740.1)
Last updated on SEPTEMBER 15, 2021
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle 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 Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Merge or insert statement fails with:
Also the merge/insert statement as such uses many bind variables as shown by the current sql in the trace file:
----- Current SQL Statement for this session (sql_id=...) -----
MERGE INTO <TABLE_NAME> (SELECT ....)
WHEN MATCHED THEN UPDATE SET <COLUMN1>=:2 ,<COLUMN2>=:3 ,<COLUMN3>=:4 , ...
WHEN NOT MATCHED THEN INSERT (<COLUMN1>, <COLUMN2>, <COLUMN3>, ...) VALUES (:49 ,:50 ,:51 , ...)
------Current SQL Statement for this session (sql_id=...) -----
INSERT INTO <TABLE_NAME>(<COLUMN1>,...<COLUMN21)) VALUES (:v1 ,:...:v19 ,:v20 ,:v21)
Note that the call stack of an ORA-3137 [12333] is rather generic and hardly useable to identify a specific issue.
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 |