- Installing DB2 UDB Servers
- Prerequisites
- Before You Begin
- Installing DB2 UDB
- Installed Directory Structure
- Considerations in an NIS Environment
- Distributed Installation
- Sample Response Files
- Creating a Response File
- Distributed Installation with a Response File
- Installing DB2 with db2_install
- DB2 UDB Environment Definitions
- DB2 Profile Registry
- Managing the DB2 Profile Registry
- The db2set Command
- Environment Variables
- Hierarchy of the DB2 UDB Environment
- DB2 Administration Server (DAS)
- DAS Process
- DB2 Instances
- Creating the Sample Database
- Using the Command Line Processor (CLP)
- Uninstalling DB2 Products
- Stopping the DAS Instance
- Stopping All DB2 Instances
- Removing the DAS Instance
- Removing DB2 Instances
- Removing DB2 Products
Distributed Installation with a Response File
With a response file, an installation can proceed without intervention. You can configure a CD-ROM drive or hard disk drive to be shared and make the DB2 UDB installation files and response files accessible to the machines where the DB2 UDB product will be installed. To use a response file, use the same installation program as a normal installation with the option to specify a response file. For Windows, execute the following command:
setup /U x:\path\response_file /L y:\path\logfile
You specify a response file with the /U option. The /L option is used to specify the log file for this installation. The default log file is x:\db2log\db2.log (x is the boot drive).
For UNIX, execute the following command:
<DB2 Code>/db2setup -r /path/response_file
Where <DB2 Code> is the location of the DB2 CD-ROM image, either on a network shared CD-ROM or some shared mount point. You specify a response file with the -r option. The log of this installation is written into the /tmp/db2setup.log file.
After the installation and configuration are completed, check the log file for any errors or problems. For Solaris, the log is located in /tmp.