Removing entries from the transaction partner log
We can remove entries from the transaction partner log file. To do this, set the REMOVE_PARTNER_LOG_ENTRY custom property for the transaction service on the server that owns the partner log.
As part of the transaction recovery process, the partner log is checked to establish which resources are needed. To remove certain entries from the partner log, such as a resource that no longer exists, set this custom property on the application server that owns the transaction partner log containing the entries we want to remove.
The REMOVE_PARTNER_LOG_ENTRY custom property is effective only when both of the following situations apply.
- The application server is started in recovery mode.
- The application server has no transactions that currently require recovery. We can establish this by checking the SystemOut.log file.
IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .
We can remove transactions from tables that have multiple transactions. Multiple transactions logs within a single database table influence database deadlocks. If there are issues with a specific JVM transaction log, we can remove the specific transaction log entry from the database table utilizing the SQL statement:
DELETE FROM [Transaction Log Table] WHERE SERVER_NAME=[Cell\Node\Server] AND SERVICE_ID=[SERVICE ID value]
Tasks
- In the administrative console, click...
Servers > Server Types > WebSphere application servers > server > [Container Settings] Container Services > Transaction Service > [Additional Properties] Custom Properties.
- Click New.
- Type REMOVE_PARTNER_LOG_ENTRY in the Name field, and in the Value field, type one or more comma-delimited integer recovery IDs to be removed.
- Click Apply or OK.
- Save changes to the master configuration.
- Restart the server in recovery mode.
Restarting an application server in recovery mode Manage transaction logging for optimum server availability Use High Performance Extensible Logging to troubleshoot applications Transaction service custom properties