db2isetup - Start instance creation interface command

Authorization

For root installations, root user authority is required on the system where the command is issued. For non-root installations, you must log on with the user ID that owns the non-root installation.

Root user authority is required on the system where the command is issued.

Required connection

None

Command syntax

Command parameters

-i language-code

Two letter code for the preferred language in which to run the install. If unspecified, this parameter will default to the locale of the current user.

-l logfile

Writes the log to the file name specified. For root installations, the path and filename default to /tmp/db2isetup.log. For non-root installations, the default log file is /tmp/db2isetup_userID.log, where userID represents the user ID that owns the non-root installation.

-t tracefile

The full path and name of trace file specified by tracefile.

-r response_file

Full path and file name of the response file to use. If you plan to use the GUI interface, do not specify this parameter.

-? | -h

Output usage information.

Usage notes

1. The Db2 Instance Setup wizard provides a subset of the functionality provided by the Db2 Setup wizard. The Db2 Setup wizard (which runs from the installation media) allows you to install Db2® database components, do system setup tasks such as DAS creation or configuration, and setup, configure and extend instances. The Db2 Instance Setup wizard provides the same functionality as the Db2 Setup wizard except it does not allow the installation of Db2 database components.
2. The Db2 Instance Setup wizard installs all the required components for the IBM® Db2 pureScale® Feature on any remote hosts if those components were not installed during the instance creation or extension.
3. The executable file for this command is located in the DB2DIR/instance directory. It is available in a typical install, but not in a compact install.
4. db2isetup runs on all supported Linux® and UNIX operating systems.
5. On AIX® 6.1 (or higher), when running this command from a shared Db2 copy in a system workload partition (WPAR) global environment, this command must be run as the root user. .
6. In a Db2 pureScale environment:
   1. The Db2 pureScale instance must be fully stopped on all hosts before being adding or dropping a member or cluster caching facility (CF.)
   2. In silent mode, existing hosts of a Db2 pureScale instance can be used in the following cases (these do not apply to the Db2 Setup wizard):
      • To add a second CF to the Db2 pureScale instance, update one of the existing members into both a CF and member host, or add a new host as a CF.
      • To add another member to the Db2 pureScale instance, update the existing CF into both a CF and member host, or add a new host as a member.
      • You cannot use the db2isetup command to drop a member or CF.
   3. There must always be at least one active CF host in the Db2 pureScale instance.
7. When you are creating a Db2 pureScale instance in a virtual machine (VM), you do not need to specify a tiebreaker disk. If you do not want to specify a tiebreaker disk, you must use inputas the tiebreaker disk option value.