Postinstallation Configuration Using the ConfigToolAllCommands Script

You can create and run a response file configuration after installing Oracle software. The configToolAllCommands script requires users to create a second response file, of a different format than the one used for installing the product.

Starting with Oracle Database 12c Release 2 (12.2), the configToolAllCommands script is deprecated and may be desupported in a future release.

About the Postinstallation Configuration File

When you run a silent or 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 response file mode by using a password response file. The script uses the passwords to run the configuration tools in succession to complete configuration.

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

The configToolAllCommands password response file has the following syntax options:

oracle.crs for Oracle Grid Infrastructure components or oracle.server for Oracle Database components that the configuration assistants configure
variable_name is the name of the configuration file variable
value is the desired value to use for configuration.

The command syntax is as follows:

internal_component_name|variable_name=value

For example:

oracle.crs|S_ASMPASSWORD=PassWord

Note:

If passwords are not specified in the response file or on the command-line, the installer prompts for the applicable passwords during installation.

The database configuration assistants require the SYS, SYSTEM, and DBSNMP passwords for use with Oracle DBCA. You may need to specify the following additional passwords, depending on your system configuration:

If the database is using Oracle Automatic Storage Management (Oracle ASM) for storage, then specify a password for the S_ASMSNMPPASSWORD variable. If you are not using Oracle ASM, then leave the value for this password variable blank.
If you create a multitenant container database (CDB) with one or more pluggable databases (PDBs), then specify a password for the S_PDBADMINPASSWORD variable. If you are not using Oracle ASM, then leave the value for this password variable blank.

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

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

Creating a Password Response File

You can create a password response file and use it with configuration assistants to perform silent installation.

Note:

If passwords are not specified in the response file or on the command-line, the installer prompts for the applicable passwords during installation.

Perform the following steps to create a password response file:

Create a response file that has a name of the format filename.properties, for example:
```
$ touch pwdrsp.properties
```
Open the file with a text editor, and cut and paste the sample password file contents, as shown in the examples, modifying as needed.

Change permissions to secure the password response file. For example:

$ ls -al pwdrsp.properties
-rw------- 1 oracle oinstall 0 Apr 30 17:30 pwdrsp.properties

Example: Password response file for Oracle Grid Infrastructure (grid user)

grid.crs|S_ASMPASSWORD=password
grid.crs|S_OMSPASSWORD=password
grid.crs|S_BMCPASSWORD=password
grid.crs|S_ASMMONITORPASSWORD=password

If you do not have a BMC card, or you do not want to enable IPMI, then leave the S_BMCPASSWORD input field blank.

Example: Password response file for Oracle Grid Infrastructure for a Standalone Server (oracle user)

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

Example: Password response file for Oracle Database (oracle user)

This example provides a template for a password response file to use with the database configuration assistants.

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

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

Running Postinstallation Configuration Using a Password Response File

Complete this procedure to run configuration assistants with the configToolAllCommands script.

Create a password response file as described in Creating a Password File.
Change directory to $ORACLE_HOME/cfgtoollogs.

Run the configuration script using the following syntax:

configToolAllCommands RESPONSE_FILE=/path/name.properties

For example:

$ ./configToolAllCommands RESPONSE_FILE=/home/oracle/pwdrsp.properties