D Executing the runConfig Command Line Tool

The Command Line tool is typically used to run any of the failed configuration tools of your product(s) under an Oracle home.

The usage to execute the runConfig tool is:

./runConfig.sh OPTION1=value1 OPTION2=value2 ...

where OPTION1, OPTION2, and so on, can be the options discussed in the following section.

Options You Can Specify to Execute runConfig

ORACLE_HOME

This is the absolute location of the Oracle home. All products/top-level components under this Oracle home that have been installed using OUI 10.2 installer are eligible for the ACTION. Products installed using an OUI that is earlier to 10.2 are not eligible for this ACTION.

ACTION

This is a mandatory option. This option can have values such as configure/clone / addnode/addlanguage/deconfigure/patchsetConfigure.

MODE

This is optional, and can have values such as perform/showStatus/listTools. For example, if the value is perform, then that ACTION is performed.

If MODE is absent, the MODE option will assume a default value of listTools.

If the value is showStatus, the status of the last-perform ACTION is displayed to the user.

Examples

Tool1 - Optional    - Failed      Tool2 - Recommended - Succeeded       Tool3 - Optional    - Succeeded

If the value of MODE is listTools, a list of recommended/optional/other tools for the specified ACTION are displayed.

Example

Recommended Tools(1): Tool2       Optional Tools (2): Tool1, Tool3       Other Tools(0):

RESPONSE_FILE

This is optional. This is the absolute location of the response file that is used to overwrite some existing parameters. ComponentID|variable = value, pairs are to be specified in this file per line per variable as:

oracle.assistants.server|var1=true oracle.network.client|var2=orcl

Example

RESPONSE_FILE=/scratch/rspfile.properties

Note:

Secure variables are not stored in the instance aggregate xml files and hence while running runConfig, if any of the configuration tools that you want to run use secure variables, such as passwords, you must supply the value of these secure variables using the RESPONSE_FILE option of runConfig. Otherwise, the tools with secure variables as arguments fail.

INV_PTR_LOC

This is optional. This is the full path of oraInst.loc.

The orainst.loc file contains inventory_loc=<location of central inventory>

inst_group=<>

Example

INV_PTR_LOC=<absolute path of oraInst.loc>

RERUN

This is optional. Possible values are true and false. RERUN has a default value of false. This means that only failed tools or those tolls that were skipped are executed. All those tools that were successfully executed are skipped during the rerun.

RERUN=true will execute all the tools afresh, including the tools that completed successful runs.

Typical Usage of the runConfig.sh

./runConfig.sh ORACLE_HOME=<path of database home> ACTION=configureMODE=perform COMPONENT_XML={encap_emseed.1_0_0_0_0.xml}

runConfig Log Files

The log files for runConfig configActions<timestamp>.log/.err are generated under ORACLE_HOME/cfgtoollogs/oui/.

Executing the configToolFailedCommands Script

During the installation, if any of the configuration assistants fail to run successfully, a configToolFailedCommands script is created in the respective Oracle home directories. If you want to rerun the failed config tools, you can either execute the runConfig tool, or navigate to the configToolFailedCommands script under the corresponding Oracle home location, and execute this script.

Usage: ./configToolFailedCommands