For examlpe out of 200 records 10 have a bad date. DB2 inserts 190 instread of rolling back to the last successful transaction.
I did this by tring to insert an invalid date to a DB2 table. Instead of aborting the job and rolling back the records that were part of the same array, it just raises a warning and keeps going without rolling back.
Is this a DB2 UDB API stage bug or a setting in the CLI Driver? Any ideas on how to get this to work?
Array size: 50
Transaction commit size: 50
Number of records processed: 200
Driver: [IBM][CLI Driver][DB2/NT]
![Question :?:](./images/smilies/icon_question.gif)