home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84405 Status: Closed

SYSCATSPACE MAY BE PUT IN RESTORE PENDING IF LOAD COPY FILE IS MISSING ON
HADR STANDBY OR DURING ROLLFORWARD

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
On HADR standby or during rollforward, replaying load copy log 
will fail if load copy image file is missing and corresponding 
tablespaces will be put in restore pending. However it's a 
defect that SYSCATSPACE may be put in restore pending in this 
situation. 
 
The following steps can be used to reproduce: 
 
1. Create two range partitioned tables with some overlap in 
their tablespaces 
db2 create tablespace ix1 
db2 create tablespace ts1 
db2 create tablespace ts2 
db2 create tablespace ts3 
db2 create table t1(c1 int not null, c2 varchar(100), primary 
key (c1)) index in ix1 
partition by range ("C1") 
(PART "PART0" STARTING(1) ENDING(300000) IN "TS1", 
PART "PART1" STARTING(300001) IN "TS2", 
PART "PART2" STARTING(600001) ENDING(1000000) IN "TS3"); 
 
db2 create tablespace ts4 
db2 create tablespace ix2 
create table t2(c1 int  not null, c2 varchar(100) , primary key 
(c1)) index in i 
x2 partition by range ("C1") (PART "PART0" STARTING(1) 
ENDING(300000) IN "TS4", 
PART "PART1" STARTING(300001) IN "TS2", PART "PART2" 
STARTING(600001) ENDING(100 
0000) IN "TS3") 
 
2. Load tables on Primary 
[i] DB2_LOAD_COPY_NO_OVERRIDE=COPY YES to /tmp/load 
db2 load from 1m.out of del replace into t1 copy no 
db2 load from 1m.out of del replace into t2 copy no 
 
Please note the copy image file is not accessible from the 
standby. 
 
3. Replaying on Standby fails and SYSCATSPACE is put in restore 
pending. 
MESSAGE : Load copy image restore terminated with rc -3785 
 
2011-08-17-12.15.21.821289-600 I152258A453        LEVEL: Warning 
PID     : 1097968              TID  : 6989        PROC : db2sysc 
0 
INSTANCE: db2ins21             NODE : 000         DB   : HADR 
APPHDL  : 0-3804               APPID: *LOCAL.DB2.110817221500 
EDUID   : 6989                 EDUNAME: db2redom (HADR) 0 
FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0 
DATA #1 : String, 53 bytes 
 
Following tablespace does not exist. TS ID: 65535, 0 
 
2011-08-17-12.15.21.828206-600 I152712A438        LEVEL: Warning 
PID     : 1097968              TID  : 6989        PROC : db2sysc 
0 
INSTANCE: db2ins21             NODE : 000         DB   : HADR 
APPHDL  : 0-3804               APPID: *LOCAL.DB2.110817221500 
EDUID   : 6989                 EDUNAME: db2redom (HADR) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpRFWppl, probe:870 
MESSAGE : Tablespaces taken offline due to failed load recovery. 
 
2011-08-17-12.15.21.828377-600 I153151A437        LEVEL: Warning 
PID     : 1097968              TID  : 6989        PROC : db2sysc 
0 
INSTANCE: db2ins21             NODE : 000         DB   : HADR 
APPHDL  : 0-3804               APPID: *LOCAL.DB2.110817221500 
EDUID   : 6989                 EDUNAME: db2redom (HADR) 0 
FUNCTION: DB2 UDB, recovery manager, sqlpRFWppl, probe:870 
DATA #1 : <preformatted> 
Tablespace 0 in restore pending state. 
 
The HADR standby will fail to start once SYSCATSPACE is put 
in restore pending state.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
Make sure that load copy file is available before activating the 
standby
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
20.11.2012
20.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList