Quick Explain results in DSNT408I SQLCODE -206 for CEV_HVERSION_LVL within Plan Analyzer.
search cancel

Quick Explain results in DSNT408I SQLCODE -206 for CEV_HVERSION_LVL within Plan Analyzer.

book

Article ID: 240256

calendar_today

Updated On:

Products

Plan Analyzer for DB2 for z/OS

Issue/Introduction

Executing a Quick Explain on any object using Plan Analyzer for Db2 for z/OS (PPA) and encountering the following:

DSNT408I SQLCODE = -206, ERROR: CEV_HVERSION_LVL 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

PP189E: Error occurred in CSECT PPA$PROM, statement 262

Environment

Release : 20.0
Component : Plan Analyzer for DB2 for z/OS

Resolution

Plan Analyzer for Db2 for z/OS r20 PTFs LU01891 and LU01892 added 
new column CEV_HVERSION_LVL to tables PTI.PTPA_ES_EXSRC_1200 and 
PTI.PTPA_EXPLPROF_1200 in support of a new explain option.      


PTF LU01892 contained the follow ++HOLD Action:

++HOLD (LU01892) SYSTEM FMID(CPPAK00)                                          
  REASON (DB2DDL )   DATE (21180)                                              
  COMMENT (                                                                    
+----------------------------------------------------------------------+       
|     CA Plan 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        


It is important after the above maintenance has been implemented that the INSMAIN Post Install
CLIST be used to regenerate the 3  Tasks - Execute DB2 catalog customization tasks /
1. Compare DB2 Objects JCL so a new ssidDLIN member is generated as input to the DDLCOMP
step with the DDL structure modification.