How to Complete Grid Infrastructure Configuration Assistant(Plug-in) if OUI is not Available (Doc ID 1360798.1)

In this Document

Purpose

Scope

Details

A. Pre-12.2

B. 12.2

C. 18c

Community Discussions

References

---

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Purpose

This note provides instructions to complete 11gR2/12c Grid Infrastructure configuration assistant(Plug-in) if Oracle Universal Installer session is not available anymore. OUI session can be gone for a number of reasons, i.e. node rebooted, session timed out due to security setting etc.

The note can only be executed after 11.2/12c Grid Infrastructure root script (root.sh or rootupgrade.sh) is finished successfully on all nodes.

Scope

This document is intended for Oracle Clusterware/Oracle RAC Database Administrators and Oracle support engineers.

Details

A. Pre-12.2

1. Verify whether "$GRID_HOME/cfgtoollogs/configToolAllCommands" exists or not, if not, as grid user, create a script file named configToolAllCommands with the following contents, for example:

/ocw/b202/oui/bin/runConfig.sh ORACLE_HOME=/ocw/b202 MODE=perform ACTION=configure RERUN=true $*

Note: in this example new GRID home is /ocw/b202; when creating, replace /ocw/b202 with the real new GRID_HOME path in your environment
If any configuration assistant(Plug-in) finished successfully previously and you'd like to skip it, set RERUN to false before executes it.

2. configToolAllCommands script would require a response file cfgrsp.properties if the configuration involves installing ASM(new installation), or upgrading ASM from a release earlier than 11.2.0.1.0.
The content of the file should be as follows:
(1) If installing ASM: (assuming that the ASMPASSWORD and ASMMONITORPASSWORD will be set to oracle)

oracle.assistants.asm|S_ASMPASSWORD=oracle
oracle.assistants.asm|S_ASMMONITORPASSWORD=oracle

(2) If upgrading ASM from a release earlier than 11.2.0.1.0:(assuming that the ASMMONITORPASSWORD will be set to oracle)

oracle.assistants.asm|S_ASMPASSWORD=                         ==>>>>leave blank
oracle.assistants.asm|S_ASMMONITORPASSWORD=oracle

3. Execute configToolAllCommands as grid user on first node:
If a response file was created in Step 2, execute configToolAllCommands as follows:

$GRID_HOME/cfgtoollogs/configToolAllCommands RESPONSE_FILE=<grid-home>/cfgtoollogs/cfgrsp.properties

Otherwise, execute:

$GRID_HOME/cfgtoollogs/configToolAllCommands

The logfile will be $GRID_HOME/cfgtoollogs/oui/configActions{TIMESTAMP}.log, it should be reviewed to find out whether there's any failures.

If on Windows platform, the syntax will be slightly different, i.e.:
<GI_HOME>\oui\bin\runconfig.bat ORACLE_HOME=<GI_HOME> ACTION=configure MODE=perform RERUN=true $*
 

B. 12.2

For 12.2, use the following:

gridSetup.sh -executeConfigTools -responseFile <responsefile.rsp>

For details, refer to:

A.7.1 Using the Installation Response File for Postinstallation Configuration

C. 18c

For 18c, use the following:

gridSetup.sh -executeConfigTools -responseFile <responsefile.rsp>
(Use the response file created during installation to also complete postinstallation configuration)
For details, refer to:

Using the Installation Response File for Postinstallation Configuration