IBM Support

PM26858: SQLERROR -206 IN ISPF OLM EXPLAIN FOR THE SELECT SQL STMT WITH MANY COLUMNS IN A ROW WITHOUT BLANKS INSIDE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • SQL statement with long list of columns without blanks inside
    caused SQLERROR -206 for the ISPF OLM EXPLAIN command
    
    SELECT
    NAME,CREATOR,TYPE,DBNAME,TSNAME,DBID,OBID,COLCOUNT,EDPROC,VALPRO
    C,CLUSTERTYPE,CLUSTERRID,CARD FROM SYSIBM.SYSTABLES ;
    
    Line 1 has 72 characters and the list of column names does not
    contain a blank.
    Line 2 continues with column names without a blank separator.
    The missing
    blank in the comma separated list of column names is the
    reason for SQLCODE -206.
    
    Error message :
    
    Module detecting the error . : DGO@YEDY
    DSNT408I SQLCODE = -206, ERROR:  CLUSTERTYPE IS NOT A COLUMN OF
    AN INSERTED
    TABLE, UPDATED TABLE, OR ANY TABLE IDENTIFIED IN A FROM
    CLAUSE, OR IS NOT A COLUMN OF THE TRIGGERING TABLE OF A
    TRIGGER
    

Local fix

  • Put the blanks between the column names
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - Explain                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. For V420 and V510                    *
    *                         EXPLAINing dynamic SQL stmt text     *
    *                         coming from a thread and having many *
    *                         columns in a row without blanks      *
    *                         inside results in SQLCODE -206.      *
    *                      2. For V510 only                        *
    *                         Using OLM Explain option "1 Explain  *
    *                         an existing entry in the plan table" *
    *                         and having a PLAN_TABLE with 58 or   *
    *                         less columns, the following error    *
    *                         occurs: SQLCODE = -206               *
    *                         ERROR: PARENT_PLANNO IS NOT A COLUMN *
    *                         OF AN INSERTED TABLE.                *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    1. For V420 and V510
       EXPLAINing dynamic SQL statement text coming from a thread
       and having many columns in a row without blanks inside
       results in SQLCODE -206.
    2. For V510 only
       Using OLM Explain option "1 Explain an existing entry in the
       plan table" and having a PLAN_TABLE with 58 or less columns,
       the following error occurs: SQLCODE = -206
       ERROR: PARENT_PLANNO IS NOT A COLUMN OF AN INSERTED TABLE.
    
    PROBLEM CONCLUSION:
    Code corrected.
    
    KEYWORDS:
    EXPLAIN THREAD NOBLANK SQLCODE-206
    PLANTABLE-58COLS PARENT_PLANNO
    

Problem conclusion

  • Code corrected.
    
    KEYWORDS:
    EXPLAIN THREAD NOBLANK SQLCODE-206
    PLANTABLE-58COLS PARENT_PLANNO
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM26858

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    420

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-11-16

  • Closed date

    2010-12-14

  • Last modified date

    2011-01-03

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

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

    UK63081

Modules/Macros

  • DGO@TSR1 DGO@TSR2 DGO@YDSQ DGO@YEDY DGO@YE00
    DGO@YE01 DGO@YID0 DGO@YIE0 DGO@YIK0 DGO@YIP0 DGO@YI00 DGO@YKSQ
    DGO@YOCD DGO@YOCI DGO@YOCM DGO@YODI DGO@YOII DGO@YOIM DGO@YOIP
    DGO@YOIS DGO@YOKI DGO@YOPI DGO@YOPT DGO@YOTI DGO@YOTM DGO@YOTP
    DGO@YOTS DGO@YQPT DGO@YX00 DGOMYDSQ DGOMYEDS DGOMYEDY DGOMYEXX
    DGOMYE00 DGOMYE01 DGOMYGED DGOMYGSQ DGOMYID0 DGOMYIE0 DGOMYIK0
    DGOMYINT DGOMYIP0 DGOMYI00 DGOMYKSQ DGOMYKTH DGOMYOCD DGOMYOCI
    DGOMYOCM DGOMYODI DGOMYOHV DGOMYOII DGOMYOIM DGOMYOIP DGOMYOIS
    DGOMYOKI DGOMYOPI DGOMYOPT DGOMYOTI DGOMYOTM DGOMYOTP DGOMYOTS
    DGOMYQPT DGOMYSXI DGOMYX00 DGOYDPC0 DGOYMAIN DGOYPLAN DGOYSERV
    DGOYTSR0 DGOYTSR1 DGOYTSR2
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R420 PSY UK63081

       UP10/12/16 P F012

  • R510 PSY UK63082

       UP10/12/17 P F012

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

Document Information

Modified date:
03 January 2011