DB2 - Problem description
Problem IT06656 | Status: Closed |
WHEN ADD STORAGE TO PRIMARY DATABSE FAILS WITH SQL1051N, LOG ENTRIES OF ALTER AND UNALTER CAUSE STANDBY TO SHUTDOWN | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Commands done on PRIMARY: db2 alter database add storage on '/home/new_storage_path/' When the path is invalid, it failed with error SQL1051N. In this case, this Alter is propagated to STANDBY and Standby fails with the following error messages : 015-01-02-23.53.54.155437+330 I6811062E575 LEVEL: Error PID : 4731 TID : 46912753363264PROC : db2sysc 0 INSTANCE: db2gras1 NODE : 000 DB : STAND1 APPHDL : 0-13215 APPID: *LOCAL.DB2.160824070945 EDUID : 60 EDUNAME: db2redom (STAND1) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:1994 MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH "Storage path does not exist or is inaccessible." DATA #1 : String, 26 bytes /new_storage_path/ 2015-01-02-23.53.54.155843+330 I6811638E688 LEVEL: Severe PID : 4731 TID : 46912753363264PROC : db2sysc 0 INSTANCE: db2gras1 NODE : 000 DB : STAND1 APPHDL : 0-13215 APPID: *LOCAL.DB2.160824070945 EDUID : 60 EDUNAME: db2redom (STAND1) 0 FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:1994 MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH "Storage path does not exist or is inaccessible." DATA #1 : String, 46 bytes Error during storage group file initialization DATA #2 : Pointer, 8 bytes 0x000000020074acd9 DATA #3 : Pointer, 8 bytes 0x0000000200e00080 2015-01-02-23.54.03.938567+330 I6820272E509 LEVEL: Severe PID : 4731 TID : 46927605393728PROC : db2sysc 0 INSTANCE: db2gras1 NODE : 000 DB : STAND1 APPHDL : 0-13215 APPID: *LOCAL.DB2.160824070945 EDUID : 181 EDUNAME: db2agent (STAND1) 0 FUNCTION: DB2 UDB, recovery manager, sqlpReplayMaster, probe:2500 RETCODE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH "Storage path does not exist or is inaccessible." 2015-01-02-23.54.03.990863+330 E6820782E950 LEVEL: Critical PID : 4731 TID : 46927605393728PROC : db2sysc 0 INSTANCE: db2gras1 NODE : 000 DB : STAND1 APPHDL : 0-13215 APPID: *LOCAL.DB2.160824070945 EDUID : 181 EDUNAME: db2agent (STAND1) 0 FUNCTION: DB2 UDB, base sys utilities, sqeLocalDatabase::MarkDBBad, probe:10 MESSAGE : ADM14001C An unexpected and critical error has occurred: "DBMarkedBad". The instance may have been shutdown as a result. "Automatic" FODC (First Occurrence Data Capture) has been invoked and diagnostic information has been recorded in directory "/datagras/db2gras1/sqllib/db2dump/FODC_DBMarkedBad_2015-01-02-2 3.54. 03.939110_0000/". Please look in this directory for detailed evidence about what happened and contact IBM support if necessary to diagnose the problem. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Customer using HADR in DB2 V9.7 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7fp11 * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.01.2015 13.10.2015 13.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.11 |