Symptom
Transaction log full issue happens.
Initial analysis following KBA shows that db2acd is holding the oldest transaction log.
You find following error in the db2diag.log.
2022-02-15-16.06.36.166082+330 E4478097800A472 LEVEL: Error
PID : 12345 TID : 17590004216288 PROC : db2acd 0
INSTANCE: db2abc NODE : 000
HOSTNAME: abcde
FUNCTION: DB2 UDB, Administrative Task Scheduler, AtsConnection::connect, probe:200
MESSAGE : ECF=0x82BA00EB=-2101739285
DATA #1 : String, 128 bytes
[IBM][CLI Driver] CLI0129E An attempt to allocate a handle failed because there are no more handles to allocate. SQLSTATE=HY014
2022-02-15-16.06.36.667783+330 E4478098273A1040 LEVEL: Info
PID : 12345 TID : 17589995827680 PROC : db2acd 0
INSTANCE: db2abc NODE : 000 DB : abc
APPID : *LOCAL.db2abc.220214093640
HOSTNAME: abcde
FUNCTION: DB2 UDB, cursor manager, csmDriveFetch, probe:130
MESSAGE : ZRC=0x8136001C=-2127167460=SQLZ_RC_NO_CONNECTION, SQLT_SQLJC
"No connection"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 24
sqlerrmc: 0 * * * * AGENT FORCED
sqlerrp : SQLJCMN
sqlerrd : (1) 0x8136001C (2) 0x0000001C (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 55032
CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol)
[0] 0x0000000000000000 ?unknown + 0x0
[1] 0x0000000000000000 ?unknown + 0x0
Read more...
Environment
- SAP on IBM Db2 for Linux, UNIX, and Windows
- One of the following release version: Db2 9.7, Db2 10.1, Db2 10.5
Keywords
CLI0129E, allocate a handle, no more handles, allocate, SQLSTATE=HY014, ECF=0x82BA00EB=-2101739285 , 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.
SAP Knowledge Base Article - Preview