DB2 - Problem description
Problem IT37130 | Status: Closed |
Open error on primary log path could lead to forced database shutdown and panic | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
A bad log condition such as below could lead to an unnecessary forced database shutdown and panic MESSAGE : ADM1839W An error occurred while DB2 was writing log data to log file "S0078319.LOG" on path "/DB2/PRD/Logs/NODE0000/LOGSTREAM0000/". The log file is still available on log path "/DB2/PRD/mDb2Logs/NODE0000/LOGSTREAM0000/". DB2 will attempt to use both paths for subsequent log files. In the meantime, check that the specified log path in which the error occurred exists and is accessible. Also check that there is space available in the file system. 2020-01-10-06.24.28.916903-300 I72860372E594 LEVEL: Info PID : 17290 TID : 139850451773184 PROC : db2sysc 0 INSTANCE: db2admin NODE : 000 DB : NOW HOSTNAME: EDUID : 29 EDUNAME: db2loggw (NOW) 0 FUNCTION: DB2 UDB, data protection services, sqlpgoleMergeRCs, probe:100 MESSAGE : ZRC=0x8610000D=-2045771763=SQLP_BADLOG "Log File cannot be used" DIA8414C Logging can not continue due to an error. DATA #1 : Open error on primary path /DB2/PRD/Logs/NODE0000/LOGSTREAM0000/S0078320.LOG | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First fixed in Db2 11.5m4fp0 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First fixed in Db2 11.5m4fp0 * **************************************************************** | |
Comment | |
Upgrade to Db2 11.5m4fp0 or higher | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.06.2021 04.06.2021 04.06.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |