3641771 - DB6: SQL0964C  The transaction log for the database is full during online/incremental backup runtime.

During the backup runtime a transaction log full issue occurs.
The db2diag.log shows there is no space available.

2025-08-01-22.40.17.000000000000000000                   LEVEL: Error
PID     : XXXX                TID : 10000000000000       PROC : db2sysc 0
INSTANCE: db2<sid>               NODE : 000              DB   : <SID>
APPHDL  : 0-XXXXX         APPID: *LOCAL.db2<sid>xxxxxxxxxxx
UOWID   : X                    ACTID: XX           
AUTHID  : DB2<SID>               HOSTNAME: xxxxxxxxxxxx
EDUID   : 0000                 EDUNAME: db2agent (<SID>) 0
FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:XXXX
MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
          "Log File has reached its saturation point"
          DIA8309C Log file was full. 

and/or

FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsTask::incrementCurrentInvocation, probe:1000
MESSAGE : ZRC=0xFFFFFC3C=-964
          SQL0964C  The transaction log for the database is full. 

Db2 LUW IBM

reorganisation, activity, maintenance, when to reorg, table, index, large, long running, hours, duration, longer, performance, NUM_LOG_SPAN, MAX_LOG, ROLLBACK, RESTART , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem