II14607: KNOWN ISSUES, SOLUTIONS & DIAGNOSTICS TIPS FOR PERFORMANCE WAREHOUSE (PWH) OF OM DB2PE COMPID 5655OPE00

APAR status

• INTRAN

Error description

• ACTIVATE PERFORMANCE WAREHOUSE:
  
  I. Via ICAT panels to enable PWH, enter storage group name and
     create runtime members.  Recycle OMPE STC.
  
  A.
  KD261MCU        OMEGAMON XE for DB2 PE - Main Menu -
  Option ===> 3
   Perform the following steps in the order presented:
     I  Configuration information (What's New)
     1  Basic product setup (incl. User interfaces)
     2  Configure monitoring profiles
     3  Configure DB2 subsystem monitoring
     4  Complete the configuration
   Optional:
     5* Install OMEGAMON subsystem (See Note)
     6  Run migration utility
     V  Overview of the current configuration
  *Note:  Required for special commands - see help for more
  information.
  
  B.
  KD261MC3 OMEGAMON XE for DB2 PE  -DB2 subsystem monitoring menu-
  Option ===> 3
   Perform the following steps in the order presented:
     1  Associate DB2 subsystems with monitoring profiles
     2  Specify port information
        (PE Client and Extended Insight)
     3  Configure Performance Warehouse
     4  Create runtime members (DB2 related)
  
  KD261PW OMEGAMON XE for DB2 PE Performance Warehouse configurati
  Command ===>
  Specify DB2 libraries used by PWH job:
  DB2 load library     ==> hilev.SDSNLOAD
  DB2 exit library     ==> hilev.SDSNEXIT
  Specify storage group and buffer pool to be used for PWH
  database:
  Storage Group          Buffer Pool
  PROCESS          DGOSTG01              _____BP0
  OUTPUT           DGOSTG01              _____BP0
  CONTROL          DGOSTG01              _____BP0
  ROT              DGOSTG01              _____BP0
  ONLINE           DGOSTG01              ___BP32K
  STAT             DGOSTG01              ___BP8K0
  QRY              DGOSTG01              ___BP32K
  ACCS             DGOSTG01              _____BP0
  Specify storage group and buffer pool used for PWH index space:
  Storage group  ==> DGOSTG01     Buffer pool  ==> _____BP0
  
  C.
  KD261MC3 OMEGAMON XE for DB2 PE  -DB2 subsystem monitoring menu-
  RTE: SYSG ----
  Option ===> 4
  
   Perform the following steps in the order presented:
  Date     Time
     1  Associate DB2 subsystems with monitoring profiles
     2  Specify port information
        (PE Client and Extended Insight)
     3  Configure Performance Warehouse
     4  Create runtime members (DB2 related)
  
  Submit job in hilev.INSTJOBS(D2#6xxxx)
  
  II. ICAT "Complete the Configuration", Step I3  - Complete
      Performance.Warehouse.configuration (If applicable)
  
  Requirements:
  - Performance Warehouse is enabled
  - The started task userid must be DB2PM or it must be
    associated to a groupid DB2PM (see Configuration &
    Customization Guide for details)
  - Your z/OS is configured to support "started jobs" (see
    Configuration & Customization Guide for details)
  
  Objectives:
  The required DB2 privileges to create and maintain the
  Performance Warehouse database are granted to the userid/groupid
  DB2PM.  Afterwards, the Performance Warehouse database is
  created and the Performance Warehouse 'started job' is made
  executable.
  
  Required authorization:
  - UPDATE privilege on the started tasks PROCLIB (For example,
    SYS1.PROCLIB)
  - SYSADM authority on the DB2 subsystems for which Performance
    Warehouse is activated.
  - If necessary (See d), privileges to create a new user ID in
    your security system (For example, RACF)
  
  Description:
  To complete the Performance Warehouse configuration perform
  the following steps. All listed members can be found in the
  library TSDB.SCHAN.DB510.SP22.RKD2SAM.
  
  III. Upgrading the Performance Warehouse
  
  If you created a Performance Warehouse for the earlier version,
  you must manually upgrade it for version 5.1.0. No tool is
  available to perform this function.  Refer to Customization &
  Configuration guide, page 164, Upgrading the Performance
  Warehouse
  
  Before you begin
  
  If you start with the new version of Performance Warehouse, you
  do not have to upgrade. Instead, do the following:
  v Delete the existing Performance Warehouse database DB2PM from
    the old version and drop the plan DB2PM with its packages.
  v If Performance Warehouse is enabled in the configuration, the
    OMEGAMON Collector of the new version automatically manages
    the bind of its packages in the plan DB2PM and creates the
    Performance Warehouse tables.
  
  If you created a Performance Warehouse for the earlier version
  and want to use existing process definitions and executions, or
  the data stored in Accounting and Statistics tables in the new
  version, you must manually upgrade it for version 5.1.0.
  You must perform unload and load steps and you must stop and
  start the OMEGAMON Collector appropriately.
  
  If Performance Warehouse is enabled, the new OMEGAMON Collector
  automatically detects that an old Performance Warehouse is in
  place and the task of the Performance Warehouse server is
  stopped.
  
  FAQ:
  
  Q#1: FPEV5040E  DDT1 PWH FOUND AN INCOMPATIBLE DATABASE DB2PM
  A#1: Drop the existing Performance Warehouse database DB2PM from
  the old version and the plan DB2PM with its packages by entering
  the dollowing DB2 CLP command:
        DB2 DROP DATABASE DB2PM
  Additional please verify the definition for Performance
  Warehouse via ICAT.  Run the BIND job (OMBDssid
  in rhilev.RKD2SAM) and restart the OM collector.
  
  e.g.
  RKD2SAM(OMBDdb2id)
  .
  BIND      PACKAGE   (KO2OM510)       +
  OWNER     (DB2PM)        +
  MEMBER    (FPE@TCO1)       +        /* OMPE v510 above only */
  EXPLAIN   (NO)             +
  ACTION    (REPLACE)        +
  VALIDATE  (BIND)           +
  ENCODING  (EBCDIC)         +
  ISOLATION (UR)
  
  NOTE: With OMPE V510 more DBRMS (and also one specific to DB2
  vA10, FPE@TCO1) were added to the package.
  
  Q#2: FPEV5031S  DSNS PWH IS NOT STARTED WITH USERID DB2PM OR IS
  NOT MEMBER OF GROUP DB2PM .
  A#2:  As background info: DB2PM is currently the hardcoded
  qualifier and owner for the Performance WareHouse database,
  tablespace, and tables.  Therefore everything within the Data
  Collector address space has to go via DB2PM authorization.  This
  can be reached by STC UID = DB2 PM or by having the STC UID
  connected to the RACF group DB2PM.
  
  OMPE/OMPM uses SET CURRENT SQLID to switch to DB2PM, which means
  either the started task UID has to be DB2PM or the start task
  userid has to be allowed to change the CURRENT SQLID to DB2PM as
  his secondary authorization ID.
  The latter can either be done by:
  - assigning SYSADM to the started userID (which is usually
    not the intention at customers),
                     or
  - to communicate to DB2 the secondary authid DB2PM.
    Note: As long as the started task UID is not a LOGON uid
    SYSADM isn't a dangerous as if it would be LONGON uid in
    addition.
  
  DB2 authorization can be defined via DB2 GRANTS or completely
  via RACF using specific DB2 RACF resources. However when using
  DB2 GRANTS, user might want to group and assign authorization
  for certain user groups if not using GRANT to PUBLIC for almost
  everything. This grouping is done via RACF normal groups. The
  way DB2 gets the secondary authid  (=RCAF groups) is through the
  DB2 exit program (at least, we don't know of others).  If you
  don't want to use the (long) RACF group list returned by the
  DB2 Security User Exit,(because of performance reasons) you will
  still need to adapt DB2 User Exit program so that it will return
  of DB2PM (e.g. hardcoded), at least, as a secondary authid.
  
  Q#3: FPEV0275E MSTR ERROR WHEN PREPARING PE SERVER SUBTASK.
  MONITORING FOR
  DB2 SUBSYSTEM DBD1 IS DISABLED
  A#2:  Please refer to Info APAR II14607 via ICAT panels to
  enable PWH, enter Storage Group name and create runtime members.
  Recycle OMPE STC.
  
  APARs/PTFs RELATED TO PERFORMANCE WAREHOUSE ISSUES:
  
  V410:
  - PK81696 / UK45032 (F903) PE AGENT DOESN'T WORK SINCE
    DB2PM.PARAMETER TABLE IS NOT UPDATED
  - PK85843 / UK46961 (F906) SUPPORT FOR UP TO 100 USER SECONDARY
    IDS WHEN CHECKING MONITOR 1 AND 2 PRIVILEGES.
  - PK86084 / UK46872 (F906) ABEND0C4 and ABEND0C1 due to storage
    overlay while SQLPA is active and DB2 switch is done from
    information line
  - PK83978 / UK47482 (F906) PWH .JOBSIN DYNAMIC ALLOCATION ERROR
    IN NON-SMS ENVIRONMENT
  - PK94696 / UK50782 (F910) FPEV5010S SSID DB2 CONNECTION FAILED
  - PK95317 / UK50746 (F910) KO2PWHCB+B0A ABEND0C1 WILD BRANCH
    LEADS TO RECOVERY LOOP WHEN SWITCHING DB2 MULTIPLE TIMES USING
    INFOLINE
  - PK97976 / UK55307 (F003) User of PE Client is not able to
    start SQL Activity Trace due to FPEV6814I message
  - PM26124 / UK62248 (F011) INVALID PROCESSING OF QXSTLOBV
    QXCASCDP QXSTXMLV(V420) in ACCOUNTING REPORT ,SAVE, AND
    PDB/PWH's DB2PMSACCT_GENERAL  TABLE
  
  V420:
  - PK94696 / UK50783 (F910) FPEV5010S SSID DB2 CONNECTION FAILED
  - PM06123 / UK54059 (F002) VARIABLE LONG NAMES OUT OF THE
    PACKAGE SECTION (E.G. PRIMAUTH / ORIGAUTH) CANNOT BE LOADED
    CORRECTLY TO PDB/PWH.
  - PM11788 / UK56310 (F004) KO2O1949E MESSAGE RETURN CODE
    FFFFFF98 REASON CODE 028C WHEN TRYING TO ACCESS SQLPA REPORTS
    FROM OMPE CLASSIC
  - PM13390 / UK57494 (F006) GARBAGE CREATED IN PRIMAUTH OR
    ORIGAUTH OR CLIENT_ENDUSER FIELD OF ACCOUNTING FILE
  - PM17339 / UK59001 (F008) =HIPER DGOVM002+112A ABEND23E-08
    FPEV0002S NUMBER 282,CODE 8 FPEV0002S NUMBER 58,   CODE 8
  - PM20091 =CLOSED PER SQLCODE 229 WITH LC_CTYPE=UNI
    ...PROBLEM SUMMARY:
       Updated agent now available:
  http://www-01.ibm.com/support/docview.wss?rs=434&uid=swg27013147
      ...the download file is db2pe.client.v4.1.0.1.861.zip
  - PM26124 / UK62249 (F011) INVALID PROCESSING OF QXSTLOBV
    QXCASCDP QXSTXMLV(V420) IN ACCOUNTING REPORT ,SAVE, AND
    PDB/PWH'S DB2PMSACCT_GENERAL  TABLE
  - PM32948 / UK66060 (F103) USER-DEFINED STORED PROCEDURES UNDER
    DB2PM OWNERSHIP CAUSE ERRORS DURING PWH DATABASE
  - PM11304 / UK66456 (F104) TS DB2PM.PROCESS is left in CHKP
    status during PWH 4.2 upgrade w causes SQL -204 error
  
  V510:
  - PM32662 / UK66061 (F103) PWH RECEIVES SQLCODE -311 DURING
    INITIAL CREATION DUE TO ONE ROT (RULE-OF-THUMB) NOT BEING
    CREATED AT RUN TIME
  - PM32948 / UK66061 (F103) USER-DEFINED STORED PROCEDURES UNDER
    DB2PM OWNERSHIP CAUSE ERRORS DURING PWH DATABASE
  - PM55589 / UK78194 (F204) GETTING MULTIPLE ROWS PER DAY FOR DB2
    SYSPARMS
  - PM76269 / UK90059 (F212) PERFORMANCE WAREHOUSE ENTERS LOOP
                      WITH ABENDS S301 AFTER INITIAL ABEND S202
  
  V510:
  - PM76269 / UK90058 (F212) PERFORMANCE WAREHOUSE ENTERS LOOP
                      WITH ABENDS S301 AFTER INITIAL ABEND S202
  
  MARKET REQUIREMENT:
  
  There is currently an open FITS requirement MR1007083359 to
  address both bind output and DDL externalization, which is still
  being analyzed to determine its implications, and is most likely
  a long ways off in the short turn.
  TITLE: Performance Warehouse DDL Externalization
  DESCRIPTION: Omegamon Performance Warehouse automatically
  generates Database definitions and Binds when activated. A
  fairly large amount of work is done on initial activation and
  minor changes are done when maintenance is periodically applied.
  Quite a bit of work is done to set up some special jobs and
  Security profiles. It tends to violate several Mainframe
  oriented guidelines where we usually want to exert more control
  over what is installed into our systems.
  
  WORKAROUND: Please contact L2 supporter.
  
  
  WEB SITE LINKS:
  
  http://publib.boulder.ibm.com/epubs/pdf/ko2ccc10.pdf
  /* OMPE/PM v510 Configuration and Customization
     Refer to Upgrade the Performance Warehouse at
     page 164 to migrate from ompe v420 to v510
     page 179 to migrate from ompe v410 to v510 */
  
  http://www.redbooks.ibm.com/abstracts/sg247224.html?Open
  /* A Deep Blue View of DB2 Performance IBM Tivoli OMEGAMON XE
     for DB2 Performance Expert on z/OS */
  
  http://www-1.ibm.com/support/docview.wss?uid=swg21171060
  /* Where does the JCL for the PWH reside? */
  
  https://w3.tap.ibm.com/w3ki/download/attachments/2772861/IDUG+NA
  2010+-+F13+Presentation+Petras+Wilkinson+%283%29.ppt?version=1
  /* How a Performance Database Can Help Save The Day */
  Note: Accounting / Statistics Source in RKO2SAMP
  

Local fix

• IBM Tivoli OMEGAMON XE for DB2 Performance Expert 5655OPE00
  

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels