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

RUNNING 'DB2HAICU -DELETE' PRODUCES DB2DIAG.LOG ERROR MESSAGES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When running 'db2haicu -delete' in a HADR-TSA setup, the 
following warning message is seen in the db2diag.log: 
 
2013-02-12-15.13.47.589692-300 E3647E320           LEVEL: 
Warning 
PID     : 7393                 TID  : 47788187225856PROC : 
db2haicu 
INSTANCE: inst1                   NODE : 000 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaUIListAllGroups, probe:100 
MESSAGE : Could not find any groups in the cluster.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All db2haicu users                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 FP3                              * 
****************************************************************
Local Fix:
N/A
available fix packs:
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
Fixed in DB2 version 10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.02.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList