3321963 - Db2 backup performance issue with LogTS buffer becoming full.

Symptom

You observe performance impact due to the LogTS buffer becoming full during online or incremental backup operations. Some times the SAP system gets stuck in COMMIT processing with all work processes becoming occupied. The issue appears to start as follows.

2023-04-06-19.00.11.213789+000 E29379739A480 LEVEL: Info
PID : 29427268 TID : 158137 PROC : db2sysc 0
INSTANCE: db2sap NODE : 000 DB : sap
APPHDL : 0-34675 APPID: *LOCAL.db2sap.230406190041
AUTHID : DB2sap HOSTNAME: hcld0013
EDUID : 158137 EDUNAME: db2agent (sap) 0
FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1902
MESSAGE : Starting an online db backup.

2023-04-06-19.00.31.621437+000 I29380220A516 LEVEL: Info
PID : 29427268 TID : 201137 PROC : db2sysc 0
INSTANCE: db2sap NODE : 000 DB : sap
APPHDL : 0-9748 APPID: 193.17.50.63.59995.230315062131
AUTHID : SAPsap HOSTNAME: hcld0013
EDUID : 201137 EDUNAME: db2agent (sap) 0
FUNCTION: DB2 UDB, recovery manager, sqlpUploadDirtyPoolEntry, probe:787
MESSAGE : LogTS buffer is full!
DATA #1 : unsigned integer, 8 bytes
0

With 'LogTS buffer is full!' message repeating in the db2diag.log.

Environment

IBM DB2 LUW (DB6) any release

Product

SAP NetWeaver Application Server all versions

Keywords

KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.