After applying maintenance, an Extract Procedure fails with SQL error -206
DSNT408I SQLCODE = -206, ERROR: RACR_ORDER_BY_UTILCD IS NOT VALID IN
THE CONTEXT WHERE IT IS USED
Release : 20.0
Component : Database Analyzer for DB2 for z/OS
New column RACR_ORDER_BY_UTILCD was introduced with PTFs LU00145, LU00146 and LU00147.
PTF LU00146 has the following Holddata:
++HOLD (LU00146) SYSTEM FMID(CPDAK00)
REASON (DB2BIND) DATE (21036)
COMMENT (
+----------------------------------------------------------------------+
| CA Database Analyzer For DB2 for z/OS Version 20.0 |
+----------+-----------------------------------------------------------+
|SEQUENCE | After Apply |
+----------+-----------------------------------------------------------+
|PURPOSE | Bind Plans and Packages |
+----------+-----------------------------------------------------------+
|USERS | |
|AFFECTED | All Users |
+----------+-----------------------------------------------------------+
|KNOWLEDGE | |
|REQUIRED | CA DB2 Tools Post Install Customization. |
+----------+-----------------------------------------------------------+
|ACCESS | 1. CA DB2 Tools Post Install |
|REQUIRED | 2. BIND, SYSADM or SYSCNTL on DB2 subsystem. |
+----------+-----------------------------------------------------------+
**************************
* STEPS TO PERFORM *
**************************
DBRMs have changed as part of this maintenance. The members in the
CDBASKL1 library identify the packages that must be rebound.
Refer to the Installing documentation for the CA Database Management
Solutions for DB2 for z/OS on docops.ca.com for more information about
performing the task in the following step.
1. Use Post-Install Tailoring option to Bind Product Packages and Plans.
++HOLD (LU00146) SYSTEM FMID(CPDAK00)
REASON (DB2DDL ) DATE (21036)
COMMENT (
+----------------------------------------------------------------------+
| CA Database Analyzer For DB2 for z/OS Version 20.0 |
+----------+-----------------------------------------------------------+
|SEQUENCE | After Apply |
+----------+-----------------------------------------------------------+
|PURPOSE | Alter CA DB2 Tools objects |
+----------+-----------------------------------------------------------+
|USERS | |
|AFFECTED | All Users. |
+----------+-----------------------------------------------------------+
|KNOWLEDGE | |
|REQUIRED | CA DB2 Tools Post Install Customization |
+----------+-----------------------------------------------------------+
|ACCESS | 1. CA DB2 Tools Post Install |
|REQUIRED | 2. Install SYSADM, SYSADM or DBADM on PTDB. |
+----------+-----------------------------------------------------------+
**************************
* STEPS TO PERFORM *
**************************
DB2 objects must be compared/altered and a Bind Replace performed as
part of this maintenance. Refer to the Installing documentation for the
CA Database Management Solutions for DB2 for z/OS on docops.ca.com for
more information about performing the following tasks using the
post-install tailoring options:
1. Compare DB2 Objects
2. Create Required DB2 Objects
3. Bind Product Packages and Plans
So the Compare and Create Post Installation jobs will create this new column for PDA table PTI.RACR_PROC_1105.
To resolve the -206 SQL error, perform the actions noted in the Holddata.
These PTFs introduced a new feature for PDA, support for LISTDEF, which is documented here.