SQLCODE -206 during ICL Analysis using RC/Migrator for COPYSTATS
Article ID: 5384
Updated On:
Products
Issue/Introduction
When analyzing ICL using an Analysis Profile in RC/Migrator for Db2 for z/OS (RCM), SQL error -206 occurs indicating that COPYSTATS is not valid:
DSNT408I SQLCODE = -206, ERROR: COPYSTATS IS NOT VALID IN THE CONTEXT WHERE IT IS USED
DSNT418I SQLSTATE = 42703 SQLSTATE RETURN CODE
DSNT415I SQLERRP = DSNXORSO SQL PROCEDURE DETECTING ERROR
DSNT416I SQLERRD = -100 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION
DSNT416I SQLERRD = X'FFFFFF9C' X'00000000' X'00000000' X'FFFFFFFF' X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
Cause
There have been a number of changes to the APTABLE, PTI.PTMGB_APTABLE_0100, as new Analysis Profile functionality has been added to
releases r18 and r19. The -206 SQL error for column COPYSTATS is a result of having applied maintenance that is now referencing this
new column in the APTABLE but the APTABLE in this environment has not been updated.
The following columns have been added to this table on Database Management r18 and r19:
VERIFYONLY
AUTOREPAIR
COPYSTATS
MERGECONSISTENCY
SOURCEEXECUTION
SOURCEFINAL
TARGETFINAL
VERSION
DATA
It is most likely that the required Post Install tasks have not been regenerated and executed after applying this maintenance.
Resolution
To resolve this problem you will need to generate the Compare, Create and Bind post install tasks through the install panels and run these jobs.
1. Compare DB2 Objects
2. Create Required DB2 Objects
3. Bind Product Packages and Plans
It is important that the jobs are regenerated through the panels before being executed, as it is this process that references
the CDBASKL0 DDL members to build the required DDL for the PTDB objects.
Feedback
