IBM Support

IT34398: GET DB CFG FOR <DBALIAS> CAN FAIL IF GATEWAY CATALOGS TARGET DB WITH DIFFERENT NAME

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • get db cfg (db2CfgGet/db2CfgCall) can fail with SQL5005C in the
    following setup:
    
    (DB Client)      (Gateway)     (DB Server)
     dbname: C -> dbname:B -> dbname:A
    
    When we connect to C from the Client, then issue "get db cfg for
    c" the request fails:
    
    $ db2 connect to C user db2inst1
    
       Database Connection Information
    
    Database server        = DB2/LINUXX8664 11.1.4.5
    SQL authorization ID   = DB2INST1
    Local database alias   = C
    
    $ db2 get db cfg for c
    SQL5005C  The operation failed because the database manager
    failed to access
    either the database manager configuration file or the database
    configuration file.
    
    Some other Db2 utilities such as IMPORT and EXPORT may also fail
    with
    SQL5005C because they can call db2CfgCall API internally.
    

Local fix

  • Use the same DB alias as DB name.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who use gateway instance to connect target database,   *
    * and catalog db alias different name than db name.            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to Db2 v11.1m4fp6 or later.                   *
    ****************************************************************
    

Problem conclusion

  • This problem is first fixed in Db2 v11.1m4fp6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34398

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-09-29

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

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

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
01 April 2021