Postinstallation Configuration Using Response File Created During Installation

To run a response file configuration after installing Oracle software:

About the Postinstallation Configuration File
When you run a silent or a response file installation, you provide information about your servers in a response file that you otherwise provide manually during a graphical user interface installation.
Running Postinstallation Configuration Using Response File
Use this procedure to run postinstallation configuration using response file.

About the Postinstallation Configuration File

When you run a silent or a response file installation, you provide information about your servers in a response file that you otherwise provide manually during a graphical user interface installation.

However, the response file does not contain passwords for user accounts that configuration assistants require after software installation is complete. The configuration assistants are started with a script called configToolAllCommands. You can run this script in the response file mode by using a password response file. The script uses the passwords to run the configuration tools in succession to complete the configuration.

If you keep the password file to use for clone installations, then Oracle strongly recommends that you store it in a secure location. In addition, if you must stop an installation to fix an error, you can run the configuration assistants using configToolAllCommands and a password response file.

The configToolAllCommands password response file consists of the following syntax options:

internal_component_name is the name of the component that the configuration assistant configures
variable_name is the name of the configuration file variable
value is the desired value of the configuration.

The command syntax is as follows:

internal_component_name|variable_name=value

For example:

oracle.crs|S_ASMPASSWORD=myPassWord

Oracle strongly recommends that you maintain security with a password response file:

Permissions on the response file must be set to 600.
The owner of the response file must be the installation owner user, with the group set to the central inventory (oraInventory) group.

Running Postinstallation Configuration Using Response File

Use this procedure to run postinstallation configuration using response file.

To run configuration assistants with the executeConfigTools script:

Create a response file using the syntax filename.properties. For example:
```
C:\> copy nul cfgrsp.properties
```
Open the file with a text editor, and cut and paste the password template, modifying as needed.
Secure the cfgrsp.properties file by changing permissions in Properties page. Right-click the file to open the Properties page. Select the Security tab, click the Edit button, select a group or user, then select Deny check box against Read permissions to remove read access for unwanted users.
Change directory to ORACLE_HOME\cfgtoollogs
Before running configToolAllCommands, rename it using the following command:

copy configToolAllCommands configToolAllCommands.bat
Run the configuration script using the following syntax:

configToolAllCommands.bat RESPONSE_FILE=\path\name.properties

for example:
```
C:\> configToolAllCommands.bat RESPONSE_FILE=C:\oracle\cfgrsp.properties
```

Example C-1 Password response file for Oracle Grid Infrastructure for a Standalone Server

Oracle Grid Infrastructure requires passwords for Oracle Automatic Storage Management Configuration Assistant (ASMCA), and for Intelligent Platform Management Interface Configuration Assistant (IPMICA) if you have a BMC card and you want to enable this feature. Provide the following response file:

oracle.crs|S_ASMPASSWORD=password
oracle.crs|S_ASMMONITORPASSWORD=password
oracle.crs|S_OMSPASSWORD=password
oracle.crs|S_BMCPASSWORD=password
oracle.crs|S_WINSERVICEUSERPASSWORD=password

Example C-2 Password response file for Oracle Database

Oracle Database configuration requires the SYS, SYSTEM, and DBSNMP passwords for use with Database Configuration Assistant (DBCA). The S_ASMSNMPPASSWORD password is necessary only if the database is using Oracle ASM for storage. Similarly, the S_PDBADMINPASSWORD password is necessary only if you create a multitenant container database (CDB) with one or more pluggable databases (PDBs). Also, if you select configure Oracle Enterprise Manager, then provide the password for the Oracle software installation owner for the S_EMADMINPASSWORD password.

oracle.server|S_SYSPASSWORD=password
oracle.server|S_SYSTEMPASSWORD=password
oracle.server|S_DBSNMPPASSWORD=password
oracle.server|S_PDBADMINPASSWORD=password
oracle.server|S_EMADMINPASSWORD=password
oracle.server|S_ASMSNMPPASSWORD=password

If you do not want to enable Oracle Enterprise Manager or Oracle ASM, then leave those password fields blank.