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 IC62530 Status: Closed

IN THE DB2V95_STOP.KSH SCRIPT IT SHOULD CALL DB2GCF -K (INSTANCE KILL)
INSTEAD OF -D IF INSTANCE CONTROLS HADR DATABASES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
We should in fact not be attempting to do a db2gcf -d 
(essentially a db2stop force) at all in cases where the instance 
is an HADR instance.  (This is due to log archiving issues that 
occur at db2stop force time which may make it more difficult to 
cleanly re-integrate the old Primary). 
 
In db2V95_stop.ksh (db2V97_stop.ksh in v97) the script should be 
modified so that instead of db2gcf -d, a db2gcf -k is called 
(instance kill).  db2gcf -k should be called if this instance is 
controlling HADR databases.  We should leave the same logic as 
now for non-HADR databases.
Problem Summary:
Problem Description: 
IN THE DB2V95_STOP.KSH SCRIPT IT SHOULD CALL DB2GCF -K (INSTANCE 
KILL) INSTEAD OF -D IF INSTANCE CONTROLS HADR DATABASES 
Problem Summary: 
We should in fact not be attempting to do a db2gcf -d 
(essentially a db2stop force) at all in cases where the instance 
is an HADR instance.  (This is due to log archiving issues that 
occur at db2stop force time which may make it more difficult to 
cleanly re-integrate the old Primary). 
 
In db2V95_stop.ksh (db2V97_stop.ksh in v97) the script should be 
modified so that instead of db2gcf -d, a db2gcf -k is called 
(instance kill).  db2gcf -k should be called if this instance is 
controlling HADR databases.  We should leave the same logic as 
now for non-HADR databases.
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem is first fixed in Version 9.7 Fix Pack 1
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.08.2009
21.12.2009
21.12.2009
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList