IBM Support

LO90903: DUPLICATE ACCOUNT RECORDS WHERE THE ACCOUNT NAME CHARACTERS ARE IN VARIOUS LETTER CASE ARE NOT IDENTIFIED BY DBACCOUNTSCHECK

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 DbAccountsCheck command can fail to identify
    records that are violating the account table unique index
    constraint. This occurs because the different records have
    fields that are in different letter case, but the database
    server uses a collation that is not case sensitive.
    

Local fix

  • NA
    

Problem summary

  • The IBM Traveler duplicat account repair tool could fail to
    identify and repair a duplicate account if the user name is
    listed twice but with different case.
    

Problem conclusion

  • The IBM Traveler server has been updated to resolve this issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO90903

  • 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-11-18

  • Closed date

    2017-02-10

  • Last modified date

    2017-02-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 #: LO90903

Modified date: 10 February 2017


Translate this page: