Different homes cannot share the same location. Also, the Oracle Universal Installer aborts. To override this condition, use the -force flag on the command line. The effect of using the -force flag is the same as selecting Yes while installing in interactive mode. You receive a warning message, but the installation continues.
To remove or deinstall Oracle homes, you can either use the Deinstall tool included with the Shiphome, or use the Deinstall utility available as part of the Oracle home. 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.
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. 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 2—2 shows the location of the default inventory pointer file for various platforms:. 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 flag 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:. For an example of the components file, see "Sample Components File".
This file contains the details about the node list, the local node name, and the Oracle Clusterware flag 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 flag to attach the local Oracle home. If you are using a shared Oracle home with the -local flag, use the -cfs flag.
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 flag, it updates the inventory.
You can use the -local flag to detach the Oracle home from the inventory of the local node. If you are using a shared Oracle home, use the -cfs flag. 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, do the following:.
Locate the oraInst. Remove the oraInst. The following procedure explains how to consolidate multiple central inventories into a single central inventory. Identify the Central Inventory to use and ensure that it is the same path on all nodes of the cluster. Go to this Central Inventory directory and run orainstRoot.
Identify the other central inventories on the system, then identify the Oracle homes for each Central Inventory. Verify that the overall inventory is being updated by running.
Ensure that the inventory shows the new home and the nodes. The following sections provide advisory information about shared Central Inventories, explain the enforced shared inventory check, and provide a procedure for reconstructing the Central Inventory. Identify a non-shared location for the Central Inventory. This location should have sufficient permissions, such as read and write permissions.
Make sure that the installation user creates this new location and that the location is part of the installation group. Obtain the list of Oracle homes from the existing shared Central Inventory registered in oraInventory, use the opatch lsinventory -all command.
Since this is a shared inventory, you may see Oracle homes listed in the Central Inventory from other systems on which the inventory is shared. Identify the Oracle home pertinent to the current system.
You can apply patchsets and upgrade an existing Oracle home. You can apply patchsets using Oracle Universal Installer. For more information on upgrading or applying patchsets for an Oracle product, refer to the respective Oracle product installation guide of the product that you want to upgrade.
You can clone an Oracle home using Oracle Universal Installer. For more information on cloning, see Chapter 5, "Cloning Oracle Software. You can back up the Oracle home using your preferred method.
You can use any method such as zip , tar , and cpio to compress the Oracle home. It is highly recommended to back up the Oracle home before any upgrade or patch operation. You should also back up the Central Inventory when Oracle home is installed or deinstalled. You want to patch this database but decide to back up the database before patching. If you are using a Win32 system, you could use WinZip to zip up the Oracle home.
Do not use the jar command to zip the Oracle home, as this causes the file permissions to become lost. Suppose you apply the patch and something goes wrong.
You decide to delete the Oracle home from the Central Inventory and restore the original Oracle home. To delete the Oracle home from the Central Inventory, use the following command:. Restore the original Oracle home and update the Central Inventory.
Restore the Oracle home to its original location using the following commands:. The inventory Central and the Oracle home inventory is critically important in the Oracle software life-cycle management. The following section explains what you need to do in case of inventory corruption. Problem: When you execute the opatch lsinventory -detail command or when you click Installed Products, the Oracle home does not appear.
Cause: This may result because of a missing or corrupted Oracle home inventory. Action: If the Oracle home inventory is missing or corrupted, restore the Oracle home inventory.
If you have not backed up the Oracle home inventory, you may have to install the software on a different node with the same platform and install the same patch levels including interim patches. After that, you can simply copy the inventory directory from the patched Oracle home to the location of the affected Oracle home.
The following sections describe the Home Selector, which is installed as part of Oracle Universal Installer on Windows computers. To view the Home Selector, click the Environment tab of the Inventory dialog, which appears when you click the Installed Products button on several Oracle Universal Installer screens. The Home Selector is a part of the installation software. If you need to switch the active home or need to perform batch work which requires a "default home" to be active, you can use the Home Selector to change the Windows NT system settings.
When using the Home Selector to make a specific Oracle home the active one, the software installation in question is moved to the front of the PATH variable, making it the first directory to be scanned for executable and library files.
When you perform an installation on a system, Oracle Universal Installer runs the selectHome. In silent mode, you perform this outside Oracle Universal Installer. This is the default Windows NT registry hive which contains all the "generic" Oracle settings. A typical Oracle home on Windows platforms contains the files and directories shown in Table The Optimal Flexible Architecture OFA standard is a set of configuration guidelines for fast, reliable Oracle databases that require little maintenance.
Organize large amounts of complicated software and data on disk to avoid device bottlenecks and poor performance. Facilitate routine administrative tasks such as software and data backup functions, which are often vulnerable to data corruption. Help eliminate fragmentation of free space in the data dictionary, isolate other fragmentation, and minimize resource contention. Table shows an example of the Oracle home directory structure and content for an Oracle Server Installation.
Under Unix, the Oracle home directory might contain the following subdirectories, as well as a subdirectory for each Oracle product selected. During an installation, prior to the actual installation of files, it may be required to prompt the user to obtain the list of selected features to install. The following sections describe how the selections are defined and how to drive the API which allows modification of these selections:. A feature set group, just like the name says, groups features together.
From a feature selection and installation perceptive these groups are virtual constructs which are only used for display purposes. The underlying dependency graph does not consider feature set groups. When a feature selection tree is presented to the user the feature set groups are meant to be the parent tree nodes which help group the features into areas the user might be interested in.
The features set references defined under each feature set group have a Boolean attribute called selected which is true by default. This defines the default selection state of that feature when the graph is initialized to the default install type or when an install type is chosen. The following is an example of two feature set groups you might see defined within a distribution definition.
Here the core. The OUI distribution definition gives you the ability to define optional install types. If the distribution definition does not define an install type, then a default one is created internally with the name Typical , which holds the default set of selections which were defined in the feature set group section of the distribution definition.
When a distribution definition defines its own install types, the feature set references within each install type override the default selections that were defined in the feature set groups for that specific install type. This install type will be used to initialize the selections in the case that no install type is chosen or custom selections changes are made. If a default is not defined or multiple defaults are defined, the first one encountered will be assumed as the default.
Whenever a new install type is selected, the selection state of the graph is reset to reflect the selections that the chosen install type defines which will overwrite any custom selections that may have been performed up to that point.
The following is an example of three install types which were defined for the feature set groups in the example above. The Standard install type does not define any overriding selection values for the feature sets. Since this install set provides no overriding values it simply takes on the selection states which were defined in the feature set groups above.
This is also the default install type which means it will be used to initialize the default set of selections after the graph is built and in absence of a install type actually being chosen.
This means that the initial selection state or if this install type was chosen of the features in the graph would contain the core. The Standard With Examples install set defines that the samples. All other selection states will be inherited from defaults defined in the feature set group section. This means that if this install type were chosen the core. The Client Only install set defines that the core.
The selection state of the client. This means that if this install type were chosen the client. If an installer allows for custom feature selection and the user chooses this option during the installation, the "selection tree" which the user is presented with is always a complete view of all feature set groups and visible features in the distribution.
This is to say that all feature set groups defined in the distribution will be presented to the user for selection. The default state of the selections in the tree presented will be determined by the install set which was chosen or the default install set if one was not chosen.
The API for interacting with the feature selections is the com. InstallerConfig class. This class lives in the com. There are two pieces of data which are required any time you are interacting with this API:.
The first thing which should be done when interacting with this API is to create a session object. The session object which is obtained by calling this method should be kept and reused for all operations in the API which pertain to the shipHomeDir and homeDir which was chosen.
If the user chooses a new Oracle home directory, a new session should be created. When the session object is created installation validation is performed. If there are any incompatibilities between the shiphome being installed and the chosen Oracle home a DependencyException error will be thrown.
Once you have the session object you should store a reference to this object and pass it to the other API methods:. This method gets a Set of the names of the install types which are defined in the distribution. If no install types are defined this will return a Set containing one install type name which is the default and has a name of "Typical". We ensure that our fantastic and extensive fleet of luxury vehicles reflects our image and your high standards. We are also capable of providing you with the vehicle of your choice from outside our fleet such as Ferraris and Porches for your added enjoyment.
Welcome To Oracle London. Oracle London is a luxury chauffeur company based in the heart of London with the aim of providing a professional service to corporate and private clients. Our service is reliable, punctual and most importantly discreet, ensuring that every client has a faultless experience. Whatever car you require, you can rest assured we have a car to suit your needs.
0コメント