Re: OUI not starting tools

From: <fitzjarrell_at_cox.net>
Date: 3 Feb 2005 10:50:33 -0800
Message-ID: <1107456633.568241.77870@f14g2000cwb.googlegroups.com>

Oxnard wrote:

> DB 9iR2 OS AIX 5.2.0.0
>
>
> I would like to have OUI not start additional tools such as Netca

when it is
> started from runInstaller. Is there something like: > ./runInstaller -NoAdditionTools

Listed below are your available options, and their usage:

-help Displays above usage.
-silent For silent mode operations, the inputs can be a response
file

             or a list of command line variable value pairs.
-responseFile <Path>

             Specifies the response file and path to use.
-formCluster

             To install the Oracle clusterware in order to form the cluster.
-remoteShell <Path>

             Used only for cluster installs, specifies the path to the
             remote shell program on the local cluster node.


  -remoteCopy <Path>

             Used only for cluster installs, specifies the path to the
             remote copy program on the local cluster cluster.


  -record -destinationFile <Path>

             For record mode operation, information is recorded in the
             destination file path.


  -deinstall For deinstall operations.

  -debug     For getting the debug information from OUI.

  -ignoreSysPrereqs

             For ignoring the results of the system pre-requisite

checks.
-executeSysPrereqs

             Execute system pre-requisite checks and exit.
-paramFile

             Specify location of oraparam.ini file to be used by OUI.


  -clone     For making an Oracle Home copy match its current

environment.


  -force     Allowing silent mode installation into a non-empty

directory.
-noconsole For suppressing display of messages to console.

             Console is not allocated.
   -removeAllPatches      Remove all interim patches from the home

   -ignorePatchConflicts Ignore all conflicts with existing interim patches during an upgrade. The conflicting interim patches are removed from the home.
-addNode For adding node(s) to the installation.
-removeHome For removing homes from the OUI inventory.

Command Line Variables Usage
  Command line variables are specified using <name=value>; for example:     [ session: | compName: | compName:version: ]variableName=" valueOfVariable"]

   Session/Installer variables are specified using:

          [session:]varName=value
    Ex 1: session:ORACLE_HOME_NAME="OraHome"     Ex 2: ORACLE_HOME_NAME="OraHome"
   The lookup order is session:varName then just varName).      The session prefix is used to avoid ambiguity.

   Component variables are specified using:

          [compInternalName:[Version:]]varName

    Ex 1: oracle.comp1:1.0.1:varName="VarValue"
    Ex 2: oracle.comp1:varName="VarValue"
    Ex 2: oracle.comp1:varName="VarValue"
   The lookup order is compInternalName:Version:varName,
     then compInternalName:varName, then just varName.

There is, apparently, no option to prevent any of the assistants from running.

David Fitzjarrell Received on Thu Feb 03 2005 - 12:50:33 CST