A fix is available
APAR status
Closed as program error.
Error description
DB2 Object Compare Tool for z/OS is not generating the Add Versioning Statement when the Alter statement in the DDL is specified prior to the History Table being created. For example: CREATE TABLE.. TEMPORAL_TABLE ALTER TABLE .. ADD VERSIONING .. CREATE TABLE .. HISTORY_TABLE The objects without the versioning statement are created.
Local fix
Move the Alter Table Add Versioning statement after the Create History Table statement.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Object Comparison Tool * * for z/OS who specify a DDL file as the * * compare source, and there is an ALTER * * TABLE ADD VERSIONING statement in the file * * but the specified history table was not * * defined at the time the statement was * * issued. * **************************************************************** * PROBLEM DESCRIPTION: When specifying a DDL file as a * * compare source which has an ALTER * * TABLE ADD VERSIONING statement to * * specify a temporal table, the * * statement was invalid because it * * specified a history table that was * * not defined at the time the * * statement was issued. After the * * compare, if the temporal table needs * * to be created or recreated, the DDL * * for the temporal table is erroneously * * generated without an ADD VERSIONING * * statement in the CHANGE file. * **************************************************************** * RECOMMENDATION: * **************************************************************** A temporal table was defined via an ALTER TABLE ADD VERSIONING statement on the source and this table needs to be created or recreated after the compare, but only the DDL of the temporal table was generated in the CHANGE file. An ADD VERSIONING statement was not generated because the ALTER TABLE ADD VERSIONING statement was not defined at the time the statement was issued.
Problem conclusion
Problem has been resolved. If an ALTER TABLE ADD VERSIONING statement specified a history table which was not defined at the time the statement was issued, DB2 Object Compare will stop processing and issue a RC=12 / Return code 12 with the following error message ADB7205E / msgadb7205e: ADB7205E The ALTER TABLE ADD VERSIONING statement cannot be processed, because the history table history_table_qualifier. history_table_name was not defined at the time the ADD VERSIONING statement was issued in the DDL file.
Temporary fix
Comments
APAR Information
APAR number
PI10310
Reported component name
DB2 OBJECT COMP
Reported component ID
5697G6400
Reported release
A20
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-24
Closed date
2014-07-03
Last modified date
2014-08-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ADBCCMM ADB7000
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.2.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 August 2014