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

DURING DB2HAICU HADR MOVE OPTION, HADR OLD PRIMARY FAILS TO REINTEGRATE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When using the db2haicu move option for HADR instance, old 
Standby will takeover by force and become Primary, but old 
Primary may fail to reintegrate. db2pd -hadr may show Primary 
Disconnected for both. This would happen if clients try to 
connect to the old Primary after the move option is used. Note 
that this is not a split brain however, as clients will not be 
able to successfully connect to old Primray. 
 
In the syslog we may see some hadrV95_monitor.ksh timeouts 
followed by db2V95_start.ksh. 
 
Also in the old Primary's db2diag.log we may see entries noting 
DBBAD and kill commands from db2gcf. 
 
2009-10-09-12.28.18.266428-300 I2763889A552       LEVEL: Severe 
PID     : 864352               TID  : 4888        PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   : SAMPLE 
APPHDL  : 0-20                 APPID: GA030317.GD37.091009170850 
AUTHID  : DB2USER 
EDUID   : 4888                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_rds_common_pre1, 
probe:650 
MESSAGE : Marking DBBAD since DB not active 
DATA #1 : Hexdump, 1 bytes 
0x0780000000EC79F2 : 02 
 
... 
 
2009-10-09-12.30.29.357628-300 I3082585A291       LEVEL: Severe 
PID     : 782408               TID  : 1           PROC : db2gcf 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 1 
FUNCTION: <0>, <0>, <0>, probe:997 
DATA #1 : <preformatted> 
Kill Command: su - db2rtin2; db2_kill;ipclean -a
Problem Summary:
USERS AFFECTED:  All 
 
PROBLEM DESCRIPTION:  please refer to the ERROR DESCRIPTION. 
 
PROBLEM SUMMARY:  please refer to the ERROR DESCRIPTION.
Local Fix:
Use the db2 takeover command instead to perform this maintenance 
routine.
available fix packs:
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 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 first fixed in Fix Pack 2 (s100514.)
Workaround
see LOCAL FIX
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.11.2009
22.07.2010
22.07.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList