An ALTER TABLE STATEMENT WITH ATTACH PARTITION CLAUSE may
receive the following even though there are no unique constrains
or primary keys:
SQL0803N
One or more values in the INSERT statement, UPDATE statement, or
foreign key update caused by a DELETE statement are not valid
because
the primary key, unique constraint or unique index identified by
"" constrains table "" from having duplicate values for the
index key. SQLSTATE=23505
The following scenario will end up reproducing the conditions
under which the SQL0803N is received:
1. The 'build missing indexes clause' is used to attach a table
that does not have indexes into a range partitioned table that
already has indexes
2. Two or more tables are attached to the range partition table
that do not have indexes.
3. The same tables are then detached.
4. An attempt is made to attach those tables back.
5. SQL0803N is received when you try to attach the second table
onwards.
DIAG.LOG would show messages similar to the following:
2016-02-21-11.24.09.325466-300 I6128898E1041 LEVEL:
Severe
PID : 19374 TID : 139985843906304 PROC :
db2sysc 0
INSTANCE: TESTINST NODE : 000 DB :
TESTDB
APPHDL : 0-8362 APPID:
AUTHID : TEST HOSTNAME: TESTHOST
EDUID : 577 EDUNAME: db2agent (TESTDB) 0
FUNCTION: DB2 UDB, catalog services, sqlrlalt, probe:9122
MESSAGE : ZRC=0x80090005=-2146893819=SQLI_DUPKEY "Duplicate key
violation"
DIA8005C Duplicate key encountered, file token ""
index token
""
record id "".
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -803 sqlerrml: 0
sqlerrmc:
sqlerrp : sqldmisr
sqlerrd : (1) 0x80090005 (2) 0x00000005 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
