Where to get oracle universal installer

The prerequisite checks are run as part of the installation process, but can also be run as a separate application. Check the Release Notes or installation guide of the products that you are installing for the required version. Memory Requirements — Memory requirements vary depending on the number of components installed. Check the Release Notes or installation guide for the products that you are installing for details. You may need up to 1 MB for the related inventory files.

When you run Oracle Universal Installer from an NFS-mounted user home, especially for Linux, execute the quota command to check the space availability. Never perform an installation on a user home for which space is allocated based on quota. A series of prerequisite checks are performed only if help is not specified. For OUI to perform the checks, include the -prereqchecker option in the command:. After these checks are performed, the installer exits without installing the product.

Once invoked, the prereqchecker application is opened and uses the oraparam. Beginning with OUI release It is no longer necessary to manually unzip one or more files before invoking the installer.

OUI includes a Java-based launcher, which requires Java 1. The OUI launcher includes the following features:. Installation is the process of choosing products from a release and deploying them in the target directory. There are four modes of installation, which are explained in Modes of Installation.

Deinstallation is the process of removing files, directories, shortcuts, start menu items, and Windows registry entries that were created by the installer. Artifacts that are not known and tracked by OUI are not removed. Cloning is the process of copying an existing installation to a different location while preserving its configuration.

You can install multiple copies of the Oracle product easily on different computers using cloning. As it works, you will see a thermometer that displays the progress of the install:. The install may take up to ten minutes, so just be patient as it loads and links the executables.

You can stop the install by clicking on the stop installation button. When the end of installation screen appears the install is complete and you can click on the exit button to exit the installer. While you can create a database manually, the beginning DBA is really better off letting Oracle handle the internals. In this section, we are going to create a database using the DBCA. However, previous to doing this you may have to set up these environment variables:.

You will see the DBCA welcome screen:. Simply press the next key and we will see the first of several screens that will guide us through the database creation. Here is the first screen:. For the purposes of this chapter we are interested only in the first option, creation of a database. Since this option is highlighted for us already, just click on the next button.

Once you do, you will see the next screen which asks us what kind of database we want to create. Note: Once you are ready to create real databases, you will likely use the?

Creation of a custom database without a template? In our case, we will choose to create a general purpose database. Both are required. This section lists the images associated with an installation. To show advertisements during an installation, specify each image as a separate variable. You can use Oracle Universal Installer to install Oracle products in any of the three following modes:.

Interactive: Use Oracle Universal Installer's interactive mode to use the graphical user interface to walk through the installation, providing information in the installation dialogs when prompted. This method is most useful when installing a small number of products in different setups on a small number of hosts. Suppressed: Use Oracle Universal Installer's suppressed mode to supply the necessary information by using a combination of a response file or command line entries with certain interactive dialogs.

You can choose which dialogs to suppress by supplying the information at the command line when you invoke Oracle Universal Installer. This method is most useful when an installation has a common set of parameters that can be captured in a response file, in addition to custom information that must be input by hand.

Silent: Use Oracle Universal Installer's silent installation mode to bypass the graphical user interface and supply the necessary information in a response file. This method is most useful when installing the same product multiple times on multiple hosts. By using a response file, you can automate the installation of a product for which you know the installation parameters.

For more information refer to Chapter 4, "Customizing and Creating Response Files", for detailed information on using response files and installing in silent mode. When you install both bit and bit Oracle Universal Installer on a bit machine, two different inventories will be created and maintained. However, you cannot install bit software in a bit home, and vice versa. If you are creating a multiple-CD installation on UNIX, you may need to launch runInstaller in the background using the following command:.

By launching runInstaller in the background, you can change your current directory after you launch Oracle Universal Installer, allowing you to eject the CD.

It may also help to launch runInstaller as a foreground process from a different directory. You may want to create a shell script that launches Oracle Universal Installer in the background and then exits. If you choose to create a shell script, remember to also pass all parameters that you passed to the shell script to runInstaller in the event that you wish to install silently using a response file.

Note that temporary files are created for single-CD installations as well. If you still have problems, refer to the documentation links at the end of this topic. In most cases, the following procedure will help with any problems you experience while switching to a second CD-ROM while installing Oracle software.

Change to the root directory of your system and log in as the root user by using the following commands:. If after attempting this procedure you are still having problems, refer to the section on installing from multiple CD-ROMs in the Oracle Database Installation Guide , which is available from the Oracle Technology Network:.

With Oracle Universal Installer, you can install products from the Web. System administrators of large customers who may want to deploy Oracle software to more than one target can use a combination of the Web installation and response file features:. Copy the staging area to a shared file system and make it accessible on the Intranet or a Web server.

Include predetermined response files on the same location. Different groups of users might rely on different response files. Clients run Oracle Universal Installer locally and use the local response file that is mailed or downloaded so they can perform a silent installation. The Web installation capability relies on some guidelines that must be followed at installation development time.

Check your installation guide for your product to see if the installation of your product is certified for Web installation. Start the Oracle Universal Installer locally and point to the location of the products. For example:. The following sections describe special instructions that apply when you are installing certain products on a UNIX system.

If you get an Xlib error or a "Failed to connect to Server" error when you are running Oracle Universal Installer on the Solaris operating system, you need to define the following environment variables on the host computer where you are running Oracle Universal Installer:. On the computer that will display Oracle Universal Installer, enter the following command. This command allows other computers to display information on the computer's monitor:. Various installation operations on the UNIX platform must be performed with root privileges.

For example, you must have root privileges to be able to create the Oracle Universal Installer inventory. If you are installing Oracle Universal Installer for the first time, you will be prompted to run a shell script from another terminal window before proceeding with the installation.

Oracle Universal Installer will prompt the user to run root. Otherwise, users are prompted to run root. Change directory to the Oracle home into which you are currently installing your Oracle software product.

When the script is finished and you are returned to the command prompt, exit from the new terminal window and return to Oracle Universal Installer to continue the installation.

If you are installing a product on a UNIX system, the Installer will also prompt you to provide the name of the group that owns the base directory. You must choose a UNIX group name which will have permissions to update, install, and remove Oracle software. 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.

The Oracle Universal Installer with the -addNode flag is always run on the local node and not on the node s to be added. You can add nodes to an Oracle Clusterware node or an Oracle Real Application Clusters node depending upon whether the node addition is being performed at the Oracle Clusterware layer or the Oracle Real Application Clusters database layer. For more information on adding nodes, see "Installing Cluster Environments". Oracle Universal Installer uses the -attachHome flag to attach an Oracle home to the inventory to set up the Central Inventory or to register an existing Oracle home with the Central Inventory.

You can use attachHome. For more information, see "Creating the Central Inventory". You can use detachHome. Oracle Universal Installer uses the -updateNodeList flag to update the node list in the inventory. For more information, see "Updating the Nodes of a Cluster". The Oracle Universal Installer inventory stores information about all Oracle software products installed in all the Oracle homes on a host, provided the product was installed using Oracle Universal Installer.

The inventory is organized as follows:. For more information on the inventory and the structure of the inventory, see "Oracle Universal Installer Inventory". An Oracle home is the system context in which the Oracle products run. This context consists of the following:. You can use the interactive mode to walk through the installation by providing information in the dialogs when prompted.

This method is useful when installing a small number of products in different setups on a small number of hosts. You can use this mode to supply the necessary information by using a combination of a response file or command line entries with certain interactive dialogs. This is useful when an installation has a common set of parameters that can be captured in a response file, in addition to the custom information that you must enter manually.

You can use this mode to bypass the Graphical User Interface GUI and supply the necessary information in a response file. This method is useful when installing the same product multiple times on multiple hosts.

By using the response files, you can also automate the installation of a product for which you know the installation parameters. For more information on silent installation, see Chapter 3, "Customizing and Creating Response Files". A cluster installation uses Oracle Universal Installer to install software on the nodes of a cluster that are network-reachable and bound together by Oracle Clusterware.

You can use Oracle Universal Installer to extend the Oracle home of a product installation to include additional nodes on the cluster. You need to install Oracle Clusterware for a cluster installation. For more information on cluster installations, see Chapter 5, "Installing Cluster Environments". Cloning of existing Oracle homes Enables you to copy an existing Oracle home to another location and "fix it up" by updating the installation configuration to be specific to the new environment.

Better support for cluster environments Oracle Universal Installer now replicates its inventory to all nodes that participate in a cluster-based installation.