IBM Support

PK37826: PWH=YES, SQLCODE -104, DGOZTBL, DSNT408I ILLEGAL SYMBOL. CREATE UNIQUE INDEX DB2PM.UIX_PROCESSGROUP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Performing the function to start the performance warehouse
    user experiences the following:
    DB2Q *****************************************
    DB2Q DB2 SQL operation failed:
    DB2Q   SQL code ............. :   -  104
    DB2Q   Detecting module ..... : DSNHPARS
    DB2Q   PM Server function ... : DGOZTBL
    DB2Q   SQL state ............ :    42601
    SQL error message .... :
     +-----------------------------------------------------------
     |  DSNT408I SQLCODE = -104, ERROR:  ILLEGAL SYMBOL " ". SOME
     |           MIGHT BE LEGAL ARE: <IDENTIFIER>
     |  DSNT418I SQLSTATE   = 42601 SQLSTATE RETURN CODE
     |  DSNT415I SQLERRP    = DSNHPARS SQL PROCEDURE DETECTING ER
     |  DSNT416I SQLERRD    = 502  0  0  -1  101  0 SQL DIAGNOSTI
     |  DSNT416I SQLERRD    = X'000001F6'  X'00000000'  X'0000000
     |           X'FFFFFFFF'  X'00000065'  X'00000000' SQL DIAGNO
     |           INFORMATION
    for the object
    CREATE UNIQUE INDEX DB2PM.UIX_PROCESSGROUP ON
    DB2PM.PROCESSGROUP(PG_CREATOR, PG_NAME) USING STOGROUP   ..
    BUFFERPOOL -
    
    No STOGROUP is specified and no BUFFERPOOL is specified. So, the
    -104 occurs.
    
    The response file:
    HLQ.RKD2PAR(PWHRDB2Q).
    shows:
    *
      INDEXES 1       BP2
      INDEXES 2       SYSGP
    *
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component:                          *
    *                 -   PE Server                                *
    *                 -   Performance Warehouse                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: During start up of Performance          *
    *                      Warehouse (PWH) the storage group and   *
    *                      buffer pool to be used to create        *
    *                      indexes for the PWH tables are read     *
    *                      from the PWH response file. When the    *
    *                      data are not parsed correctly from the  *
    *                      response file the creation of the       *
    *                      indexes fails with SQL code -104        *
    *                      (illegal symbol) or SQL code -204       *
    *                      (undefined name).                       *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF if PWH start up fails with    *
    *                 SQL codes -104 or -204.                      *
    ****************************************************************
    Performance Warehouse start up or migration fails with SQL code
    -104 or -204.
    

Problem conclusion

  • The parser for the PWH response file was corrected and the
    following modifications were implemented.
    
    1. When Performance Warehouse (PWH) is started and creates or
    migrates tables, the storage group and buffer pool used for the
    indexes is written to the server log (SYSPRINT) as supplemental
    info to the existing informational messages FPEV5009I.
    
    2. The OMEGAMON server subtask PESERVER does no longer have to
    be restarted to force PWH to read the index info from the
    response file. Instead, the operator can issue a modify command
    with option PWH=N followed by a command with option PWH=F to the
    Performance Expert Server subtask PWH. During PWH start up in
    force mode the response file is read to parse the index info
    which is then used to create or modify the indexes.
    
    
    KEYWORDS : PERFORMANCE WAREHOUSE PWH SQL -104 -204
               STORAGE GROUP BUFFER POOL INDEXES
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK37826

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-01-22

  • Closed date

    2007-02-22

  • Last modified date

    2007-03-01

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

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

    UK22413 UK22414

Modules/Macros

  •    DGO@DB   DGO@TBL  DGOZDB   DGOZTBL
    

Publications Referenced
GC18963701GC18997900   

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R310 PSY UK22413

       UP07/02/27 P F702

  • R410 PSY UK22414

       UP07/02/27 P F702

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":"310","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":"310","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
01 March 2007