|
View previous topic :: View next topic
|
| Author |
Message |
ksathishkumar83
New User
Joined: 21 Nov 2006
Posts: 50
Location: India
|
|
|
|
Hi,
I am getting sql code of -803 when inserting a row in to the table.
but there are no entries present in the table.
How to resolve this. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| what does the fine db2 manual say about it ?? |
|
| Back to top |
|
|
veerababu_p
New User
Joined: 18 Mar 2006
Posts: 5
Location: mumbai
|
|
|
|
| Do mean to say table is empty.If your answer is yes.How you are inserting the record? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
Code -803
-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 |
|
|
veerababu_p
New User
Joined: 18 Mar 2006
Posts: 5
Location: mumbai
|
|
|
|
| How you are inserting the data? |
|
| Back to top |
|
|
Pandora-Box
Global Moderator
.jpg)
Joined: 07 Sep 2006
Posts: 1592
Location: Andromeda Galaxy
|
|
|
|
| Its is -803 because when you are inserting a new row it is trying to insert a duplicate row for the index which is being declared as unique.So you got to change the values. |
|
| Back to top |
|
|
|
|
