Using a RETURNING clause for batch updates with OCI_BATCH_ERRORS Results in Some Records Not Being Returned to the Client when a Constraint Violation (ORA-1) is Encoutered
(Doc ID 1456363.1)
Last updated on MARCH 01, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
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.
An OCI program performing an array insert with OCI_BATCH_ERRORS and returna the newly inserted values back to the OCI program.
This works fine as long no constraint violation occurs - either using dynamic bind or default bind.
If a constraint violation occurs the records are still inserted but the lastest record is not returned to the OCI program.
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