Solution : https://service.sap.com/sap/support/notes/1308895 (SAP Service marketplace login required)
Summary :
The SAP Note advises on errors related to a full transaction log directory in DB2 systems, highlighting causes like inadequate file system size or archiving issues. It specifically calls attention to configurations under SAP standard settings, including 'BLK_LOG_DSK_FUL' set to 'YES', which halts errors while enabling log file creation attempts every five minutes when facing disk full situations. It warns against deletion of active log files. The possible solutions insist on checking parameters as per related SAP Notes and emphasize increasing the file system size to handle extended transaction logs, alongside ensuring robust mechanisms for managing archive logs and overcoming archiving failures. Additionally, understanding and implementing 'LOGARCHMETH', 'FAILARCHPATH', and 'ARCHRETRYDELAY' settings are crucial for a reliable resolution.
Key words :
<dbname> db2 list history archive log, db2 list history archive log, legacy user exit method, installed db2 udb version 8, logarchmeth1primary log archive method, destinationlogarchmeth2secondary log archive method, prevent disk full errors, log disk full error, blk_log_dsk_fulin sap standard configuration, transaction log full situation
Related Notes :
| 1476792 | DB6: DB transaction log being held by an open transaction |
| 1329179 | DB6: DB2 9.7 Standard Parameter Settings |
| 1293475 | DB6: Transaction Log 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 |