B Using Response Files

This appendix describes how to install Oracle Database Vault using a response file. It includes the following topics:

B.1 How Response Files Work

You can automate the installation and configuration of Oracle software by specifying a response file when you start Oracle Universal Installer. Oracle Universal Installer uses the values contained in the response file to provide answers to some or all of Oracle Universal Installer prompts.

Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you effectively eliminate some or all of the installer dialog screens. To completely suppress the graphical user interface session, add the -silent parameter to the runInstaller command.

During a silent mode installation, Oracle Universal Installer does not display any screens. Instead, it displays progress information in the terminal that you used to start it.

You define the settings for a silent mode installation by entering values for the variables listed in the response file. For instance, to specify the Oracle home, you would supply the appropriate value for the ORACLE_HOME variable, as in the following example:

ORACLE_HOME = "/disk$oracle10/home10204"

See Also:

Oracle Universal Installer and OPatch User's Guide for more information about response file formats

B.1.1 Creating the oraInst.loc File

If you plan to install Oracle products noninteractively, then you must manually create the oraInst.loc file, if it does not exist. This file specifies the location of the Oracle Inventory directory where Oracle Universal Installer creates the inventory of Oracle products that are installed on the system.


If Oracle software has been installed previously on the system, then the oraInst.loc file may exist. If the file does exist, then you do not need to create a new file.

