DB2 enterprise stage - Reject handling
Posted: Wed Nov 29, 2006 1:26 pm
Hi,
This is in regard with the DB2 EE stage...
I have done a search in the forum..but was not able to find an appropriate solution
The problem is as follows.
The job is a simple one..Seqfile -> transformer -> DB2 enterprise stage(Upsert strategy ) ---> Seq file (to capture rejects)
The DB2 table has one attribute whose data type is DATE.
When all the records are good records (i.e., no rejects are happening from Database), we are able to see all the records in the table.
But whenever we have few rejects in the source file (ex: invalid date ), these rejects are being passed to the reject file, but at the same time we are not able to account for all the other good records in the DB Table.
When the same file (with rejects) was run with a commit interval of 1(one), all the good records were inserted into the table.
Is it that when some records are rejected, the database is not able to commit the other inserted records!! Why are those good records missing?
The input link to the DB2EE stage shows the correct record count, and the reject link also shows the correct count...In the datastage director also, we are getting the correct record count (Inserted+Updated+Rejected), but still these records are missing in the database.
Can somebody suggest what is the problem and what can be the solution?
Thanks
This is in regard with the DB2 EE stage...
I have done a search in the forum..but was not able to find an appropriate solution
The problem is as follows.
The job is a simple one..Seqfile -> transformer -> DB2 enterprise stage(Upsert strategy ) ---> Seq file (to capture rejects)
The DB2 table has one attribute whose data type is DATE.
When all the records are good records (i.e., no rejects are happening from Database), we are able to see all the records in the table.
But whenever we have few rejects in the source file (ex: invalid date ), these rejects are being passed to the reject file, but at the same time we are not able to account for all the other good records in the DB Table.
When the same file (with rejects) was run with a commit interval of 1(one), all the good records were inserted into the table.
Is it that when some records are rejected, the database is not able to commit the other inserted records!! Why are those good records missing?
The input link to the DB2EE stage shows the correct record count, and the reject link also shows the correct count...In the datastage director also, we are getting the correct record count (Inserted+Updated+Rejected), but still these records are missing in the database.
Can somebody suggest what is the problem and what can be the solution?
Thanks