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
Last updated on JULY 05, 2017
Applies to:Oracle Server - Enterprise Edition - Version 220.127.116.11 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms