DB2 does not accept new connections while db2diag.log shows log archival to third party vendor in progress
Priyanka Joshi 270003HTNX Visits (2603)
When DB2 archiving a log file to vendor program (for example TSM), if TSM does not respond to DB2 (neither success nor failed), and if the database is deactivating during the "non-response" window, DB2 will get stuck in the deactivting process and hence cannot accept new connections to the database
Please refer the technote :
DB2 does not accept new connections if it is archiving a log file to vendor program and database is deactivating at the same time
Most customers have not run the DEACTIVATE DATABASE command and wonder if their situation still matches this technote.
In such cases, customers should check if they have scheduled any daily service restart type jobs (eg : WAS service restart ) which might trigger termination of all connections from that service (and may be this is the only service/application using db2). This might terminate the last active connection to database causing it to deactivate. A db2diag.log message “DB2 is waiting for log files to be archived” should appear in your db2diag.log at this time.
PID : 10289678 TID : 31265 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB : SAMPLE
EDUID : 31265 EDUNAME: db2loggr (SAMPLE) 0
FUNCTION: DB2 UDB, data protection services, sqlp
MESSAGE : DB2 is waiting for log files to be archived.
Please check if you have any service restart or last connection deactivation at this time (timestamp of above db2diag.log message) from any appl