The transaction log is either full with a DIA8309C error code, or monitoring of the log space shows the transaction log growing unexpectedly
2019-01-01-01.01.01.521852-300 I44283044E592 LEVEL: Error
PID : 12345 TID : 140574002767616 PROC : db2sysc 0
INSTANCE: db2sid NODE : 000 DB : SID
APPHDL : 0-123 APPID: 10.96.10.1.21162.190103190446
AUTHID : SAPSID HOSTNAME: dbhostname
EDUID : 454 EDUNAME: db2agent (SID) 0
FUNCTION: DB2 UDB, data protection services, sqlpWriteLR, probe:6680
MESSAGE : ZRC=0x85100009=-2062548983=SQLP_NOSPACE
"Log File has reached its saturation point"
DIA8309C Log file was full.
After analysis from KBA 2141933 you find that the oldest application is
This application can be showing in a UOW Waiting or UOW Executing status
You may see that the db2sysc is consuming 100% of the CPU
DB2 10.1 GA through DB2 10.1FP2
DBH_DIAG_LOG_COLLECT, DIA8309C, log full , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.