DB2 - Problem description
Problem IT37021 | Status: Closed |
SNAPSHOT BACKUP FAILED WITH SQL1550N RC 5 | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
SNAPSHOT BACKUP fails randomly in DPF with SQL1550N rc 5, and seemingly whenever there is a LOAD running at the same time. The customer claims that this works in ESE. There is a diag (in ecurep /ecurep/sf/TS005/305/TS005305197/2021-04-15/TS005305197.db2diag. log.20210414.000300) where the only msg from backup is 2021-04-13-17.03.33.997859-240 E283619062E606 LEVEL: Error PID : 39923 TID : 140584190732032 PROC : db2sysc 5 INSTANCE: xxxxx NODE : 005 DB : MARCH APPHDL : 1-45873 APPID: *N1.xxxxxxx.210426173226 AUTHID : MSDB2 HOSTNAME: xxxxxx EDUID : 137891 EDUNAME: db2agntp (MARCH) 5 FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:400 MESSAGE : ZRC=0x8005047B=-2147154821=SQLE_RC_SUSPEND_FAILED "Set Write Suspend failed" DATA #1 : String, 45 bytes Failed to acquire the preventSuspendIO lotch. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to v11.5.7 that has the fix * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to v11.5.7 that has the fix * **************************************************************** | |
Comment | |
upgrade to v11.5.7 that has the fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.05.2021 11.08.2021 11.08.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |