IBM Support

PK56762: AUTOMATIC PWH VIEW CREATION FAILS WITH SQL ERROR -204

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • While the Performance Warehouse is automatically updated it
    fails during the bind of the DBRM DGO@VW2 with the following
    error message:
    
    REQUIRED DBRM DGO@VW2 NOT BOUND. BINDING IT
    ****************************************************************
    *********
    DB2 SQL operation failed:
    SQL code ............. : - 204
    Detecting module ..... : DSNXOTL
    PM Server function ... : DGOZVW2
    SQL state ............ : 42704
    SQL error message .... :
    +---------------------------------------------------------------
    --------
    DSNT408I SQLCODE = -204, ERROR: DB2PM.PMRO_ROT_GROUP IS AN
    UNDEFINED NAME
    This error message is caused by the CREATE statement of the PWH
    view DB2PM.PMRO_ROT_CLUSTER. If the entries in the PWH table
    DB2PM.MT_VIEW do not have the original order but a sequential
    order instead the creation of the views fail with the error
    message above. With this APAR the design of the MT_VIEW table is
    changed to allow independent access to the correct view creation
    order regardless of the entry order in the table.
    In general the correct order of entries in the MT_VIEW table is
    guaranteed by the PWH Server and only in very rare situations
    this can occur.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   Performance Warehouse users              *
    ****************************************************************
    * PROBLEM DESCRIPTION: While the Performance Warehouse is      *
    *                      automatically updated it fails during   *
    *                      the bind of the DBRM DGO@VW2 with the   *
    *                      following error message:                *
    *                                                              *
    *                      REQUIRED DBRM DGO@VW2 NOT BOUND.        *
    *                      BINDING IT                              *
    *                      *************************************** *
    *                      DB2 SQL operation failed:               *
    *                      SQL code ............. : - 204          *
    *                      Detecting module ..... : DSNXOTL        *
    *                      PM Server function ... : DGOZVW2        *
    *                      SQL state ............ : 42704          *
    *                      SQL error message .... :                *
    *                      +-------------------------------------  *
    *                      DSNT408I SQLCODE = -204, ERROR:         *
    *                      DB2PM.PMRO_ROT_GROUP IS AN UNDEFINED    *
    *                      NAME                                    *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF and restart the Performance   *
    *                 Warehouse started task for the failing DB2   *
    *                 subsystem.                                   *
    ****************************************************************
    PROBLEM SUMMARY:
    This error message is caused by the CREATE statement of the PWH
    view DB2PM.PMRO_ROT_CLUSTER. If the entries in the PWH table
    DB2PM.MT_VIEW do not have the original order but a sequential
    order instead the creation of the views fail with the error
    message above. In general the correct order of entries in the
    MT_VIEW table is guaranteed by the PWH Server and only in very
    rare situations this problem can occur.
    
    PROBLEM CONCLUSION:
    With this APAR the design of the MT_VIEW table is changed to
    allow independent access to the correct view creation order
    regardless of the entry order in the table.
    

Problem conclusion

  • With this APAR the design of the MT_VIEW table is changed to
    allow independent access to the correct view creation order
    regardless of the entry order in the table.
    
    KEYWORDS : DGOZVW2 DGO@VW2 -204 PERFORMANCE WAREHOUSE PWH
    

Temporary fix

  • Start the Performance Warehouse for the failing subsystem in
    force mode after the server was started.
    Operator command:
    /F <OM Server started task name>,F PESERVER,F <subsystem
    id>,PWH=F
    
    This causes the table MT_VIEW to be dropped and recreated with
    the original entry sequence.
    

Comments

APAR Information

  • APAR number

    PK56762

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    410

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-11-19

  • Closed date

    2007-12-13

  • Last modified date

    2017-02-04

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

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

    UK32038

Modules/Macros

  •    DGO@BTCH DGO@CHKB DGO@CONV DGO@CRDP DGO@DTA1
    DGO@DTA2 DGO@DTA3 DGO@DTA4 DGO@DTA5 DGO@DTA6 DGO@DTA7 DGO@EXCP
    DGO@LOAD DGO@MT1  DGO@MT1I DGO@MT2  DGO@MT2I DGO@MT2J DGO@MT2K
    DGO@MT3  DGO@MT3I DGO@MT4  DGO@MT4I DGO@MT5  DGO@MT5I DGO@MT5J
    DGO@PC1  DGO@PC2  DGO@PC3  DGO@PC4  DGO@PRV1 DGO@PRV2 DGO@SAPI
    DGO@SCRD DGO@SDOB DGO@SP   DGO@SQPA DGO@TBL  DGO@TRG  DGO@VW1
    DGO@VW2  DGO@WRPA DGO@WRP2 DGO@WR2C DGO@WSTE DGOVEXCP DGOVSDOB
    DGOVWRPA DGOVWRP2 DGOVWR2C DGOZBTCH DGOZCHKB DGOZCONV DGOZCRDP
    DGOZDTA1 DGOZDTA2 DGOZDTA3 DGOZDTA4 DGOZDTA5 DGOZDTA6 DGOZDTA7
    DGOZLOAD DGOZMT1  DGOZMT1I DGOZMT2  DGOZMT2I DGOZMT2J DGOZMT2K
    DGOZMT3  DGOZMT3I DGOZMT4  DGOZMT4I DGOZMT5  DGOZMT5I DGOZMT5J
    DGOZPC1  DGOZPC2  DGOZPC3  DGOZPC4  DGOZPRV1 DGOZPRV2 DGOZSAPI
    DGOZSCRD DGOZSP   DGOZSQPA DGOZTBL  DGOZTRG  DGOZVW1  DGOZVW2
    DGOZWSTE
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R410 PSY UK32038

       UP07/12/15 P F712

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
04 February 2017