Solution : https://service.sap.com/sap/support/notes/1293475 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues related to full transaction logs in DB2 UDB Version 8 or higher, with symptoms appearing in SYSLOG, db2diag.log, or as short dumps. Common errors include SQL0964C and ADM1823E, indicating a full log held by an ongoing transaction. This could be due to a high workload or a transaction preventing log reuse. The solutions detailed involve using DB2 diagnostic tools and SQL commands to diagnose and address these issues. Tools like db2 get snapshot and db2pd, alongside SQL statements, help determine the transaction holding the log and provide a pathway for mitigation through COMMIT, ROLLBACK, or FORCE APPLICATION commands.
Key words :
current log number 135pages written 5339method 1 archive status successmethod 1, 3 db2pd command db2pd -db <dbname> -transactions, application handle 23315 occupied log file s0000123, prevent stop sap application servers, identify current open transactions span, db2 system-wide unique id, encounter transaction log full situation, client application = <client_pid> coordinator agent process, 3 db2pd -db <dbname> -transactions -logs, uow_log_space_used descfor db2 udb v8
Related Notes :
| 1493587 | DB6: Use of infinite logging or secondary log files |
| 1476792 | DB6: DB transaction log being held by an open transaction |
| 1329179 | DB6: DB2 9.7 Standard Parameter Settings |
| 1308895 | DB6: File System for Transaction Log is Full |
| 1250466 | DB6: Perform database administration, keeping SAP AS running |
| 1086130 | DB6: DB2 9.5 Standard Parameter Settings |
| 913481 | DB6: Archiving log files with DB2 log file management |
| 899322 | DB6: DB2 9.1 Standard Parameter Settings |
| 584952 | DB6: DB2 UDB Version 8 Standard Parameter Settings |
| 495297 | DB6: Monitoring transaction log |
| 72557 | Logging in DB2 UDB systems |