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
R850 PSY
UP
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 November 2021