When using the same OBID data set in the Insight Data Collector (DC) monitoring members of a DB2 Data Sharing group, I see this message "DBG48006E OBID TABLE FILE IS INVALID" in the DC DBGPRINT output.

book

Article ID: 52245

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Description:

Why do I see message "DBG48006E OBID TABLE FILE IS INVALID" in my Insight Data Collector started task DBGPRINT output when I use the same OBID data set in the Insight DCs that are monitoring all members of a DB2 Data Sharing group?
You need to add the jcl parameter =GROUP=db2group in the jcl that initializes the OBID data set.
Details in the Insight System Guide, Appendix 'D' for details on OBID Translation Utility.

Solution:

Each Insight Data Collector that is monitoring a member of a DB2 Data Sharing group can use a single OBID file.
This OBID data set is created and populated by the utility coded in the IDB2OBI JCL member of the product SOURCE data set.
You would only need to run it against one member of the DS group.

In order for a single OBID file to be used by all Insight DCs monitoring members of a DB2 DS group, modify the IDB2OBI JCL member as follows:

  1. Code the =GROUP parameter in the PARM entry for the EXEC card in the JCL.

    e.g.
    Assume DB2T is a member of the DS group DSNGET0.
    To create a single OBID file that can be used for all members of the DSNGET0 group, code the IDB2OBI JCL as follows:
    ...
    //IDOBLOAD EXEC PGM=IDB2OBI,REGION=0M,COND=(0,LT),
    // PARM='=UPPER=NO =PLAN=IDBOxxxx =SSID=DB2T =GROUP=DSNGET0'
    ...
    Plan IDBOxxxx would have been bound as part of the product post install process, where xxxx can be any 4 characters.

Environment

Release:
Component: IDB2