LI70020: CREATE TABLE WITTH DATALINK COLUMN CAN FAIL WITH SQL0803N

DB2 UDB Version 8.1 FixPak 16 (also known as Version 8.2 FixPak 9 )

APAR status

• Closed as program error.

Error description

• Running SQL statements similar to the following three,
  will result in an 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 "<index-id>"
  constrains table "<table-name>" from having duplicate rows for
  those columns":
  CREATE TABLE TX (
  COL1      DATALINK  LINKTYPE URL
  FILE LINK CONTROL
  INTEGRITY ALL
  READ PERMISSION FS
  WRITE PERMISSION BLOCKED
  RECOVERY NO
  ON UNLINK RESTORE
  );
  RENAME table TX to TX_TMP;
  CREATE TABLE TX (
  COL1      DATALINK  LINKTYPE URL
  FILE LINK CONTROL
  INTEGRITY ALL
  READ PERMISSION FS
  WRITE PERMISSION BLOCKED
  RECOVERY NO
  ON UNLINK RESTORE
  );
  The second CREATE TABLE will receive the SQL0803N error.
  

Local fix

• Do not rename tables with datalinks columns. Drop and recreate
  the table in question instead.
  

Problem summary

• Users Affected: Datalink column users
  Problem Description:
  CREATE TABLE WITH DATALINK COLUMN CAN FAIL WITH SQL0803N
  

Problem conclusion

• Problem was first fixed in DB2 V8.1 FP11.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 UDB EXE LIN

• Fixed component ID

  5724E4904

Applicable component levels

• R810 PSN

     UP

• R820 PSN

     UP