So the entries in oratab might be dicey. It will really help you a lot if you first start the OS administration first before starting the DB part. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy.
Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Improve this answer. Won't work if env var is undefined. Marco 3, 4 4 gold badges 20 20 silver badges 25 25 bronze badges. Sid Sid 11 1 1 bronze badge.
What's the default if the env var is undefined? RDFozz Could you double-check, to make sure the answer is in fact complete and correct? Name ". The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. 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 the. 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:.
The Oracle Central Inventory is a repository for all Oracle products software installed on a system. Since the Central Inventory consists of system-specific information, it is required that the Central Inventory be saved on a local non-shared directory on the system. While software can be shared across nodes, the inventory should be local to each system.
If the Central Inventory is shared across system nodes , this would reflect the installation information for a group of systems collectively. Such a configuration also mandates that all Oracle homes registered in the inventory are also shared.
However, a shared inventory is contrary to Central Inventory design principles. Consequently, Oracle recommends placing the Central Inventory on a local file system not shared by other systems , because the Central Inventory is a system-specific inventory of the installations on this system.
Shared inventories are strongly discouraged. Since a shared inventory is a recommended practice, OUI displays a warning if you attempt to specify a shared inventory location under the following circumstances:. If you have already set up your inventory on shared storage prior to Grid Control version If you do not want to reconstruct the central inventory on a non-shared location, you can pass the -ignoreSharedInventory option to suppress the shared inventory error when invoking runInstaller.
Tru64 is a special operating system where all storage is shared storage including the operating system installed on shared storage. Therefore, a shared inventory is permissible. Perform the following steps as a Grid Control installation user, which is the user who owns the 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.
0コメント