During installation, you are prompted for the Oracle base path. Typically, an Oracle base path for the database is created during Oracle Grid Infrastructure installation.
OUI creates other necessary paths and environment variables in accordance with the Optimal Flexible Architecture OFA rules for well-structured Oracle software environments. For example, with Oracle Database 11g, Oracle recommends that you do not set an Oracle home environment variable allow OUI to create it instead. Because installation owner names are used by default for some paths, this ASCII character restriction applies to user names, file names, and directory names.
In the Specify Installation Location page, enter the Oracle home settings for the installation session. See Table for a description of the fields in this section of the screen. Continue with your installation. See Chapter 4, "Installing Products" for detailed information. Enter a name for the Oracle home. This name identifies the program group associated with a particular home and the Oracle services installed on this home. The Oracle home name must be between 1 to characters long, and can include only alphanumeric characters and underscores.
Enter the full path to an Oracle home, or select an Oracle home from the drop-down list of existing Oracle homes. The Oracle home location is the directory where products are installed. Data files may or may not be installed within an Oracle home. You can use the Browse button to choose a directory to install your product. Also, the Oracle Universal Installer aborts. To override this condition, use the -force option on the command line.
The effect of using the -force option is the same as selecting Yes while installing in interactive mode. You receive a warning message, but the installation continues. By default, when you start Oracle Universal Installer, the software searches your system to determine the default Oracle home where Oracle software should be installed.
See Chapter 3, "Creating and Customizing a Response File," for instructions for creating a response file. Typically, the following convention is used for the name:. If neither is specified, the following conventions are used for the path:. The instance-related directory location is accepted first from the response file, if specified.
If the parent directory of the Oracle home is writable, these directories are created in the parent directory of the Oracle home. Oracle Universal Installer supports the installation of several active Oracle homes on the same host as long as the products support this at run-time. Multiple versions of the same product or different products can run from different Oracle homes concurrently.
Products installed in one home do not conflict or interact with products installed on another home. You can update software in any home at any time, assuming all Oracle applications, services, and processes installed on the target home are shut down.
Processes from other homes may still be running. The Oracle home currently accessed by Oracle Universal Installer for installation or deinstallation is the target home. To upgrade or remove products from the target homes, these products must be shut down or stopped. The Oracle Universal Installer inventory stores information about all Oracle software products installed in all Oracle homes on a host, provided the product was installed using Oracle Universal Installer.
The XML format enables easier diagnosis of problems and faster loading of data. Any secure information is not stored directly in the inventory. As a result, during removal of some products, you may be prompted to enter the required credentials for validation.
It is strongly recommended that you place the central inventory on a local disk so that installations from other systems do not corrupt the inventory. You should not place the central inventory in the Oracle Base. Every Oracle software installation has an associated Central Inventory where the details of all the Oracle products installed on a host are registered. The Central Inventory is located in the directory that the inventory pointer file specifies.
Each Oracle software installation has its own Central Inventory pointer file that is unknown to another Oracle software installation. For Oracle homes sharing the same Central Inventory, the Oracle Universal Installer components perform all read and write operations on the inventory.
The operations on the Central Inventory are performed through a locking mechanism. This implies that when an operation such as installation, upgrade, or patching occurs on an Oracle home, these operations become blocked on other Oracle homes that share the same Central Inventory.
Table shows the location of the default inventory pointer file for various platforms:. The following string shows an example of the path for the oraInst. In UNIX, if you do not want to use the Central Inventory located in the directory specified by the inventory pointer file, you can use the -invPtrLoc option to specify another inventory pointer file.
The syntax is as follows:. The Central Inventory contains the information relating to all Oracle products installed on a host. It contains the following files and folders:. This file lists all the Oracle homes installed on the node. For each Oracle home, it also lists the Oracle home name, home index, and nodes on which the home is installed.
It also mentions if the home is an Oracle Clusterware home or a removed Oracle home. It can only detect removed Oracle homes created using Oracle Universal Installer version This file is present in the following location:.
The logs directory contains the logs corresponding to all installations performed on a particular node. The installation logs for an installation are identified by the timestamp associated with the log files. These files are generally saved in the following format:. For example, consider an attachHome operation performed on 17th, May, at 6. The associated log file would be created as follows:. Oracle home inventory or local inventory is present inside each Oracle home.
It only contains information relevant to a particular Oracle home. This file is located in the following location:. This file contains the details about third-party applications like Java Runtime Environment JRE required by different Java-based Oracle tools and components. In addition, it also contains details of all the components as well as patchsets or interim patches installed in the Oracle home.
This file is located here:. This file contains the details about the node list, the local node name, and the Oracle Clusterware option for the Oracle home. In a shared Oracle home, the local node information is not present. This file also contains the following information:.
The patching and patchset application depends on this ID. The information in oraclehomeproperties. Table lists the other folders you can find in the Oracle home inventory:. Oracle Universal Installer enables you to set up the Central Inventory on a clean host or register an existing Oracle home with the Central Inventory when it is lost or corrupted. If it does not find an entry there, it takes it from the Oracle Clusterware stack. You can use the -local option to attach the local Oracle home.
If you are using a shared Oracle home with the -local option, use the -cfs option. This ensures that the local node information is not populated inside a shared Oracle home. You can also view the contents of the inventory. You can detach an Oracle home from the Central Inventory. When you pass this option, it updates the inventory. Optional If you need to point to a custom inventory, you have the option to use the detachHome. You can use the -local option to detach the Oracle home from the inventory of the local node.
If you are using a shared Oracle home, use the -cfs option. Even after all the Oracle homes on a host are removed, you will find traces of the inventory with certain log files. If you do not want to maintain these files and want to remove the Central Inventory completely, do the following:. For Unix. Oracle Universal Installer creates the directory path that you specify under the Oracle base directory. It also sets the correct permissions on it. You do not need to create this directory. During installation, you must not specify an existing directory that has predefined permissions applied to it as the Oracle home directory.
If you do, then you may experience installation failure due to file and group ownership permission errors. In Oracle Database files and programs, a question mark? For example, Oracle Database expands the question mark in the following SQL statement to the full path of the Oracle home directory:.
The directory paths specified on each line identify Oracle home directories. I had 11g previously installed and now I have installed 12c. Have not uninstalled 11g. What is the path to 'home' of 12c? Improve this question.
Kaushik Nayak 29k 5 5 gold badges 25 25 silver badges 40 40 bronze badges. Add a comment. Active Oldest Votes. Improve this answer.
Kaushik Nayak Kaushik Nayak 29k 5 5 gold badges 25 25 silver badges 40 40 bronze badges. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password.
0コメント