Bind Job DSNT201I BIND FOR PLAN IDBSPLAN NOT SUCCESSFUL

Products

• Bind Analyzer for DB2 for z/OS
• SQL-Ease for DB2 for z/OS
• SYSVIEW Performance Management Option for DB2 for z/OS
• Plan Analyzer for DB2 for z/OS
• Subsystem Analyzer for DB2 for z/OS
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - SQL Performance Suite

Issue/Introduction

While binding the plan IDBSPL19, got this resource unavailable message as shown below

DSNT200I  -DBM1  BIND FOR PLAN IDBOPL19 SUCCESSFUL                              
DSN                                                                             
     BIND PLAN (IDBSPL19)                             PKLIST(                   
      )       OWNER(SYSADM) VALIDATE ( RUN )       ISOLATION  ( CS      )       
      RELEASE    ( COMMIT  )       DBPROTOCOL ( DRDA    )       EXPLAIN    ( NO 
                    RETAIN;                                                     
DSNT500I  -DBM1 DSNTBCM1 RESOURCE UNAVAILABLE                                   
           REASON 00E30083                                                      
           TYPE 00000800                                                        
           NAME IDBSPL19                                                        
DSNT201I  -DBM1  BIND FOR PLAN IDBSPL19 NOT SUCCESSFUL           

I also saw a timeout message against the Data collector started task. How come this is coming? Anything specific i need to do

Environment

Release : 19.0

Component : CA Insight Database Performance Monitor for DB for z/OS

Resolution

CA SYSVIEW for DB2 Plans should not be bound when a maintenance is applied. So you may ignore those BIND PLAN errors.

In Post-Install Tasks you have two options for 'INS Bind Product Packages and Plans' Task.

 

- Bind ALL product packages and plans

  (Must be performed for base installs)

- Bind only product packages for maintenance

  (Bind only affected packages from changed DBRMs)

After maintenance you should select second one so only the thr affected Packages should be bound.

Some times after a large maintenance applied it is recommended to select first option so you are sure all Packages

will be bound again, the you have to run the BIND Job with CA SYSVIEW for DB2 Data Collectors stopped, or if they

are started you can ignore the Bind error messages for CA SYSVIEW for DB2 Plans.