IBM Support

JR63857: PASSWORD MISSING ERROR WHEN CONNECTING TO DB AFTER GETTING A CONNECTION ERROR RUNNING A CDC UTILITY

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

  • The PASSWORD MISSING error occurs because of a CDC bug when
    dmts64 returns the connection data to the utility so it can
    include the user name in the error message. We don't want to
    include the password in this message, so it is erased. The bug
    is the password was being erased directly in the connection info
     object that is used by the instance when creating new
    connections. So the password is missing for all subsequent
    connection attempts. The fix is to make a copy of the connection
     info before erasing the password and the erase the password in
    the copy and return the copy along with the error message.
    

Local fix

  • A) Don't run any target-side CDC utilities. There aren't very
    many - dmchangetablestate, dmset, and dmsupportinfo are the main
     ones
    B) Stop and restart the CDC instance when the Db2Wh connection
    failure happens. This will force CDC to re-obtain the user name
    and password from the secret store on disk.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * This issue might affect you if you are using IDR             *
    * 11.4.0.3-5596 or older as a target engine and you use CDC    *
    * command line utilities with that engine.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The problem occurs if you run a command line utility, and    *
    * for some reason the utility is not able to connect to the    *
    * database (for example, if the database rejects the           *
    * connection request). Any new connection that the CDC engine  *
    * tries to create will then fail until you restart the CDC     *
    * engine.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDR 11.4.0.4-5599 or newer.                       *
    ****************************************************************
    

Problem conclusion

  • Upgrading to IDR 11.4.0.4-5599 or newer resolves the issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR63857

  • Reported component name

    IS CDC DB2 LUW

  • Reported component ID

    5725E30DL

  • Reported release

    B40

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-06-30

  • Closed date

    2021-08-16

  • Last modified date

    2021-08-16

  • 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

    IS CDC DB2 LUW

  • Fixed component ID

    5725E30DL

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B40"}]

Document Information

Modified date:
17 August 2021