Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC63975 Status: Closed

DBA7617 ERROR WHEN ALTOBJ ADMIN ROUTINE IS CALLED AFTER ALTERING
THE TABLE DEFINITION (ADDING CONSTRAINT TO TABLE)

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
ALTOBJ SQL admin routine fails with DBA7617N when a Unique 
constraint is added to the table. 
 
Steps to reproduce the problem 
 
--create database tmp; 
--connect to tmp; 
 
drop table db2.test; 
CREATE TABLE db2.test ( 
   address_linked_person_id integer NOT NULL, 
   address_id          integer NOT NULL, 
   person_id           integer NOT NULL, 
   linked_person_type  integer NOT NULL 
); 
 
ALTER TABLE db2.test 
ADD CONSTRAINT alp_uk 
UNIQUE(address_id,person_id,linked_person_type); 
 
call sysproc.altobj('VALIDATE', 'CREATE TABLE DB2.TEST( 
   ADDRESS_LINKED_PERSON_ID INTEGER NOT NULL, 
   ADDRESS_ID          INTEGER NOT NULL, 
   PERSON_ID           INTEGER NOT NULL, 
   LINKED_PERSON_TYPE  INTEGER NOT NULL, 
   X                   INTEGER NOT NULL 
)', null, ?); 
 
It fails with DBA7617N error
Problem Summary:
Users affected:All 
 
ERROR DESCRIPTION: 
ALTOBJ SQL admin routine fails with DBA7617N when a Unique 
constraint is added to the table. 
 
Steps to reproduce the problem 
 
--create database tmp; 
--connect to tmp; 
 
drop table db2.test; 
CREATE TABLE db2.test ( 
   address_linked_person_id integer NOT NULL, 
   address_id          integer NOT NULL, 
   person_id           integer NOT NULL, 
   linked_person_type  integer NOT NULL 
); 
 
ALTER TABLE db2.test 
ADD CONSTRAINT alp_uk 
UNIQUE(address_id,person_id,linked_person_type); 
 
call sysproc.altobj('VALIDATE', 'CREATE TABLE DB2.TEST( 
   ADDRESS_LINKED_PERSON_ID INTEGER NOT NULL, 
   ADDRESS_ID          INTEGER NOT NULL, 
   PERSON_ID           INTEGER NOT NULL, 
   LINKED_PERSON_TYPE  INTEGER NOT NULL, 
   X                   INTEGER NOT NULL 
)', null, ?); 
 
It fails with DBA7617N error 
 
LOCAL FIX: 
None
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in v97 fp1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.10.2009
17.12.2009
17.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList