I agree that batch update is integrated so no way to catch individually commands error.
I'm trying to change my Persistence Tier to instead of use JDBC refactory to Stored Procedure that will result the number of rows on Insert/Update/Delete (CRUD) and also using a Queue process like Oracle Advanced Queuing (AQ) to notifies Erros to subscribers Java process.
I have to process a huge amount off request and very short ansewers time!
What do you think about this approach ?
Bill, do you think that using Queuing to catch/notify Huge amount of SQL commands it's a good option ?
I'm not sure if there is a SQL Patterns indicated to this scenario.
author & internet detective
A sotred procedure cuts down on the netowrk traffic so it will help some.
I don't see how a queue helps you though. Once you introduce the queue, you are no longer updating in a single transaction. And if you don't need a single transaction, that opens the door to other batching techniques - like threading.