Component : DB2 Universal Database for Unix / NT -

Solution : https://service.sap.com/sap/support/notes/495297 (SAP Service marketplace login required)

Summary :
To manage and prevent the recurring issue of a full transaction log in SAP systems with DB2 database, referencing SAP Note instructions becomes vital. When the DB2 transaction log fills up, it causes all active database transactions to roll back, pausing database operation momentarily. Notably, from DB2 UDB V7 FixPak 4b onwards, outdated monitoring methods are no longer supported. The solution involves using database snapshot commands like 'db2 get snapshot for database on ' to gather crucial information about log space utilization and transactions holding logs. For diagnosing and resolving issues, details from 'db2 list applications show detail' or snapshots for applications also play a crucial role. The log parameters MAX_LOG and NUM_LOG_SPAN can be adjusted to prevent log full errors, provided their restrictions and functionalities are understood correctly. These adjustments and monitoring are part of proactive database maintenance to ensure continuous system availability and performance.

Key words :
table arfcsdata  [db   log by0=> cli0108e  communication link failure, [ibm][cli driver]cli0108e  communication link failure, reconnectb   log by4=> sql error -99999 performing sel, client application          = <client pid>  coordinator agent process, longer deletes secondary log files automatically, application handle                        = <app handle>  process id, thread id     = <db2agent pid> limitations, log bym=> severe db error -99999, db2 list applications show detailor, sap system issues sql error -99999

Related Notes :

1476792	DB6: DB transaction log being held by an open transaction
1308895	DB6: File System for Transaction Log is Full
1293475	DB6: Transaction Log Full