View previous topic :: View next topic
|
Author |
Message |
Kevin Dcosta
New User
Joined: 01 Jan 2008 Posts: 35 Location: Hyderabad
|
|
|
|
A cics background transaction is getting abended with -803 but when i check for the record in the table i did not find it . is there something more that i need to look at . Please Help..... |
|
Back to top |
|
|
abhishekmdwivedi
New User
Joined: 22 Aug 2006 Posts: 95 Location: india
|
|
|
|
Here's the description as per manuals.
-803
AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE INDEX index-name CONSTRAINS COLUMNS OF THE TABLE SUCH THAT NO TWO ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS RID OF EXISTINGF ROW IS X’rid’.
Need to look up for a value which is creating duplicate records within the table. |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
well, don't fool yourself, db2 does not issue these erroneously. there is a duplicate attmpt at insert.
either use a debugger to trace or use some kind of audit trail (displays) to follow your logic. you might be in a loop, who knows? |
|
Back to top |
|
|
stodolas
Active Member
Joined: 13 Jun 2007 Posts: 632 Location: Wisconsin
|
|
|
|
As Dick said, a loop is a good starting point. If you aren't committing your records, your program could be doing an INSERT using that key and if it goes uncommitted you could be attempting another INSERT using the same key, but due to the abend without a commit, all the data is rolled back off the table so when you go to look for it, it is gone. |
|
Back to top |
|
|
|