DB2 - Problem description
Problem IT34177 | Status: Closed |
SLOW DATABASE ACTIVATION. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Database appears to hang during database activation. This problem can be diagnosed by looking at the db2diag.log In the db2diag.log, look for multiple messages similar to this: 2020-08-08-08.57.36.762348-240 I19589E1228 LEVEL: Info PID : 41180 TID : 140735785461504 PROC : db2sysc 0 INSTANCE: dbinst1 NODE : 000 DB : dbname HOSTNAME: db1 EDUID : 7706 EDUNAME: db2loggr (DBNAME) 0 FUNCTION: DB2 UDB, data protection services, sqlpgOpenLogExtent, probe:2164 MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." DIA8411C A file "" could not be found. DATA #1 : String, 19 bytes Log is not found... DATA #2 : Codepath, 8 bytes 19:24:26 DATA #3 : String, 99 bytes extNum / logLocation / logStreamId / callerFlag / logFileName1 / logFileName2 / callerSpecifiedPath DATA #4 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes 100 The last line shows the log file number that was attempted to be deleted. If you are hitting this APAR, you will see a large number of these messages where the log number is incrementing by 1. Although it may seem like the database is hanging when you hit this APAR, this is not a hang. The database will eventually complete activation. It is recommended that you do not force/cancel/kill the database while experiencing this long activation; let the activation complete. If you do not allow Db2 to complete activation, the subsequent activation will experience this same long activation time. On the other hand, if you allow the database to complete activation, the issue is resolved and subsequent activation will not experience this long activation. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * No plan to fix. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * No plan to fix. * **************************************************************** | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.09.2020 14.09.2020 14.09.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |