IBM Support

IT32671: INTERMITTENT DB2 CLIENT AUTHENTICATION ERRORS WHEN USING ODBC XA

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

  • A globally coordinated message flow configured with additional
    instances that uses ODBC XA connections to a DB2 database may
    intermittently fail to authenticate with the DB2 server. The
    following error will be reported if using a client security
    plugin for DB2:
    
    BIP2322E: Database error: SQL State '08001';
    Native Error Code '-30082'; Error Text '[unixODBC][IBM][CLI
    Driver] SQL30082N Security processing failed with reason "38"
    ("INVALID CLIENT CREDENTIAL"). SQLSTATE=08001 '.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and IBM App Connect
    Enterprise V11 using globally coordinated transactions with DB2.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    A globally coordinated message flow configured with additional
    instances that uses ODBC XA connections to a DB2 database may
    intermittently fail to authenticate with the DB2 server. The
    following error will be reported if using a client security
    plugin for DB2:
    
    BIP2322E: Database error: SQL State '08001'; Native Error Code
    '-30082';
    Error Text '[unixODBC][IBM][CLI Driver] SQL30082N Security
    processing failed with reason "38" ("INVALID CLIENT
    CREDENTIAL"). SQLSTATE=08001 '.
    
    The problem is due to an old DB2 XA transaction context being
    used with a new MQ queue manager connection.
    

Problem conclusion

  • The product now removes any XA transaction contexts that are
    associated with a thread when the connection to the queue
    manager is closed.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v10.0      10.0.0.24
    v11.0      11.0.0.12
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32671

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-28

  • Closed date

    2020-12-15

  • Last modified date

    2021-06-11

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]

Document Information

Modified date:
13 June 2021