To create the oraInst.loc file, follow these steps:

  1. Go to the [.nodename] subdirectory under the SYS$LOGIN directory, which is where the oraInst.loc file must reside.

  2. Set the default directory to the directory that will contain the oraInst.loc file:

    $ SET DEFAULT logindisk:[logindir.nodename]
  3. Use a text editor to create the oraInst.loc file, containing the following lines:


    In this example, oraInventory_location is the location of the Oracle Inventory directory, which is on an ODS-5 volume and is specified in UNIX syntax, and group_id is the group ID of the Oracle Database account. Ensure that the oraInventory_location setting points to the existing inventory of your Oracle Database 10g release 2 ( database installation.

  4. Set the file protection on the oraInst.loc file as follows:

    $ SET FILE/PROT=(S:RWED,O:RWED,G:RWE,W:RE) oraInst.loc

B.1.2 General Procedure for Using Response Files

The following are the general steps to install and configure Oracle products using Oracle Universal Installer in silent mode:


You must complete all required preinstallation tasks on a system before running Oracle Universal Installer in silent mode. See "Configure the Oracle User's Environment".
  1. Verify that the oraInst.loc file is created and exists as described in "Creating the oraInst.loc File".

  2. Prepare a response file.

  3. Run Oracle Universal Installer in silent mode by executing runInstaller.com with the response file listed as a command argument.

B.2 Installing Database Vault Using a Response File

Use the following steps to install Database Vault using a response file:


By default, the oraInst.loc file should be present in the directory described in "Creating the oraInst.loc File". This is because Oracle Database Vault is installed into an existing Oracle Database installation.

B.2.1 Step 1: Prepare the Response File

Oracle Database Vault comes with a response file template (dv.rsp) that you can edit to customize your installation. You can use this response file for silent mode installations.

The dv.rsp file is located in the response directory on the installation media. Use the following steps to copy and modify the response file:

  1. Copy the response file from the response directory to a directory on your system.

    $ COPY kit_device:[Disk1.response]DV.RSP local_directory

    In this example:

    • kit_device is the disk containing your Oracle Database Vault installation kit.

    • local_directory is the path to a directory on your disk.

  2. Open the response file in a text editor:

    $ EDIT [local_directory]dv.rsp

    The response file contains variables that store information required by Oracle Universal Installer. You must set these variable values in the file. For example, you must specify values for the Oracle home location, Database Vault owner name, and other such information required by Oracle Universal Installer.

    The response file contains two parts. You should edit the variables only in the first part. The second part of the file contains preset variables, which must not be edited. This instruction is also provided in the response file.

    Some of the variables are mandatory while others are optional. The mandatory variables must be supplied for a successful installation. Each variable is explained within the response file. Examples are also provided within the response file.

    The following excerpt from the response file shows instructions related to setting the Oracle home variable:

    #Name       : ORACLE_HOME
    #Datatype   : String
    #Description: Complete path of the existing database Oracle
    #             Home into which Oracle Database Vault will be installed.
    #Requirement: 1) Must have Oracle Database Enterprise Edition release 
    #       installed.
    #             2) Cannot contain Oracle Database Vault.
    #Example: ORACLE_HOME = "/dka100/oracle_db1"
    ORACLE_HOME=<Value Required>

    Lines starting with the # symbol are comment entries. If you want to omit an optional variable, you can comment it by adding the # symbol to the beginning of the line. You cannot comment lines containing mandatory variables, such as ORACLE_HOME.

    See Also:

    Oracle Universal Installer and OPatch User's Guide for detailed information on creating response files.
  3. Follow the instructions in the file to edit it. Save and close the file.


    Oracle Universal Installer fails if you do not correctly configure the response file. Refer to Troubleshooting Silent Mode Installation for more information about troubleshooting a failed silent mode installation.
  4. Grant read, write, and execute permissions to the Oracle software owner, but not to any other users.

    $ SET SECURITY/PROTECTION=(O:RWED,S,G,W) response_file.rsp


    A fully specified response file for an Oracle Database Vault installation contains the passwords for database administrative accounts. Ensure that only the Oracle software owner user can view or modify response files or consider deleting them after the installation succeeds.

B.2.2 Step 2: Run Oracle Universal Installer Using the Response File

Now, you are ready to run Oracle Universal Installer at the command line, specifying the response file you created, to perform the installation. The Oracle Universal Installer executable, runInstaller, provides several options.

To run Oracle Universal Installer using a response file:

  1. Complete the preinstallation tasks listed in Chapter 2, "Installing Oracle Database Vault as an Option".

    See Also:

    Frequently Asked Questions in the Oracle Database Vault Release Notes for hp OpenVMS for a checklist of the preinstallation requirements
  2. Log in as the Oracle software owner user (for example, ORACLE).

  3. To start Oracle Universal Installer, enter a command similar to the following:

    $ @kit_device:[Disk1]runInstaller [-silent] -responseFile response_filename


    Do not specify a relative path to the response file. If you specify a relative path, Oracle Universal Installer fails.

    In this example:

    • kit_device is the disk containing your Oracle Database Vault installation kit.

    • -silent indicates that you want to run Oracle Universal Installer in silent mode.

    • responsefilename is the full path and file name of the installation response file that you configured. Provide this path using the OpenVMS syntax.


    For more information about other options for the runInstaller command, enter the following command:
    $ kit_device:[Disk1]runInstaller -help

B.3 Troubleshooting Silent Mode Installation

During a silent installation, Oracle Universal Installer records all the actions that it performs in a log file. If you encounter problems during the installation, review the log file for information about possible causes of the problem.

To view the log file:

  1. Determine the location of the oraInventory directory. This can be found as the value of the inventory_loc parameter in the oraInst.loc file, which is located in the hostname subdirectory of SYS$LOGIN.

  2. Set default to the directory determined in Step 1, and then to the LOGS subdirectory.

  3. Obtain a directory listing to determine the file name of the log file. Installer log files have names similar to the following, where date_time indicates the date and time when your Oracle Database Vault installation started:


    This command lists the files in the order of creation, with the most recent file shown last.

  4. If an error displayed by Oracle Universal Installer or listed in the log file indicates a relinking problem, refer to the following file for more information:


A silent installation fails in the following conditions:

  • You do not specify a response file

  • You specify an incorrect or incomplete response file

  • Oracle Universal Installer encounters an error, such as insufficient disk space

  • The Database Vault installation prerequisites have not been met

Oracle Universal Installer or configuration assistant validates the response file at run time. If the validation fails, the silent mode installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file.