Removing entries from the transaction partner log
You 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.
About this task
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. You can establish this by checking the SystemOut.log file.
Note: You can remove transactions from tables that have multiple transactions. Multiple
transaction logs within a single database table influence database deadlocks. If there are issues
with a specific JVM transaction log, you 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]
Note: This topic references one or more of the application server log files. As a
recommended alternative, you can configure the server to use the High Performance Extensible Logging
(HPEL) log and trace infrastructure instead of using SystemOut.log ,
SystemErr.log, trace.log, and
activity.log files on distributed and IBM®
i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace
information using the LogViewer command-line tool from your server profile bin directory. See the
information about using HPEL to troubleshoot applications for more
information on using HPEL.
Procedure
- In the administrative console, click .
- 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 your changes to the master configuration.
- Restart the server in recovery mode.