DB2 - Problem description
Problem IT38144 | Status: Closed |
FALSE LOW LOG DISK SPACE WARNINGS IN DB2DIAG.LOG AT DATABASE ACTIVATION | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
Starting from DB2 Version 11.5 Mod Pack 6, on database activation, false warning messages may be printed in the db2diag.log reporting not sufficient disk space is available for primary log files even though disk space is sufficient and database activation succeeds. 2021-08-21-03.32.26..757450+480 I69936074E879 LEVEL: Warning PID : 328976 TID : 143236874566327 PROC : db2sysc INSTANCE: DB2INST1 NODE : 000 DB : DBNAME APPHDL : 0-808 APPID: *LOCAL.DB2INST1.xxxxxx AUTHID : DB2INST1 HOSTNAME: HOST1 EDUID : 3212 EDUNAME: db2agent (DBNAME) FUNCTION: DB2 UDB, data protection services, sqlpCheckFreeSpaceUnderLogPath, probe:1228 MESSAGE : Log path is low on disk space. DATA #1 : String, 82 bytes codepath / logpath / freeSpaceInLogPath / reusableSpace / logSpaceReq / forRename: DATA #2 : Codepath, 8 bytes 1 DATA #3 : String, 41 bytes /opt/DB2PrimaryLog/DBNAME/NODE0000/LOGSTREAM0000/ DATA #4 : unsigned integer, 8 bytes 77815205888 DATA #5 : unsigned integer, 8 bytes 0 DATA #6 : unsigned integer, 8 bytes 107375001600 DATA #7 : Boolean, 1 bytes false ... 2021-08-21-03.32.26..757586+480 E69937532E2981 LEVEL: Warning PID : 328976 TID : 143236874566327 PROC : db2sysc INSTANCE: DB2INST1 NODE : 000 DB : DBNAME APPHDL : 0-808 APPID: *LOCAL.DB2INST1.xxxxxx AUTHID : DB2INST1 HOSTNAME: HOST1 EDUID : 3212 EDUNAME: db2agent (DBNAME) FUNCTION: DB2 UDB, data protection services, sqlpgUseCurrentPath, probe:3170 MESSAGE : ZRC=0x85100084=-2062548860=SQLP_NO_SPACE_FOR_LOG "Not enough space in log path to create log." DATA #1 : String, 52 bytes Not enough disk space is available for primary logs. DATA #2 : DB2PrimaryLogStreamIDType, PD_TYPE_DB2_LOG_STREAM_ID, 2 bytes 0 DATA #3 : String, 41 bytes /opt/DB2PrimaryLog/DBNAME/NODE0000/LOGSTREAM0000/ DATA #4 : unsigned integer, 8 bytes 0 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) ... | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Database activation * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First fixed in 11.5.8.0. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Database activation * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First fixed in 11.5.8.0. * **************************************************************** | |
Comment | |
First fixed in 11.5.8.0. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.08.2021 03.06.2022 03.06.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |