DB2® high
availability instance configuration utility (db2haicu) is a text-based
utility that you can use to configure and administer your highly available
databases in a clustered environment.
db2haicu collects
information about your database instance, your cluster environment,
and your cluster manager by querying your system. You supply more
information through parameters to the db2haicu call,
an input file, or at run time by providing information at db2haicu prompts.
Syntax
db2haicu [ -f XML-input-file-name ]
[ -disable ]
[ -delete [ dbpartitionnum db-partition-list |
hadrdb database-name ] ]
Parameters
The parameters that you pass
to the db2haicu command are case-sensitive, and
must be in lower case.
- -f XML-input-file-name
- You can use the -f parameter to specify your
cluster domain details in an XML input file, XML-input-file-name.
For more information, see: Running DB2 High Availability Instance Configuration Utility (db2haicu) with an XML input file.
- -disable
- A database manager instance is considered configured for
high availability after you use db2haicu to
create a cluster domain for that instance. When a database manager
instance is configured for high availability, then whenever you perform
certain database manager administrative operations that require related
cluster configuration changes, the database manager communicates those
cluster configuration changes to the cluster manager. When the database
manager coordinates these cluster management tasks with the cluster
manager for you, you do not have to perform a separate cluster manager
operation for those administrative tasks. This integration between
the database manager and the cluster manager is a function of the DB2 High Availability
Feature.
You
can use the -disable parameter to cause a database
manager instance to cease to be configured for high availability.
If the database manager instance is no longer configured for high
availability, then the database manager does not coordinate with the
cluster manager if you perform any database manager administrative
operations that require related cluster configuration changes.
To
reconfigure a database manager instance for high availability, you
can run db2haicu again.
- -delete
- You can use the -delete parameter to delete
resource groups for the current database manager instance.
If
you do not use either the dbpartitionnum parameter
or the hadrdb parameter, then db2haicu removes
all the resource groups that are associated with the current database
manager instance.
- dbpartitionnum db-partition-list
- You can use the dbpartitionnum parameter
to delete resource groups that are associated with the database partitions
listed in db-partition-list. db-partition-list is
a comma-separated list of numbers that identify the database partitions.
- hadrdb database-name
- You can use the hadrdb parameter to delete
resource groups that are associated with the high availability disaster
recovery (HADR) database named database-name.
If there are no resource groups that are left in
the cluster domain after db2haicu removes the resource
groups, then db2haicu will also remove the cluster
domain.
Running db2haicu with the -delete parameter
causes the current database manager instance to cease to be configured
for high availability. If the database manager instance is no longer
configured for high availability, then the database manager does not coordinate
with the cluster manager if you perform any database manager administrative
operations that require related cluster configuration changes.
To
reconfigure a database manager instance for high availability, you
can run db2haicu again.
DB2 Version 10.1 for Linux, UNIX, and Windows