pureScale database snapshot will cache the default storage group
ID on the member the snapshot is run at. If another member drops
the default storage group, the member with the cached storage
group ID will not refresh the ID on subsequent database
snapshots. This results in several severe error messages such as
the messages below:
2018-08-28-09.14.57.449074-300 I48172A631 LEVEL: Severe
PID : 29360408 TID : 262670 PROC : db2sysc 2
INSTANCE: XXXXXXXX NODE : 002 DB :
APPHDL : 2-50320 APPID: *N2.XXXXXXXX.180926213958
AUTHID : XXXXXXXX HOSTNAME: XXXXXXXX
EDUID : 262670 EDUNAME: db2agent (instance) 2
FUNCTION: DB2 UDB, database monitor, sqm___sqlmindb, probe:4013
MESSAGE : ZRC=0x870201A8=-2029911640=SQLB_INV_SG_ID
"Invalid storage group identified found."
DATA #?1 : String, 52 bytes
sqlbGetAllStoragePathsForDefaultSG returned an error
2018-08-28-09.15.48.869614-300 I57648A632 LEVEL: Severe
PID : 5767358 TID : 205578 PROC : db2sysc 1
INSTANCE: XXXXXXXX NODE : 001 DB :
APPHDL : 1-44116 APPID: *N1.XXXXXXXX.180828141549
AUTHID : XXXXXXXX HOSTNAME: XXXXXXXX
EDUID : 205578 EDUNAME: db2agent (instance) 1
FUNCTION: DB2 UDB, buffer pool services,
sqlbGetPathsForStorageGroup, probe:1944
MESSAGE : ZRC=0x870201A8=-2029911640=SQLB_INV_SG_ID
"Invalid storage group identified found."
DATA #?1 : String, 36 bytes
Error occured while retrieving paths
Steps to reproduce:
Member 0: Create new default stogroup
Member 1: Do database snapshot (caches the default stogroup ID)
Member 0: Drop default stogroup
Member 1: Do database snapshot (uses cached stogroup ID which is
now invalid -> error) |
