IBM Support

PH35202: SERVER USING ENABLE_DBTXLOG_PEERLOCKING=TRUE FAILS TO START IF THE TRANSACTION LOG TABLES ARE EMPTY

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

  • After applying PH10643 with ENABLE_DBTXLOG_PEERLOCKING=TRUE,
    the server will not start if the transaction log tables are
    empty (WAS_COMP_LOG, WAS_PARTNER_LOG, WAS_TRAN_LOG). If there
    are records in these tables or the tables don't exist then the
    server starts correctly.
    This condition will only occur if the tables were manually
    created or records were deleted by an administrator.  Normal,
    logically empty, logs will contain meta-data records and are
    not affected by this issue.
    

Local fix

  • If uncheck the enable_dbtxlog_peerlocking parameter the servers
    start normally.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server storing transaction and              *
    *                  compensation logs in a relational           *
    *                  database.                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server startup    *
    *                      fails with CWRLS0029W when the          *
    *                      transaction log tables are empty.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When transaction logs are stored in a relational database and
    the alternate locking scheme introduced in APAR PH10643 is
    enabled by setting ENABLE_DBTXLOG_PEERLOCKING=TRUE, the
    recovery log service will fail to recover the logs if the data
    for a recoverable unit with RUID=-1 does not exist.
    

Problem conclusion

  • The WebSphere Application Server Transaction Log component is
    modified to correctly process empty log tables.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.20 and 9.0.5.9. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH35202

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-10

  • Closed date

    2021-05-12

  • Last modified date

    2021-05-12

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
13 May 2021