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

IN AN HADR/TSA ENVIRONMENT, DB2HAICU ONLY CREATES DEPENDENCIES AGAINST
NETWORK EQUIVALENCIES NAMED AS "DB2_PUBLIC_NETWORK_X"

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In an automated HADR environment, the db2haicu utility will only 
create dependencies against networks with the name 
"db2_public_network_x". When running db2haicu in XML mode and 
specifying a network name that is not of the form 
"db2_public_network_x" than resource dependencies will not be 
created against it. In order to ensure that dependencies get 
created, the network equivalency should be deleted and 
re-created using the "db2_public_network_x" naming convention or 
alternatively the dependencies can be manually created via the 
"mkrel" TSA native command.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HADR/HA users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5                              * 
****************************************************************
Local Fix:
Manually create dependencies against the network equivalency 
grouping or re-create them using the "db2_public_network_x" 
naming convention.
Solution
Fixed in DB2 version 10.1.0.5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList