CA Repository DB2 13 Updates
Article ID: 259178
Updated On:
Products
Issue/Introduction
PROBLEM DESCRIPTION:
The CA Repository for z/OS r7.2 does not list 13 as a valid version
in the Repository installation 'DB2 Defaults' panel, the DB2 Catsync
panel (SYNCDB2), and the DDLDB2 panels.
These components have been modified to allow 13 as a valid version.
New functionality introduced with DB2 13 will not be supported
at this time.
In addition, when performing a new installation of the Repository for
z/OS r7.2 in a DB2 v13 subsystem, Step 7 'Create the Tables, Views,
Stored Procedures, and Triggers' will return a SQLCODE = -769 during
the creation of an auxiliary table 'APPROVAL_CLOB', as the tablespace
that holds the auxiliary table is not defined as UTS. Step 10 'Create
the Data Tables' will return a SQLCODE = -646 during creation of the
table 'TEMP_SUBSYTES2' as this table needs to have its own tablespace.
This only affects those sites that will be installing a brand new
repository in a DB2 13 environment.
SYMPTOMS:
Specifying 13 as the DB2 version parameter in the installation DB2
Defaults panel will result in a 'Invalid value' message. Specifying
13 for the DB2 Version parameter in the Catsync (SYNCDB2) or DDL gen
(DB2DDL) panels will result in the following message:
"The value 13 entered for DB2 VERSION NO. is not valid. Valid values
are 10, 11 OR 12."
Step 6 of a new installation of the Repository on a DB2 13 system will
return SQLCODE = -769, ERROR: SPECIFICATION OF CREATE AUX TABLE DOES
NOT MATCH THE CHARACTERISTICS OF THE BASE TABLE
Step 10 of a new installation of the Repository on a DB2 13 system will
return SQLCODE = -646, ERROR: TABLE TEMP_SUBTYPES2 CANNOT BE CREATED
IN OR MOVED TO SPECIFIED TABLE SPACE TEMPSUB BECAUSE IT ALREADY CONTAINS
A TABLE.
IMPACT:
Customers cannot specify 13 as a valid version, and for those sites
performing new installations in a DB2 13 environment will encounter the
SQLCODEs described above.
CIRCUMVENTION:
None.
Environment
Release : 7.2
Feedback
