IBM Support

PH12976: BIND QUERY FAILS WITH REASON: 3. THE STATEMENT TEXT CONTAINS ANERROR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When to do BIND QUERY to get a statement level optimization
    hint, bind query job fails with following message
    DSNT281I  -DL3 BIND QUERY FOR QUERYNO = 68 NOT SUCCESSFUL,
               REASON:  3. THE STATEMENT TEXT CONTAINS AN ERROR
    DSNT290I  -DL3 BIND QUERY COMMAND COMPLETED
    
    Because Db2 uses a wrong application compatibility when
    processing the BIND QUERY, resulting in below error and BIND
    QUERY fails
    
    SQL ERROR CODE -4743  ATTEMPT TO USE NEW FUNCTION WHEN THE
    APPLICATION COMPATIBILITY SETTING IS SET FOR A PREVIOUS LEVEL
    
    Additional Keywords:
    MSGDSNT281I BINDQUERY SQLBINDQUERY ZSA1
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Db2 12 for z/OS users of BIND QUERY                      *
    * who are using new V12 syntax                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Message DSNT281I was issued with                             *
    * REASON: 3. THE STATEMENT TEXT CONTAINS                       *
    * AN ERROR during a BIND QUERY                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply corrective PTF when available                          *
    ****************************************************************
    User ran a BIND QUERY for a SQL statement to do statement
    level optimization hint. The explain for that statement
    worked fine. But the BIND QUERY failed with message
    DSNT281I - BIND QUERY FOR QUERYNO = query-identifier NOT
    SUCCESSFUL, REASON: 3. THE STATEMENT TEXT CONTAINS AN ERROR.
    
    The problem happened because an internal local variable was
    not set correctly.
    
    Additional Keywords:
    MSGDSNT281I OPTHINT OPTHINTS SQLHINT SQLHINTS HINTS
    

Problem conclusion

  • Code has been changed to correct the aforementioned problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH12976

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    C10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-09

  • Closed date

    2019-08-13

  • Last modified date

    2019-09-01

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

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

    UI64721

Modules/Macros

  • DSNXOBNQ
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI64721

       UP19/08/28 P F908

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"12.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 September 2019