Only users who belong to this group are able to install or deinstall software on this machine. Use the File Locations screen to enter the stage or source location of your products and the location where you want to install your product.
Specify full paths with directory names not exceeding 32 alphanumeric characters. The following sections provide more information about the fields on this screen. Note: Do not leave any fields empty. Path: Enter the full path of the products. You may also use the Browse button to find the products. The stage location is the centralized location where components have been placed for installations.
It could be a single-CD staging area or a multi-CD staging area which spans across more than one disk. The components are bundled in one stage location and their description file is the products. The Oracle Universal Installer will read this file and provide a list of the components available to be installed. See the examples in the table below. Name: Enter an Oracle home name or select it from the drop-down list.
If you currently do not have a home created on your machine, one is created for you during the installation. The home will have whatever name you enter in the Name field. Oracle homes are identified by name, and the Oracle home name identifies the program group associated with a particular Oracle home, and the Oracle services installed on the associated home. The Oracle home name must be 1 to 16 characters long and can only include alphanumeric characters and underscores. The Oracle home name must not include spaces.
Note: Name field only appears in Windows Platforms. Path: Enter the Oracle home with its full path or select it from a drop-down list of existing Oracle Homes. You may also use the Browse button to choose a directory to install your product.
This location is the destination directory to which the product will be installed. When you have entered the appropriate information, click Next to continue. The Available Products screen appears. Select a product option to install and click Next to continue.
An installation type is a pre-defined component set that automatically selects which components to install. The Installation Types which appear in this screen depend on the list that the install developer had specified when the components were built with the Oracle Software Packager, an installation definition tool which allows you to define the installation characteristics of a component.
Refer to the Oracle Software Packager User's Guide for detailed information about building components. Installation Types are given a name, followed by a description of what is installed when you select the installation type. Examples of Installation Types for a product could be Minimum, Complete, Custom, and Typical, and the order of the types may differ depending on how the installation had been developed.
Examples for the installation types are listed below: Type Definition Minimum Installs required dependee components. Complete Installs all dependee components. Custom Installs end-user selected dependee components. If you choose Custom, a tree listing appears which allows you to specify which dependee components to install.
Typical Installs default dependee components. Note: When the number of Installation Types cannot fit as radio buttons on the screen, you may see a scrollable list of install types instead of radio buttons.
Additional information may be provided through pop-up descriptions or an I button. For a pop-up description of a specific Installation Type, you can move the mouse cursor over the Installation Type and hold it there briefly to display the description.
Click the I button for additional information. When you have chosen the Installation Type, click Next to continue. The screen which appears next depends on the Installation Type you have chosen. Use the Available Product Components screen to select a component or patch to install or to deselect components you do not want to install.
To familiarize yourself with the behavior of the checkmarks next to each component, review the following descriptions before continuing:. If you select this item again, it will be deselected and the item will not be installed. If you select the item after that, the item will return to the selected state. This icon only appears if the item in its current context has not been user-determined.
A component that is to be installed may depend on the installation of other components. If you try to deselect a required component, the following message appears: "This is a required component.
You cannot deselect a required component. For information on the status of the installations, see the Install Status column. Upgrade: Products to be upgraded to a higher version. Installed: Products which are already installed if they are the same version. The Oracle Universal Installer does not install these products. Reinstall: Products which are already installed, but which you have chosen to install again.
Attention: Patches are installable units that have bug fixes for released products and are associated with the component they patch. You can install a patch over a component or a patched component with a lower or equal patch version. Patchsets are top level installable items containing a group of patches. The Product Languages button allows you to select all languages your product will be running in. Note: Changing the language of a product does not affect the installation session's language.
The Oracle Universal Installer runs in the language detected at the operating system level. Refer to "Internationalization and Installation Translations Support" on page for more information changing the language of a product. Click Next to continue. Come for the solution, stay for everything else. Welcome to our community! Hence, the Oracle Universal Installer cannot be run.
Join our community to see this answer! Unlock 1 Answer and 3 Comments. Andrew Hancock - VMware vExpert. Is Oracle home set? You are right, I have created link and now I got other error, that is better already, at least I know what the reason. And I will try to resolve next error. Thank you! Please wait I had the same problem with postcfg and loadjava on the OID installation and saw this the first time on a 9iAS install with loadjava.
Members of this group must have write permissions to the base directory chosen. The following sections describe how to remove products installed using Oracle Universal Installer. A de-installation can be performed before selecting products to install or after a successful installation. For UNIX platforms, at the command line, run the script called runInstaller from the directory where it is stored, which is by default at the same level as the first Oracle home created on that host.
Select the product s you want to remove from the Contents tab of the Inventory panel and click Remove. Oracle homes may also be removed in the same manner. Once an Oracle home has been removed, you can reuse its name and location to install other products. The Remove Confirmation Dialog appears, asking if you want to remove the products and their dependent components.
Click Yes. Oracle Universal Installer warns you of any product dependencies that might cause problems if particular products are removed, and prompts you to confirm the de-installation. Pay special attention to the full list of products being removed before proceeding. Oracle Universal Installer computes this list based on the dependencies of each component.
A top level component is the most important component of an installation. It is the installable product you see at the first installation screen.
You can only install one top level component for each installation session. When you select a specific component for removal, Oracle Universal Installer analyzes the dependency information to determine if there are other components that should be removed along with it. In general, if a component is selected for removal, the following components will be removed with it:. Dependents of the selected component that have no other dependents.
A dependent is a component on which the top level component dependent has a dependency. Not only can you perform command line installations, as described in section "Installing and Using a Response File" , you can also perform command line de-installations. A command line de-installation enables you to remove Oracle products or Oracle homes from your system without using the Oracle Universal Installer graphical user interface. You can choose to display no dialog boxes or prompts to the user, or you can selectively avoid displaying certain dialog boxes that are normally used during a de-installation.
Use the following commands to immediately display the Inventory dialog box, which allows the user to select items for removal without navigating the Oracle Universal Installer startup screen:. For example, on a UNIX machine, enter:. Use the following commands to hide the de-installation confirmation and progress dialog boxes during a command line de-installation:. The following sections describe the different ways that Oracle Universal Installer can be used after installation.
Oracle Universal Installer is installed on your system during the installation of your Oracle products:. For all platforms, the executable file setup.
Oracle Universal Installer is placed under "Independent Products" in the Inventory panel as a "non-Oracle home" product. A runInstaller. When Oracle Universal Installer is first installed and run, it checks for the JRE path the location from which it runs , using the location specified in the oraparam.
Following is the output from the runInstaller -help command, which gives you the full list of command line options and their descriptions, as well as command line variables usage:. If you are starting and stopping Oracle Universal Installer programmatically for example, by invoking Oracle Universal Installer using a response file , you may need to consider the exit codes generated by Oracle Universal Installer and perform a particular action depending on the code Oracle Universal Installer returns.
This feature will not work if Oracle Universal Installer is running in "bootstrap" mode. In this case setup. Oracle Universal Installer will be running in "bootstrap" mode if the following line exists in the oraparam. If you exit without installing any products for example if you exit from the "Welcome" screen , the exit code will be You can copy an existing Oracle home, then configure it for its new environment. This process is called "cloning. Use setup. The -responseFile parameter is optional.
Clone-time parameters may be supplied on the command line or through the response file named on the command line. After cloning is finished, you must run oraInstRoot. When you install or de-install products using Oracle Universal Installer, important information about each installation is saved not only in the inventory, but also in a series of log files, located in the following directory:.
These log files can be used to troubleshoot installation problems. These files are also crucial for removing and configuring the various software components you install on your Windows or UNIX computer. Oracle Universal Installer displays the name and location of the current session's log file on the Install page.
For more information about the log files generated by Oracle Universal Installer, refer to the online help. Pre-requisite checking can be performed in the following three ways: Automatically: Checks are performed automatically when the user runs the Oracle Universal Installer executable during an installation.
Oracle Universal Installer provides two kinds of online help Generic online help provided with every copy of Oracle Universal Installer. Online help specific to a particular installation. Note : Only generic help topics are available in the navigator, or table of contents. Custom help topics can only be accessed by clicking the Help button on the dialogs or windows they describe.
0コメント