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: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
Note: You 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, 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]
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.