Run root. The Cluster Node Addition Progress page's Status column displays Succeeded if the phase completes, In Progress if the phase is in progress, and Suspended when the phase is pending execution. This sets both networks to global. Therefore, you do not need to run the oifcfg command manually after you add a node unless the network interfaces differ.
After completing the procedures in this section, you have defined the new nodes at the cluster database layer. Use one of the following procedures to add the database instances to the new nodes:. To add a database instance to a new node with Enterprise Manager, perform the following procedure:. Under the Deployments section, click Add Instance.
This initiates a wizard to guide you through the instance addition process. After you submit the job, the wizard provides a summary page that shows whether the job succeeded and the wizard also provides other detailed information about the job, such as the elapsed time and an output log.
After adding the instances to the new nodes using the steps described in this section, perform any needed service configuration procedures as described in Chapter 6, "Introduction to Workload Management". To add a database instance to a new node with DBCA in interactive mode, perform the following procedure:. Select Add Instance and click Next. On the Adding an Instance page, enter the instance name in the field at the top of this page if the instance name that DBCA provides does not match your existing instance naming scheme.
If you are using raw devices or raw partitions, then on the Instance Storage page select the Tablespaces folder and expand it. Select the undo tablespace storage object and a dialog appears on the right-hand side. Change the default datafile name to the raw device name for the tablespace. If you are using raw devices or raw partitions or if you want to change the default redo log group file name, then on the Instance Storage page select and expand the Redo Log Groups folder. For each redo log group number that you select, DBCA displays another dialog box.
If you are using a cluster file system, then click Finish on the Instance Storage page. If you are using raw devices, then repeat step 10 for all of the other redo log groups, click Finish , and DBCA displays a Summary dialog. Review the information on the Summary dialog and click OK or click Cancel to end the instance addition operation. After you terminate your DBCA session, run the following command to verify the administrative privileges on the new node and obtain detailed information about these privileges where nodelist consists of the newly added nodes:.
Use the following syntax to perform this operation where node is the node onto which you want to add the instance, gdbname is the global database name, instname is the name of the new instance, sysdba is the name of an Oracle user with SYSDBA privileges, and password is the password for the user name in sysdba :. Note that you only need to provide an instance name if you want to override the Oracle naming convention for Oracle RAC instance names.
After you have completed either of the DBCA procedures in this section, DBCA has successfully added the new instance to the new node and completed the following steps:. Created and started services if you entered services information on the Services Configuration page. To add nodes to a cluster that already have clusterware and Oracle software installed on them, you must configure the new nodes with the Oracle software that is on the existing nodes of the cluster.
To do this, you must run two versions of an OUI process: one for the clusterware and one for the database layer as described in the following procedures:. Add new nodes at the Oracle Clusterware layer by running OUI from the Oracle Clusterware home on an existing node, using the following command:. In the -noCopy mode, OUI performs all add node operations except for the copying of software to the new nodes. This section explains how to delete nodes from clusters using detailed manual procedures.
To delete an instance with Enterprise Manager from an existing node, perform the following steps:. Under the Deployments section, click Delete Instance. This action initiates a wizard to guide you through the deletion process. After you submit the job, the wizard displays a summary page that shows whether the job succeeded. The wizard also provides other detailed information about the job, such as an output log and information about the elapsed time.
Start DBCA on a node other than the node that hosts the instance that you want to delete. Select an Oracle RAC database from which to delete an instance. The List of Cluster Database Instances page shows the instances that are associated with the Oracle RAC database that you selected and the status of each instance. Use this feature to reassign services from this instance to other instances in the cluster database.
Review the information about the instance deletion operation on the Summary page and click OK. Otherwise, click Cancel to cancel the instance deletion operation. Use DBCA to delete a database instance from a node as follows, where the variables are the same as those in the preceding add instance command:.
You only need to provide a node name if you are deleting an instance from a node other than the one on which you are running DBCA. Deleted the Oracle Flexible Architecture directory structure from the instance's configured node. If there are instances on the node that you want to delete, then perform the procedures in the section titled "Step 1: Deleting Instances from Oracle Real Application Clusters Databases" before executing these procedures.
If you are deleting more than one node, then delete the instances from all the nodes that you are going to delete. If necessary, re-create this listener in another home.
Using this command does not launch an installer GUI. Run OUI from the home and deinstall this home. Only run this command once and use the nosharedhome argument if you are using a local file system. The default for this command is sharedhome which prevents you from updating the permissions of local files such that they can be removed by the oracle user.
If the ocr. If you are deleting more than one node from your cluster, then repeat this step on each node that you are deleting. For a non-shared Oracle home, on each node that you are deleting, perform the following two steps:. Executing this command does not launch an installer GUI. Run the following command to verify that the node is no longer a member of the cluster and to verify that the Oracle Clusterware components have been removed from this node:.
The response from this command should not contain any information about the node that you deleted; the deleted node should no longer have the Oracle Clusterware components on it. This verifies that you have deleted the node from the cluster. As mentioned earlier in this procedure, you can optionally delete nodes from Oracle Real Application Clusters databases in silent mode by completing the following steps:.
Complete steps 1 through 3 of the procedure described at the start of this section under the heading "Step 2: Deleting Nodes from Oracle Real Application Clusters Databases".
Depending on whether you have a shared or non-shared Oracle Clusterware home, complete one of the following two procedures:.
For shared homes, do not perform a deinstall operation. Instead, perform a detach home operation on the node that you are deleting. Stop all of the databases that use the ASM instance that is running from the Oracle home that is on the node that you are deleting.
On the node that you are deleting, if this is the Oracle home which from which the ASM instance runs, then remove the ASM configuration by completing the following steps. Run the command srvctl remove asm -n node for all nodes on which this Oracle home exists. If you are not using a cluster file system for your ASM Oracle home, then run the rm or delete commands mentioned in the previous step on each node on which the Oracle home exists. In addition, use a directory that exists on all of the nodes.
Quick-Start Node and Instance Addition and Deletion Procedures This section explains node and instance addition and deletion for UNIX-based systems using procedures that are presented in a quick-start format.
If you are using Oracle Clusterware with vendor clusterware, then you can add nodes on some UNIX-based systems without stopping the existing nodes if your clusterware supports this.
Refer to your vendor-specific clusterware documentation for more information. Note: For all of the procedures in this chapter, it is very important that you perform each step in the order shown.
In other words, you extend the software onto the new nodes in the same order as you installed the clusterware and Oracle database software components on the existing nodes. Run the orainstRoot. Note: The orainstRoot. Note: The root.
Cause: The Oracle home may be missing from the Central Inventory, or the Central Inventory could be missing or corrupted. If the Oracle home is missing from the Central Inventory, perform an attach home operation on the missing Oracle home. The Central Inventory will be restored. If the Central Inventory is missing or corrupted, restore the Central Inventory.
If you have not backed up the Central Inventory, perform an attach home operation. For more information on the attach home operation, see "Creating the Central Inventory". If multiple entries are in the inventory. In this event, you should remove these duplicate entries manually. In the above example, the first and third entries are duplicates. The Oracle home name and Oracle home location are identical.
In this example, remove the third line. Note that all duplicate inventory issues are caused by manual updates to the inventory.
When you execute opatch lsinventory -detail or when you click Installed Products, the Oracle home appears, but the products and components within the Oracle home are not listed.
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.
In an Oracle Real Application Clusters environment, the inventory also contains a list of nodes associated with an Oracle home. It is important that during upgrade and patching, the inventory is correctly populated with the list of nodes. For more information, see Chapter 5, "Installing Cluster Environments". When you use the -updateNodeList flag with the Oracle Universal Installer, it retrieves the list of nodes and updates the inventory.
For shared Oracle homes, you need to use this with the -cfs flag. Recreate the Central Inventory with the attachhome option as in MetaLink note 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. Skip Headers.
The Oracle home consists of the following: Directory location where the products are installed Corresponding system path setup Program groups associated with the products installed in the home where applicable Services running from the home.
To install the product and create the Oracle home, perform the following steps: Run Oracle Universal Installer. Software Location Enter the full path to an Oracle home, or select an Oracle home from the drop-down list of existing Oracle homes. Note: Oracle recommends that you designate an Oracle home location that is an empty or non-existing directory. If you select a directory for the Oracle home location that is not empty or already exists, you will be warned and asked if you want to proceed.
Removing Oracle Homes 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. To use the Deinstall tool, do the following to remove the Oracle home: cd to DeinstallTool. Run Deinstall. Determining the Default 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.
Multiple Oracle Homes 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. Target Home The Oracle home currently accessed by Oracle Universal Installer for installation or deinstallation is the target home.
Oracle Universal Installer Inventory 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. Note: Oracle recommends placing the central inventory on a local file system that is not shared by other systems, since the central inventory is a system-specific inventory of the installations on this system.
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. X64 Windows. Note: If the contents of the oraInst. Central Inventory The Central Inventory contains the information relating to all Oracle products installed on a host. Oracle Home Inventory Oracle home inventory or local inventory is present inside each Oracle home.
Home Properties File This file contains the details about the node list, the local node name, and the Oracle Clusterware flag for the Oracle home. ContentsXML Contains the details of the components and libraries installed.
Templates Contains the template files used for cloning. Creating the Central 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.
Note: Oracle recommends cloning on Windows operating systems to create the Central Inventory. Removing the Central Inventory Even after all the Oracle homes on a host are removed, you will find traces of the inventory with certain log files. Delete the Central Inventory directory and all its contents. Consolidating Multiple Central Inventories The following procedure explains how to consolidate multiple central inventories into a single central inventory. Reconstructing a Shared Central Inventory on a Non-shared Location 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.
Enforced Shared Inventory Check 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: Grid Control upgrades from HPTru64 Cases — Tru64 is a special operating system where all storage is shared storage including the operating system installed on shared storage. Procedure to Reconstruct the Central Inventory Perform the following steps as a Grid Control installation user, which is the user who owns the inventory.
You can delete the directory, but this is not mandatory. Backing up the Inventory You can back up the Oracle home using your preferred method. Recovering from Inventory Corruption The inventory Central and the Oracle home inventory is critically important in the Oracle software life-cycle management. Diagnosing and Recovering from Central Inventory Corruption When you execute opatch lsinventory -detail or when you click Installed Products, the Oracle home does not appear.
Action: Do the following: If the Oracle home is missing from the Central Inventory, perform an attach home operation on the missing Oracle home. Diagnosing and Recovering from Oracle Home Inventory Corruption When you execute opatch lsinventory -detail or when you click Installed Products, the Oracle home appears, but the products and components within the Oracle home are not listed.
Note: For Oracle Universal Installer version Updating the Nodes of a Cluster When you use the -updateNodeList flag with the Oracle Universal Installer, it retrieves the list of nodes and updates the inventory.
If you do not specify the -local flag, then the command removes the Oracle Grid Infrastructure home from every node in the cluster. If you cut and paste the preceding command, then paste it into a text editor before pasting it to the command line to remove any formatting this document might contain. If you have a shared home, then run the following commands in the following order on the node you want to delete. If you have a shared Oracle Grid Infrastructure home, then append the -cfs option to the command example in this step and provide a complete path location for the cluster file system.
Note: You can remove the Oracle RAC database instance from the node before removing the node from the cluster but this step is not required. Voting files are automatically backed up in OCR after any changes you make to the cluster.
0コメント