From 11gR2 onward the "-record" option is no longer supported. Instead, the final OUI screen before starting the installation always gives you the option of saving a response file.
The response files are quite large, containing a large number of parameters and comments. The following files are examples of response files from different Oracle Database versions. A silent installation is initiated using the following command.
The "-silent" parameter indicates that this is a silent installation and the "-responseFile" parameter defines the name and location of the response file. Some useful "runInstaller" flags include the following. About Response Files Before doing a silent installation, you must provide information specific to your installation in a response file for example, the installation directory. Running the Oracle Universal Installer in Silent Mode Follow these instructions to run the Oracle Universal Installer in silent mode and to set up your Oracle central inventory for the first time.
Response files are text files that you can create or edit in a text editor. Creating a Response File Oracle recommends using your product graphical installer or deinstaller to create a response file that you can use to silently install or deinstall your product. Sample Response Files The provided sample response files show you the parameters that can be included in a response file for a silent installation or deinstallation.
Run your product graphical installer or deinstaller, as described in your product installation guide. For product installation, on the Installation Summary screen, click Save Response File to save your installation parameters to a response file.
Summary of the Silent Installation Syntax and Commands To run the product installer from the command line, make sure that you understand the syntax and various command line options you can use for your installation.
This is the default operation. Only one operation can be specified. As a result, you see a prompt similar to the following example: You are starting your first installation on this host or you do not have sufficient permission to access current inventory. As part of this install, you need to specify a directory for installer files. This is called the "inventory directory". Within the inventory directory, the installer automatically sets up subdirectories for each product to contain inventory data and will consume typically Kilobytes per product.
It is recommended that this file oraInst. You need root privileges to do so. Actual Actual 64 Passed bit not required Checking temp space: must be greater than MB. All rights reserved. Reading response file.. Validations are enabled for this session. Summary of the Silent Deinstallation Syntax and Commands To run the product deinstaller from the command line, make sure that you understand the syntax and various command line options you can use for deinstallation.
Sample Silent Deinstall Commands These commands show how you can deinstall your product in silent mode. Starting silent deinstallation Location of the Oracle home directory.
Launches the 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 OUI'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 machines. By using a response file, you can automate the installation of a product for which you know the installation parameters.
When you install both bit and bit OUI 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.
By launching runInstaller in the background, you can change your current directory after you launch OUI, 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 OUI in the background and then exits. If you choose to create a shell script, remember to also pass all parameters that 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 Web. You can publish your staging area from a Web server and then in the Universal Installer's Source lo cation, specify the HTTP location for the products. 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 emailed or downloaded so they can perform a silent install.
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 OUI on the Solaris operating system, you need to define the following environment variables on the host computer where you are running OUI:.
On the computer that will display OUI, 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 OUI inventory. If you are installing OUI for the first time, you will be prompted to run a shell script from another terminal window before proceeding with the installation. OUI 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 OUI 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 deinstall Oracle software. Members of this group must have write permissions to the base directory chosen.
The following sections describe how to deinstall products installed using OUI. This section covers the pre-installation tasks that may be required before you are able to perform a silent installation. The Oracle inventory directory is used by the installer to keep track of all Oracle products installed on the computer.
The inventory directory is stored in a file called oraInst. If this file does not already exist on your system, you must create it before starting a silent installation. This file is used by the installer. Using a text editor such as vi or emacs, create the oraInst. The contents of the file consist of the following two lines:.
If you have not installed any Oracle products on your computer, then you need to create the following Registry key and value:. For example:. To run the product installer in silent mode, use -silent mode and specify a response file:. Table lists the valid command line parameters for silent installation.
Table Installer Command Line Parameters. Launches the installer in GUI mode. This is the default mode and is used if no mode is specified on the command line. Install in silent mode. The installer must be passed either a response file or command line variable value pairs. Displays the usage parameters for the runInstaller or setup.
Pointer to the inventory location file. Replace file with the full path and name of the oraInst. Pointer to the response file. Replace file with the full path and name of the response file. Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:. Log debugging information pertaining to time usage. This command causes the timeTaken timestamp. Windows only - the installer will wait for completion instead of spawning the Java engine and exiting.
0コメント