IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

SQLl error code -803 whille inserting a row


IBM Mainframe Forums -> DB2
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
mbatta1

New User


Joined: 30 Jan 2008
Posts: 3
Location: chennai

PostPosted: Mon Feb 11, 2008 12:00 pm
Reply with quote

hi all whille inserting a row in a table i am getting sql error code -803 i.e
constraints voilation but actually i didn't mention any unique constraint condition while declaring the table please help me in solving this problem
Back to top
View user's profile Send private message
kovur

New User


Joined: 15 Nov 2007
Posts: 36
Location: India

PostPosted: Mon Feb 11, 2008 12:06 pm
Reply with quote

Hi,
the explanation for -803 is this

-803 AN INSERTED OR UPDATED VALUE IS INVALID BECAUSE THE INDEX IN INDEX
SPACE indexspace-name CONSTRAINS COLUMNS OF THE TABLE SO NO TWO
ROWS CAN CONTAIN DUPLICATE VALUES IN THOSE COLUMNS. RID OF EXISTING
ROW IS Xrid



Explanation: The table that is the object of the INSERT or UPDATE operation is constrained (by UNIQUE INDEX in the INDEX SPACE indexspace-name to have unique values in certain columns. Completion of the requested INSERT or UPDATE would result in duplicate values occurring in row rid.
If a view is the object of the INSERT or UPDATE statement, the table that defines the view is constrained. The update might also be caused by a DELETE operation of a parent row that cascades to a dependent row with a delete rule of SET NULL.

System Action: The INSERT, UPDATE, or DELETE statement cannot be executed. The object table is unchanged.

Programmer Response: Examine the definitions for UNIQUE INDEX in the INDEX SPACE indexspace-name to determine the uniqueness constraint imposed. Please refer to SYSIBM.SYSINDEXES for the indexspace-name and the associated index-name.

For an UPDATE statement, verify that the specified operation is consistent with the uniqueness constraint. If this does not indicate the error, examine the object table to determine the cause of the problem.

For an INSERT statement, examine the object table to determine which values violate the uniqueness constraint. If the INSERT statement contains a subquery, match the contents of the table addressed by the subquery and the contents of the object table to determine the cause of the problem.

For a DELETE statement, examine the index key columns in the table that defines the index. These columns contain a foreign key, which when set NULL on a cascade delete from the object table, causes the duplicate values.

SQLSTATE: 23505
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> DB2

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts run rexx code with jcl CLIST & REXX 15
No new posts Compile rexx code with jcl CLIST & REXX 6
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
Search our Forums:

Back to Top