For example, the help topic for the Installation Types page is often a custom help topic created by the installation developer that describes the specific installation types for the product you are installing.Īfter you view an online help topic, choose Navigator from the Tools menu to display the navigator pane. These topics are created by the product developer and describe the screens and dialog boxes specific to the product you are installing. Online help specific to a particular installation. These topics describe the screens and dialog boxes that every Oracle Universal Installer user sees, regardless of the product they are installing. Generic online help provided with every copy of Oracle Universal Installer. Oracle Universal Installer provides two kinds of online help The prerequisite_results.xml file can be reused as an input file for subsequent executions of the checker.ĥ.2.1 Getting Help While Installing Oracle ProductsĪt any time while installing your product, click Help for information about the screens specific to your installation. These files are located in the oraInventory/logs directory. Once the checker is run, results, along with the pre-defined inputs, can be found in the prerequisite_results.xml file. Inputs to the checker are listed in the prerequisite.xml file. This may be useful when you know that the checks themselves are faulty or the environment has already been verified.This is an optional flag though not recommended by Oracle. Use this flag on the command line to ignore all pre-requisite checks. This can be used to verify that the basic pre-requisites have been met before deciding to perform an installation. Use this flag on the command line to perform only the pre-requisite check, without continuing the installation. Note that Oracle Universal Installer will use the file you specify for all operations, including the pre-requisite checks. For example, you may create your own parameters file and use that to operate Oracle Universal Installer. Use this flag to specify the location of the oraparam.ini file to be used. Table 5-1 Command Line Parameters for Pre-Requisite Checks Command Refer to Table 5-1 for a description of the flags to use. Standalone: Checks can be run without completing an installation. For silent installations, Oracle Universal Installer performs as many pre-requisite checks as possible, alerts the user on all errors (if any), and provides the location of the installActions.log file before exiting. Silent Mode: Checks can be run and managed from the command line for a silent installation. Simply run Oracle Universal Installer and all pre-defined pre-requisite checks will be performed. Pre-requisite checking can be performed in the following three ways:Īutomatically: Checks are performed automatically when the user runs the Oracle Universal Installer executable during an installation. All the results are logged in the install Actions.log file. All pre-requisite check parameters must be defined in the oraparam.ini file (or another *.ini file that you define). Specific pre-requisite checks are defined for each operating system on which Oracle Universal Installer runs. Oracle Universal Installer is required to perform all pre-requisite checks defined for the installation before installing any software, whether they are Oracle Universal Installer-specific tests, or tests defined for a specific product. Early detection of problems with the system setup reduces the chances of encountering problems during installation for instance, problems with insufficient disk space, missing patches, inappropriate hardware, and so on. 5.1 Checking Pre-Requisites Before Installationīefore installation, Oracle Universal Installer checks the environment to see whether it meets the requirements for successful installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |