IBM Support

LO89540: CHANGE OF DB2 USERNAME COULD LEAD TO RE-SYNC OF ALL USERS.

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

  • Customer changed the DB2 username used to connect to the
    Traveler DB2 database which inadvertantly also changed the
    schema name being used.  The new schema name was created and
    essentially acts as a new database.
    

Local fix

  • NA
    

Problem summary

  • When using Auto Schema on DB2 the schema name used is the
    database user.  Change the user could inadvertantly change the
    schema name being used, therefore creating a new schema.
    

Problem conclusion

  • The IBM Traveler server and documentation has been updated to
    provide sufficient warning in this scenario with corrective
    actions if desired to continue with DB2 user name change.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO89540

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    901

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-05

  • Closed date

    2016-07-10

  • Last modified date

    2016-07-10

  • 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

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R901 PSY

       UP



Document information

More support for: IBM Traveler

Software version: 9.0.1

Reference #: LO89540

Modified date: 10 July 2016