Windows Oracle Data Access Components (MOSC)

MOSC Banner

Insert with Array Binding fails to return the exceptions thrown in the after insert trigger

edited Jun 25, 2018 2:32PM in Windows Oracle Data Access Components (MOSC) 3 commentsAnswered
Hello all,

we have a table with an after-insert-trigger, where some bussiness rules are checked.
We try to insert into this table from .Net using the ODP.Net's feature 'array bind'.
Problem: If there are more rows violating the bussiness rules, the OracleException which is thrown contains only one OracleError, the mesasge is right(containing the exception issued by the trigger) but its ArrayBindIndex is wrongly = 0.
We were expecting more OracleErrors with the right ArrayBindIndex to identify the rows which failed.
Can anyone explain this behaviour? Is array binding error handling not supposed to work with user defined exceptions?

Thanks for any hint,

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center