|
Problem IC99052
|
Status: Closed |
ROLLFORWARD DATABASE RETURNS SQL1774N ON HADR DATABSE AFTER SNAPSHOT RESTORE AND DB2INIDB AS MIRROR |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Starting with DB2 v10.1 FP2 usage of an external snapshot backup
image to restore a HADR (primary) database will not longer work.
After restore and 'db2inidb as mirror' any rollforward database
command will result in error SQL1774N.
SQL1774N Table space restore or rollforward cannot be issued on
an HADR primary or HADR standby database.
In the db2diag.log you will see message:
2014-01-08-18.53.15.710102+060 I330298E636 LEVEL:
Error
PID : 6640 TID : 48006090975552 PROC :
db2sysc 0
INSTANCE: db2hadr3 NODE : 000 DB :
HADRDB
APPHDL : 0-10 APPID:
*LOCAL.db2hadr3.140108175315
AUTHID : DB2HADR3 HOSTNAME: DB2HADR1
EDUID : 19 EDUNAME: db2agent (HADRDB) 0
FUNCTION: DB2 UDB, High Availability Disaster Recovery,
hdrCheckDb, probe:18000
MESSAGE : ZRC=0xFFFFF912=-1774
SQL1774N Table space restore or rollforward cannot be
issued on an
HADR primary or HADR standby database.
Following sequence will reproduce the behaviour:
- setup HADR primary and standby database
- on HADR primary
- db2 set write suspend for database
- backup local/system db directory and db container files
using external tools (e.g. tar)
- db2 set write resume for database
- db2stop on HADR primary database server
- restore database from external backup (e.g. tar archive)
- db2start
- db2inidb <DBNAME> as mirror
-> any db2rollforward command will receive SQL1774N
This APAR will ensure 'db2inidb as mirror' resets the HADR
database role to STANDARD.
With database role STANDARD it's allowed to perform the
rollforward operation. Afterwards HADR needs to be configured
again. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.5 FixPack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 version 10.5 FixPack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.01.2014
09.09.2014
09.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
