|
Problem IC63291
|
Status: Closed |
DB2HAICU SEGMENTATION FAULT WHEN SETTING UP LARGE CLUSTER |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When setting up large cluster (for example, contains over 30
partitions) via db2haicu interactive mode, this problem may be
encountered:
.
$db2haicu
Welcome to the DB2 High Availability Instance Configuration
Utility (db2haicu).
You can find detailed diagnostic information in the DB2 server
diagnostic log file called db2diag.log. Also, you can use the
utility called db2pd to query the status of the cluster domains
you create.
For more information about configuring your clustered
environment using db2haicu, see the topic called 'DB2 High
Availability Instance Configuration Utility (db2haicu)' in the
DB2 Information Center.
db2haicu determined the current DB2 database manager instance
isbcuaixp. The cluster configuration that follows will apply to
this instance.
db2haicu is collecting information on your current setup. This
step may take some time as db2haicu will need to activate all
databases for the instance to discover all paths ...
When you use db2haicu to configure your clustered environment,
you create cluster domains. For more information, see the topic
'Creating a cluster domain with db2haicu' in the DB2
InformationCenter. db2haicu is searching the current machine for
an existing active cluster domain ...
db2haicu found a cluster domain called bcudomain on
this machine. The cluster configuration that follows will
apply to this domain.
Segmentation fault(coredump) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users who are using db2haicu to set up large cluster. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When using db2haicu to set up large cluster, you may *
* encounter segmentation fault. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7.0.1 *
**************************************************************** |
| 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 |
The problem was first fixed in version 9.7 fix pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.09.2009
21.12.2009
21.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.0.1,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
