Fixes are available
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
Closed as program error.
db2look collects the primary key definition for nickname although the primary key is defined on remote table. Due to the primary key information is fetched to local when creating nickname, we'll get redundant primary key definition error by running this output. For example: ALTER NICKNAME "<schema>"."<nickname>" ADD CONSTRAINT <primary key name> PRIMARY KEY(key1, key2...) NOT ENFORCED ENABLE QUERY OPTIMIZATION DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0624N Table "<schema>.<nickname>" already has a "PRIMARY" key. SQLSTATE=42889 The correct one should be: db2look doesn't generate this ALTER statement.
Users affected: Users of the DB2 for LUW Homogeneous Federation Feature or InfoSphere Federation Server Problem description and summary: See error description.
Problem was first fixed in Version 9.5 FixPak 5 (s091123 ). This fix should be applied on the federation server.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels
22 December 2009