|
Plans in the N1 SPS Oracle 10g R2 RAC Plug-In
This page contains the following information:
Solaris User Plan
This section describes the Solaris user plan, Oracle_User.create.
Top
Oracle User Installation Plan (Oracle_User.create)
The Oracle_User component has the standard install and attach semantics. If the component finds that the Solaris user exists, it checks that all of the component variables match the definition. If they do, then no further action is taken. This operation is considered an attach. If the user does not exist, then the user is created along with the associated home directory. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The Oracle_User component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables is null.
- The user exists on a node and the component variables do not match the existing settings.
Solaris Package Plans
This section describes the following Solaris package plans:
Top
Sun Cluster Reconfiguration Framework Package Installation Plan (SUNWscucm_package.install)
The SUNWscucm_package component has the standard install and attach semantics. When the SUNWscucm_package.install plan is run, it will only install the SUNWscucm package if the package is not present. Target nodes must be of type system#crhost.
 | Note
When you use Sun Cluster 3.2 software, the SUNWscucm_package.install plan will automatically install the other Solaris packages in the Java Availability Suite Oracle RAC agent group.
SPARC - SUNWudlmr, SUNWudlm, SUNWscmd, SUNWcvmr, SUNWcvmr and SUNWscor
AMD/x64 - SUNWscmd, SUNWcvmr, SUNWcvmr and SUNWscor |
The SUNWscucm_package component installation will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
Top
UNIX Distributed Lock Manager Package Installation Plan (ORCL-SUNWudlmX_package.install)
The SUNWudlmr_package, SUNWudlm_package, and ORCLudlm_package components have the standard install and attach semantics. When the ORCL-SUNWudlmX_package.install plan is run, it will only install the SUNWudlmr, SUNWudlm or ORCLudlm packages if they are not present. In the case of Sun Cluster 3.2 software, the installation of the SUNWscucm package results in this always being an attach operation for the SUNWudlmr and SUNWudlm packages. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The SUNWudlmr_package, SUNWudlm_package, and ORCLudlm_package component installations will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
Top
Sun Cluster Solaris Volume Manager Integration Package Installation Plan (SUNWscmd_package.install)
The SUNWscmd_package component has the standard install and attach semantics. When the SUNWscmd_package.install plan is run, it will only install the SUNWscmd package if is not present. In the case of Sun Cluster 3.2 software, the installation of the SUNWscucm package results in this always being an attach operation. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The SUNWscmd_package component installation will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
Top
Sun Cluster Veritas Cluster Volume Manager Integration Package Installation Plan (SUNWcvmX_package.install)
The SUNWcvmr_package and SUNWcvm_package components have the standard install and attach semantics. When the SUNWcvmX_package.install plan is run, it will only install the SUNWcvmr or SUNWcvm packages if they are not present. In the case of Sun Cluster 3.2 software, the installation of the SUNWscucm package results in this always being an attach operation. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The SUNWcvmr_package and SUNWcvm_package component installation will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
Top
Sun Cluster Hardware RAID Integration Package Installation Plan (SUNWschwr_package.install)
The SUNWschwr_package component has the standard install and attach semantics. When the SUNWschwr_package.install plan is run, it will only install the SUNWschwr package if it is not present. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The SUNWschwr_package component installation will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
Top
Sun Cluster Oracle Agent Package Installation Plan (SUNWscor_package.install)
The SUNWscor_package component has the standard install and attach semantics. When the SUNWscor_package.install plan is run, it will only install the SUNWscor package if it is not present. In the case of Sun Cluster 3.2 software, the installation of the SUNWscucm package results in this always being an attach operation. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The SUNWscor_package component installation will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
Top
Sun StorageTek QFS Root and User Packages Installation Plan (SUNWqfsX_package.install)
The SUNWqfsr_package and SUNWqfsu_package components have the standard install and attach semantics. When the SUNWqfsX_package.install plan is run, it will only install the SUNWqfsr or SUNWqfsu packages if they are not present. If the packages are not installed and an invalid installPath is specified, the installation will fail. Target nodes must be of type system#crhost.
The plan can be targeted at individual nodes or at groups of nodes and does not use a synchronized installation process.
The SUNWqfsr_package and SUNWqfsu_package component installation will fail if the following condition exists:
- The package is not installed and an invalid installPath is specified.
File System Plans
This section describes the following file system plans:
Top
Shared QFS File System Creation Plan (Shared_QFS.create)
The Shared_QFS.create plan creates, attaches to, or expands a shared QFS file system. If the file system is present on a target node and matches the component variable settings, then no further action is taken. If the file system is not present on one or more of the target nodes, the file system is created or extended to those nodes. Target nodes must be of type system#crhost.
| Note
This component uses a synchronized installation or expansion plan. Target all the nodes on which you want the component in the "To Be" state. |
The plan has a single plan variable:
The shared QFS component installation will fail if any of the following conditions exist:
- The SUNWqfsr or SUNWqfsu packages are not installed.
- Any of the mandatory component variables are null.
- The mount point for the file system (installPath) is not an absolute path, that is, starts with a leading slash (/).
- The dau or fsOrdinal contains letters or spaces.
- The mount options contain spaces.
- Any of the settings conflict with existing settings on any of the nodes, for example, file system /rac_data has fsOrdinal equal to 10, but on one node it already has fsOrdinal equal to 20 in /etc/opt/SUNWsamfs/mcf.
- If an /etc/opt/SUNWsamfs/hosts.fs file, such as, hosts.rac_data is found on a cluster node that has not been targeted. This means that the plan has not been targeted properly.
- The ssh root passphrase has not been set up correctly.
- Not all the cluster nodes are up and running.
Top
Shared QFS File System Deinstallation Plan (Shared_QFS.remove)
The Shared_QFS.remove plan removes a shared QFS file system from the target nodes. Target nodes must be of type system#crhost. The shared QFS file system will be unmounted on all nodes during this procedure.
| Note
This component uses a synchronized contraction or removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has two plan variables:
- The mount point of the file system to shrink or remove, such as /rac_data.
- The ssh root passphrase.
The shared QFS component deinstallation will fail if any of the following conditions exist:
- The SUNWqfsr is not installed.
- The shared QFS file system cannot be unmounted from all nodes it is currently defined for.
- Not all the cluster nodes are up and running.
Sun Cluster Resource Group Plans
This section describes the following Sun Cluster resource group plans:
Top
RAC Framework Resource Group Installation Plan (RAC_framework_RG.create)
The RAC_framework_RG.create plan creates a Sun Cluster resource group that can be used to contain the RAC framework, RAC udlm, and RAC volume manager resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Install/Attach/Expand Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or expansion plan. Target all the nodes on which you want the component in the "To Be" state. |
The RAC framework resource group component installation will fail if any of the following conditions exist:
- The SUNWscucm package is not installed.
- The installName or nodeList is null.
- The node list has spaces in it.
- The specified resource group already exists, but has node list is a superset or disjoint set from the nodeList component variable that is specified. This would be effectively asking for the resource group to be contracted by using an installation step rather than by using a removal step.
Top
RAC Framework Resource Group Deinstallation Plan (RAC_framework_RG.remove)
The RAC_framework_RG.remove plan shrinks or removes a Sun Cluster resource group that is capable of holding the RAC framework, RAC udlm, and RAC volume manager resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Contract/Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized contraction or removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has a single plan variable:
- The name given to the RAC framework resource group deployed by N1 SPS, such as rac-framework-rg.
The RAC framework resource group component uninstall will fail if the following condition exists:
- The named RAC framework resource group has not been previously deployed by N1 SPS on that node.
Top
RAC Proxy Resource Group Installation Plan (RAC_proxy_RG.create)
The RAC_proxy_RG.create plan creates a Sun Cluster resource group that can be used to contain RAC proxy resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Install/Attach/Expand Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or expansion plan. Target all the nodes on which you want the component in the "To Be" state. |
The RAC proxy resource group component installation will fail if any of the following conditions exist:
- The cluster is not running Sun Cluster 3.2 software.
- The RAC framework resource group component is not installed on the node.
- The node list has spaces in it.
- The specified resource group already exists, but has node list is a superset or disjoint set from the nodeList component variable that is specified. This would be effectively asking for the resource group to be contracted by using an installation step rather than by using a removal step.
Top
RAC Proxy Resource Group Deinstallation Plan (RAC_proxy_RG.remove)
The RAC_proxy_RG.remove plan shrinks or removes a Sun Cluster resource group that is that is capable of holding the RAC proxy resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Contract/Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized contraction or removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has a single plan variable:
- The name given to the RAC proxy resource group deployed by N1 SPS, such as rac-proxy-rg.
The RAC framework resource group component uninstall will fail if the following condition exists:
- The named RAC proxy resource group has not been previously deployed by N1 SPS on that node.
Top
Scalable Device Group Resource Group Installation Plan (Scalable_Device_Group_RG.create)
The Scalable_Device_Group_RG.create plan creates a Sun Cluster resource group that can be used to contain scalable device group resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Install/Attach/Expand Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or expansion plan. Target all the nodes on which you want the component in the "To Be" state. |
The scalable device group resource group component installation will fail if any of the following conditions exist:
- The cluster is not running Sun Cluster 3.2 software.
- The installName or nodeList is null.
- The node list has spaces in it.
- The specified resource group already exists, but has node list is a superset or disjoint set from the nodeList component variable that is specified. This would be effectively asking for the resource group to be contracted by using an installation step rather than by using a removal step.
Top
Scalable Device Group Resource Group Deinstallation Plan (Scalable_Device_Group_RG.remove)
The Scalable_Device_Group_RG.remove plan shrinks or removes a Sun Cluster resource group that is capable of holding the scalable device group resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Contract/Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized contraction or removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has a single plan variable:
- The name given to the scalable device group resource group deployed by N1 SPS, such as scaldg-rg.
The scalable device group resource group component uninstall will fail if the following condition exists:
- The named scalable device group resource group has not been previously deployed by N1 SPS on that node.
Top
Scalable Mount Point Resource Group Installation Plan (Scalable_Mount_Point_RG.create)
The Scalable_Mount_Point_RG.create plan creates a Sun Cluster resource group that can be used to contain scalable mount point resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Install/Attach/Expand Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or expansion plan. Target all the nodes on which you want the component in the "To Be" state. |
The scalable mount point resource group component installation will fail if any of the following conditions exist:
- The cluster is not running Sun Cluster 3.2 software.
- The installName or nodeList is null.
- The node list has spaces in it.
- The specified resource group already exists, but has node list is a superset or disjoint set from the nodeList component variable that is specified. This would be effectively asking for the resource group to be contracted by using an installation step rather than by using a removal step.
Top
Scalable Mount Point Resource Group Deinstallation Plan (Scalable_Mount_Point_RG.remove)
The Scalable_Mount_Point_RG.remove plan shrinks or removes a Sun Cluster resource group that is capable of holding the scalable mount point resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Contract/Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized contraction or removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has a single plan variable:
- The name given to the scalable mount point resource group deployed by N1 SPS, such as scalmp-rg.
The scalable mount point resource group component uninstall will fail if the following condition exists:
- The named scalable mount point resource group has not been previously deployed by N1 SPS on that node.
Top
Shared QFS Resource Group Installation Plan (Shared_QFS_RG.create)
The Shared_QFS_RG.create plan creates a Sun Cluster resource group that can be used to contain shared QFS resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Install/Attach/Expand Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or expansion plan. Target all the nodes on which you want the component in the "To Be" state. |
The shared QFS resource group component installation will fail if any of the following conditions exist:
- The installName or nodeList is null.
- The node list has spaces in it.
- The specified resource group already exists, but the node list is a superset or disjoint set from the nodeList component variable that is specified. This would be effectively asking for the resource group to be contracted by using an installation step rather than by using a removal step.
Top
Shared QFS Resource Group Deinstallation Plan (Shared_QFS_RG.remove)
The Shared_QFS_RG..remove plan shrinks or removes a Sun Cluster resource group that is capable of holding the shared QFS resources. The plan operates according to the rules that are described in Sun Cluster Resource Group Contract/Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized contraction or removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has a single plan variable:
- The name that is given to the shared QFS resource group that is deployed by N1 SPS, such as qfs-rg.
The shared QFS resource group component uninstall will fail if the following condition exists:
- The named shared QFS resource group has not been previously deployed by N1 SPS on that node.
Sun Cluster Resource Plans
This section describes the following Sun Cluster resource plans:
Top
RAC Framework Resource Installation Plan (RAC_framework_RS.create)
The RAC_framework_RS.create plan creates a Sun Cluster RAC framework resource. This should be deployed after the RAC_framework_RG component has been deployed and must have the rg_name set to the installName of that component. There is only one RAC framework resource cluster-wide. You cannot install more than one of these resources. The plan operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the RAC framework resource on creation. This should not be checked when you use Sun Cluster 3.2 software.
The RAC framework resource component installation will fail if any of the following conditions exist:
- A rac_framework resource has been created in a different resource group (only one can be created cluster-wide).
- The SUNWscucm package component is not installed on the node.
- The rac framework resource group component is not installed on the node.
- The nodes targeted by the component installation do not match the current node list for the resource group specified.
Top
RAC Framework Resource Deinstallation Plan (RAC_framework_RS.remove)
The RAC_framework_RS.remove plan removes a Sun Cluster RAC framework resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore, the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the RAC framework resource to remove.
Top
RAC Framework Resource Enable/Disable plan (RAC_framework_RS.enable and RAC_framework_RS.disable)
The RAC_framework_RS.enable and RAC_framework_RS.disable plans enable you to enable and disable a resource deployed through the RAC_framework_RS component. When you use Sun Cluster 3.2 software, you should only enable the RAC_framework resource when you have successfully created all the required RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm, resources. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the RAC framework resource to enable or disable.
Top
CRS Framework Resource Installation Plan (CRS_framework_RS.create)
The CRS_framework_RS.create plan creates a Sun Cluster CRS framework resource. This should be deployed after the RAC_framework_RG component has been deployed and must have the rg_name set to the installName of that component. The plan can only be used under Sun Cluster 3.2 software and operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the CRS framework resource on creation. This should not be checked when you use Sun Cluster 3.2 software.
The CRS framework resource component installation will fail if any of the following conditions exist:
- The cluster is not running Sun Cluster 3.2 software.
- The SUNWscor package in not installed.
- A rac_framework resource has not been installed on this node.
- The rac framework resource group component is not installed on the node.
- A crs_framework resource has been created in a different resource group (only one can be created cluster-wide).
Top
CRS Framework Resource Deinstallation Plan (CRS_framework_RS.remove)
The CRS_framework_RS.remove plan removes a Sun Cluster CRS framework resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the CRS framework resource to remove.
Top
CRS Framework Resource Enable/Disable Plans (CRS_framework_RS.enable and CRS_framework_RS.disable)
The CRS_framework_RS.enable and CRS_framework_RS.disable plans enable you to enable and disable a resource deployed through the CRS_framework_RS component. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the CRS framework resource to enable or disable.
Top
RAC Proxy Resource Installation Plan (RAC_proxy_RS.create)
The RAC_proxy_RS.create plan creates a Sun Cluster RAC proxy resource. This should be deployed after a RAC_proxy_RG component has been deployed and must have the rg_name set to the installName of that component. The plan can only be used under Sun Cluster 3.2 software and operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the CRS framework resource on creation. This should not be checked when you use Sun Cluster 3.2 software.
The RAC proxy resource component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables is null.
- The cluster is not running Sun Cluster 3.2 software.
- The SUNWscor package component has not been installed.
- The CRS framework resource component has not been installed.
- A rac proxy resource group component is not installed on the node.
Top
RAC Proxy Resource Deinstallation Plan (RAC_proxy_RS.remove)
The RAC_proxy_RS.remove plan removes a Sun Cluster RAC proxy resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the RAC proxy resource to remove.
Top
RAC Proxy Resource Enable/Disable Plans (RAC_proxy_RS.enable and RAC_proxy_RS.disable)
The RAC_proxy_RS.enable and RAC_proxy_RS.disable plans enable you to enable and disable a resource that is deployed through the RAC_proxy_RS component. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the RAC proxy resource to enable or disable.
Top
RAC Proxy Resource Create CRS Proxy Resource Plan (RAC_proxy_RS.add_crs_integration)
The RAC_proxy_RS.add_crs_integration plan that calls a control to create an Oracle Clusterware proxy resource that is linked to the RAC proxy resource. This can only be run once the RAC proxy resource has been created through the plug-in and can only be used under Sun Cluster 3.2 software. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
The plan has a single plan variable:
- The name of the Sun Cluster RAC proxy resource to add the Oracle CRS proxy integration for.
Top
RAC Proxy Resource Remove CRS Proxy Resource Plan (RAC_proxy_RS.remove_crs_integration)
The RAC_proxy_RS.remove_crs_integration plan that calls a control to remove an Oracle Clusterware proxy resource that is linked to the RAC proxy resource. This can only be run once the RAC proxy resource has been created through the plug-in and can only be used under Sun Cluster 3.2 software. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
The plan has a single plan variable:
- The name of the Sun Cluster RAC proxy resource for which to remove the Oracle CRS proxy integration.
Top
RAC Solaris Volume Manager Resource Installation Plan (RAC_svm_RS.create)
The RAC_svm_RS.create plan creates a Sun Cluster RAC svm resource. Deploy this plan after the RAC_framework_RG component has been deployed. The rg_name must be set to the installName of that component. There is only one RAC svm resource cluster-wide. You cannot install more than one of these resources. The plan operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the RAC svm resource on creation. This should not be checked when you use Sun Cluster 3.2 software.
The RAC svm resource component installation will fail if any of the following conditions exist:
- The SUNWscmd packages is not installed.
- The architecture is SPARC and the SUNWudlm package is not installed.
- A rac_framework resource has not been installed on this node.
- The rac framework resource group component is not installed on the node.
- A RAC svm resource has been created in a different group (only one can be created cluster-wide).
Top
RAC Solaris Volume Manager Resource Deinstallation Plan (RAC_svm_RS.remove)
The RAC_svm_RS.remove plan removes a Sun Cluster RAC svm resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore, the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the RAC svm resource to remove.
Top
Solaris Volume Manager Resource Enable/Disable Plans (RAC_svm_RS.enable and RAC_svm_RS.disable)
The RAC_svm_RS.enable and RAC_svm_RS.disable plans enable you to enable and disable a resource that is deployed through the RAC_svm_RS component. When you use Sun Cluster 3.2 software, you should only enable the RAC_svm resource when you have successfully created all the required RAC_framework, RAC_udlm (SPARC only) and RAC_svm resources. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the RAC svm resource to enable or disable.
Top
RAC Veritas Cluster Volume Manager Resource Installation Plan (RAC_cvm_RS.create)
The RAC_cvm_RS.create plan creates a Sun Cluster RAC cvm resource. Deploy this plan after the RAC_framework_RG component has been deployed. The rg_name must be set to the installName of that component. There is only one RAC cvm resource cluster-wide. You cannot install more than one of these resources. The plan operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the RAC cvm resource on creation. This should not be checked when you use Sun Cluster 3.2 software.
The RAC svm resource component installation will fail if any of the following conditions exist:
- Any of the mandatory variables is null.
- The SUNWcvmr or SUNWcvm packages are not installed. These will be absent on x64 since these packages do not exist yet.
- A rac_framework resource has not been installed on this node.
- The rac framework resource group component is not installed on the node.
- A RAC cvm resource has been created in a different group (only one can be created cluster-wide).
Top
RAC Veritas Cluster Volume Manager Resource Deinstallation Plan (RAC_cvm_RS.remove)
The RAC_cvm_RS.remove plan removes a Sun Cluster RAC cvm resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore, the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the RAC cvm resource to remove.
Top
RAC Veritas Cluster Volume Manager resource Enable/Disable Plans (RAC_cvm_RS.enable and RAC_cvm_RS.disable)
The RAC_cvm_RS.enable and RAC_cvm_RS.disable plans enable you to enable and disable a resource that is deployed through the RAC_cvm_RS component. When you use Sun Cluster 3.2 software, only enable the RAC_cvm resource after you have successfully created all the required RAC_framework, RAC_udlm (SPARC only), and RAC_cvm resources. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the RAC cvm resource to enable or disable.
Top
RAC Hardware RAID Resource Installation Plan (RAC_hwraid_RS.create)
The RAC_hwraid_RS.create plan creates a Sun Cluster RAC hwraid resource. Deploy this plan after the RAC_framework_RG component has been deployed. The rg_name must be set to the installName of that component. There is only one RAC hwraid resource cluster-wide. You cannot install more than one of these resources. The plan operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the RAC hwraid resource on creation. This can be checked when you use Sun Cluster 3.1 software.
The RAC hwraid resource component installation will fail if any of the following conditions exist:
- The SUNWschwr is not installed. This will be absent on Sun Cluster 3.2 software since the package does not exist.
- A rac_framework resource has not been installed on the node.
- The rac framework resource group component is not installed on the node.
- A RAC hwraid resource has been created in a different group (only one can be created cluster-wide).
Top
RAC Hardware RAID Resource Deinstallation Plan (RAC_hwraid_RS.remove)
The RAC_hwraid_RS.remove plan removes a Sun Cluster RAC hwraid resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore, the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the RAC hwraid resource to remove.
Top
RAC Hardware RAID Resource Enable/Disable Plans (RAC_hwraid_RS.enable and RAC_hwraid_RS.disable)
The RAC_hwraid_RS.enable and RAC_hwraid_RS.disable plans enable you to enable and disable a resource that is deployed through the RAC_hwraid_RS component. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the RAC hwraid resource to enable or disable.
Top
RAC UDLM Resource Installation Plan (RAC_udlm_RS.create)
The RAC_udlm_RS.create plan creates a Sun Cluster RAC udlm resource on SPARC platforms only. Deploy this plan after the RAC_framework_RG component has been deployed. The rg_name must be set to the installName of that component. There is only one RAC udlm resource cluster-wide. You cannot install more than one of these resources. The plan operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- Whether to enable the RAC udlm resource on creation. This should not be checked when you use Sun Cluster 3.2 software.
The RAC udlm resource component installation will fail if any of the following conditions exist:
- Any of the time-out variables is null.
- The SUNWudlmr, SUNWudlm or ORCLudlm packages are not installed. These will always be absent on x64 since these packages do not exist.
- A rac_framework resource has not been installed on this node.
- The rac framework resource group component is not installed on the node.
- A RAC udlm resource has been created in a different group (only one can be created cluster-wide).
Top
RAC UDLM Resource Deinstallation Plan (RAC_udlm_RS.remove)
The RAC_udlm_RS.remove plan removes a Sun Cluster RAC udlm resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the RAC udlm resource to remove.
Top
RAC UDLM Resource Enable/Disable Plans (RAC_udlm_RS.enable and RAC_udlm_RS.disable)
The RAC_udlm_RS.enable and RAC_udlm_RS.disable plans enable you to enable and disable a resource that is deployed through the RAC_udlm_RS component. When you use Sun Cluster 3.2 software, you should only enable the RAC_udlm resource when you have successfully created all the required RAC_framework and volume manager RAC_svm or RAC_cvm resources. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the RAC udlm resource to enable or disable.
Top
Scalable Device Group Resource Installation Plan (Scalable_Device_Group_RS.create)
The Scalable_Device_Group_RS.create plan creates a Sun Cluster scalable device group resource. Deploy this plan after a Scalable_Device_Group_RG component has been deployed. The rg_name must be set to the installName of that component. The plan can only be used under Sun Cluster 3.2 software and operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- (Optional) Whether to enable the scalable device group resource on creation.
The Scalable Device Group resource component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables is null.
- The volume manager is not equal to svm or cvm.
- The cluster is not running Sun Cluster 3.2 software.
- A RAC_svm resource has not been installed and the volume manager is svm.
- A RAC_cvm resource has not been installed and the volume manager is cvm.
- The device group named is not multi-owner.
- The device group node list does not match the target node list.
Top
Scalable Device Group Resource Deinstallation Plan (Scalable_Device_Group_RS.remove)
The Scalable_Device_Group_RS.remove plan removes a Sun Cluster scalable device group resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the scalable device group resource to remove.
Top
Scalable Device Group Resource Enable/Disable Plans (Scalable_Device_Group_RS.enable and Scalable_Device_Group_RS.disable)
The Scalable_Device_Group_RS.enable and Scalable_Device_Group_RS.disable .plans enable you to enable and disable a resource deployed through the Scalable_Device_Group_RS component. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the scalable device group resource to enable or disable.
Top
Scalable Mount Point Resource Installation Plan (Scalable_Mount_Point_RS.create)
The Scalable_Mount_Point_RS.create plan creates a Sun Cluster scalable mount point resource. Deploy this plan after a Scalable_Mount_Point_RG component has been deployed. The rg_name must be set to the installName of that component. The plan can only be used under Sun Cluster 3.2 software and operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- (Optional) Whether to enable the scalable mount point resource on creation.
The Scalable Mount Point resource component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables is null.
- The target mount point is not at absolute path.
- The cluster is not running Sun Cluster 3.2 software.
- The file system type is not s-qfs or nas.
Top
Scalable Mount Point Resource Deinstallation Plan (Scalable_Mount_Point_RS.remove)
The Scalable_Mount_Point_RS.remove plan removes a Sun Cluster scalable mount point resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore, the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the scalable mount point resource to remove.
Top
Scalable Mount Point Resource Enable/Disable Plans (Scalable_Mount_Point_RS.enable and Scalable_Mount_Point_RS.disable)
The Scalable_Mount_Point_RS.enable and Scalable_Mount_Point_RS.disable plans enable you to enable and disable a resource deployed through the Scalable_Mount_Point_RS component. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the scalable mount point resource to enable or disable.
Top
Shared QFS File System Resource Installation Plan (Shared_QFS_RS.create)
The Shared_QFS_RS.create plan creates a Sun Cluster shared QFS resource. Deploy this plan after a Shared_QFS_RG component has been deployed. The rg_name must be set to the installName of that component. The plan operates according to the rules that are described in Sun Cluster Resource Install/Attach/Modify Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. These nodes must also match the current node list of the resource group that contains the resource. |
The plan has a single plan variable:
- (Optional) Whether to enable the shared QFS resource on creation.
The shared QFS resource component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables is null.
- The value of QFSFileSystem is not an absolute path.
- The SUNWqfsr or SUNWqfsu packages are not installed on the nodes.
- A shared QFS resource group component is not installed on the nodes.
Top
Shared QFS File System Resource Deinstallation Plan (Shared_QFS_RS.remove)
The Shared_QFS_RS.remove plan removes a Sun Cluster shared QFS (metadata server) resource. The plan operates according to the rules that are described in Sun Cluster Resource Remove Semantics. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. These nodes must not be in the current node list of the resource group that contains the resource. Therefore the resource group must be shrunk first. |
The plan has a single plan variable:
- The name of the shared QFS resource to remove.
Top
Shared QFS File System Resource Enable/Disable Plans (Shared_QFS_RS.enable and Shared_QFS_RS.disable)
The Shared_QFS_RS.enable and Shared_QFS_RS.disable plans enable you to enable and disable a resource deployed through the Shared_QFS_RS component. Target nodes must be of type com.sun.oracle10g_RAC#ClusterNodeHT.
| Note
This component uses a synchronized enable or disable plan. You can target any node on which the resource is present. The enable or disable operation will be performed only once. |
The plan has a single plan variable:
- The name of the shared QFS resource to enable or disable.
Oracle Component Plans
This section describes the following Oracle component plans:
Top
Oracle Clusterware Installation Plan (CRS.install)
The CRS.install plan installs Oracle Clusterware (CRS) on one or more Sun Cluster nodes. The component must only be deployed after the Oracle_User, RAC_framework_RG, and associated RAC_framework, RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm, or RAC_hwraid components have been deployed. There must only be one Oracle Clusterware framework that runs on a Sun Cluster configuration at any one time. Therefore, only attempt to deploy the Oracle Clusterware component once to a particular installPath (or Oracle CRS HOME directory). If you need to change the installPath, remove all Oracle components, including CRS, and then redeploy by using the new path. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT.
| Note
All the nodes in the cluster must be active when this plan runs. This requirement is to ensure that the correct operation is performed and that no previous CRS installation exists on a node that has not been targeted by the plan. |
The component has install, attach, and expand semantics that enable it to handle cases where CRS might have been installed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If CRS is not installed on any node in the cluster in the given installPath, then a fresh installation is performed.
- If CRS is installed in the installPath only on the nodes targeted, that is, the CRS node list matches the plan target list, then the component performs an attach. The other component variables are ignored. This means that you cannot change or add languages, or add or change the OCR or voting disks by using this approach.
- If CRS is installed on nodes which form a subset of the nodes targeted, then the plug-in assumes that you want to perform a CRS expansion. CRS is then installed on all of the nodes that it is not currently installed on.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. |
The plan has a single plan variable:
The CRS component installation will fail if any of the following conditions exist:
- Any of the target host variables are null.
- The target VIP host IP address or netmask does match a ... format.
- Any of the mandatory component variables is null.
- The ORACLE_BASE, ORACLE_HOME (installPath), or mediaLocation component variable isn't an absolute path, that is, starts with a slash (/) or has a trailing space.
- The OCR and voting disk device lists don't have names with absolute paths.
- The node list has spaces in (it should be comma separated only).
- The ssh root passphrase has not been set up correctly.
- The /etc/system parameters are insufficient on Solaris 9 OS.
- Any part of the CRS installation exits with an Oracle error.
- The Oracle user component has not been installed.
- The RAC framework resource component has not been installed.
As part of the second step in the install plan on each node, the shared memory and semaphore settings are tested. If these are insufficient on Solaris 10 OS, then the plan uses /usr/sbin/prctl to set suitable values for user root and project default. However, these settings will be lost across reboots and any database instances that are configured might fail to start.
| Note
Check the standard output of step 2 of the installation plan on a Solaris 10 system to see whether any /etc/system parameter settings are recommended |
Top
Oracle Clusterware Deinstallation Plan (CRS.remove)
The CRS.remove plan removes Oracle Clusterware (CRS) from one or more Sun Cluster nodes. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT.
| Note
The "markOnly" uninstall plan for this component can be used in cases where the CRS.remove plan fails and you need to remove the CRS component. The component has contract and remove semantics that enable it to handle cases where CRS might have been removed or modified outside the N1 SPS environment. |
The rules for these semantics are as follows:
- If CRS is not installed on a target node, the component is removed.
- If CRS is only installed on the nodes that are targeted by the plan, the plug-in assumes that you want to completely remove CRS.
- If the nodes that are targeted by the plan form a subset of the current nodes on which CRS is installed, the plug-in assumes that you want to shrink the deploy. CRS will only be removed from those nodes that have been targeted.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has a single plan variable:
The CRS component deinstallation will fail if any of the following conditions exist:
- The ssh root passphrase has not been set up correctly.
- Any part of the CRS deinstallation returns an Oracle error.
Top
Oracle RAC Installation Plan (RAC.install)
The RAC.install plan installs Oracle RAC software on one or more Sun Cluster nodes into the specified ORACLE_HOME. An individual node might have more than one ORACLE_HOME, thereby requiring the component to be deployed several times. The component must only be deployed after the Oracle_User, RAC_framework_RG and associated RAC_framework, RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm or RAC_hwraid and CRS components have been deployed. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT.
The component has install, attach, and expand semantics that enable it to handle cases where RAC might have been installed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If RAC is not installed on any node in the cluster in the given installPath, a fresh installation is performed.
- If RAC is installed in the installPath only on the nodes targeted, that is, the RAC node list matches the plan target list, the component performs an attach. The other component variables are ignored. This means that you cannot change or add languages or change the installation type, that is, from SE to EE or the reverse, by using this approach.
- If RAC is installed on nodes which form a subset of the nodes targeted, the plug-in assumes that you want to perform a RAC expansion. RAC is then installed on all of the nodes that it is not currently installed on.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes on which you want the component in the "To Be" state. |
The plan has a single plan variable:
The RAC component installation will fail if any of the following conditions exist:
- Any of the target host variables are null.
- The installation type is not EE or SE.
- The ORACLE_HOME (installPath) or mediaLocation component variable isn't an absolute path, that is, starts with a slash (/) or has a trailing space.
- The node list has spaces in (it should be comma separated only).
- Any of the Oracle install return an error.
- The CRS component has not been deployed to the target nodes.
Top
Oracle RAC Deinstallation Plan (RAC.remove)
The RAC.remove plan removes Oracle RAC software for a specific ORACLE_HOME from one or more Sun Cluster nodes. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT.The "markOnly" uninstall plan for this component can be used in cases where the RAC.remove plan fails and you need to remove the RAC component. The component has contract and remove semantics that enable it to handle cases where RAC might have been removed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If RAC is not installed on a target node, the component is removed.
- If RAC is only installed on the nodes targeted by the plan, the plug-in assumes that you want to completely remove RAC.
- If the nodes that are targeted by the plan form a subset of the current nodes on which RAC is installed, the plug-in assumes that you want to shrink the deploy. RAC will only be removed from those nodes that have been targeted.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has two plan variables:
- The ssh root passphrase.
- The ORACLE_HOME to remove.
The RAC component deinstallation will fail if any of the following conditions exist:
- The ssh root passphrase has not been set up correctly.
- Any part of the RAC deinstallation returns an Oracle error.
Top
Automatic Storage Management (ASM) Database Installation Plan (ASM.create)
The ASM.create plan installs an Oracle ASM database on one or more Sun Cluster nodes. Deploy the component only after the Oracle_User, RAC_framework_RG and associated RAC_framework, RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm or RAC_hwraid, CRS, and RAC components have been deployed. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has install, attach, and expand semantics that enable it to handle cases where an ASM database might have been installed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If ASM is not installed on any node in the cluster by using the given installPath (ORACLE_HOME), a fresh installation is performed.
- If ASM exists for the specified installPath (ORACLE_HOME) only on the nodes targeted, that is, the ASM node list matches the plan target list, the component performs an attach. The other component variables are ignored. This means that you cannot change redundancy levels, add new disks, or change the enterprise management method. For these operations, use the standard Oracle tools.
- If ASM is installed on nodes which form a subset of the nodes targeted, the plug-in assumes that you want to perform a ASM expansion. ASM instances are then installed on all of the nodes that ASM is not currently present on.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes you want the component on in the "To Be" state. |
The plan has three plan variables:
- A tick box for whether the LUNs specified should have the first 10MB of the disk scrubbed (zeroed). This is needed in cases where the LUNs have been used for ASM before. The disk scrubbing is only performed if this is a fresh installation. It is not done if this is an ASM instance addition.
- The ssh root passphrase.
- The password for the ASM database.
The ASM component type installation will fail if any of the following conditions exist:
- Any of the mandatory component variables are null.
- The ASM password is null.
- The redundancy is not HIGH, NORMAL, or EXTERNAL.
- The emConfiguration is not CENTRAL or NONE.
- The recoveryGroupName is set but the either the recoveryDiskList or the recoveryGroupRedundancy component variables is null.
- The recoveryGroupName is set but the recoveryGroupRedundancy is HIGH, NORMAL, or EXTERNAL.
- The emConfiguration is CENTRAL but centralAgent is not set.
- The diskString does not have absolute paths, that is, has a leading slash (/) or has a space in the list (it should be comma separated only).
- The node list has a space in the list (it should be comma separated only).
- The ASM creation fails for reasons based on Oracle logic.
Top
Automatic Storage Management (ASM) Database Deinstallation Plan (ASM.remove)
The ASM.remove plan removes Oracle ASM database instances from one or more Sun Cluster nodes. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has contract and remove semantics that enable it to handle cases where ASM might have been removed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If an ASM instance is not installed on a target node, the component is removed.
- If the ASM database is only installed on the nodes targeted by the plan, the plug-in assumes you want to completely remove the ASM database.
- If the nodes targeted by the plan form a subset of the current nodes on which the ASM database is installed, the plug-in assumes that you want to shrink the deploy. ASM instances will only be removed from those nodes that have been targeted.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has one plan variable:
The ASM component deinstallation will fail if any of the following conditions exist:
- The ssh root passphrase has not been set up correctly.
- Any part of the ASM deinstallation returns an Oracle error.
Top
Oracle Database Stored on ASM Installation Plan (Database_on_ASM.create)
The Database_on_ASM.create plan installs an Oracle database whose storage is managed by ASM on one or more Sun Cluster nodes. The component must only be deployed after the Oracle_User, RAC_framework_RG and associated RAC_framework, RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm or RAC_hwraid, CRS, RAC and ASM components have been deployed. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has install, attach, and expand semantics that enable it to handle cases where the database might have been installed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If database is not installed on any node in the cluster by using the given installPath (ORACLE_HOME), then a fresh installation is performed.
- If the database exists for the specified installPath (ORACLE_HOME) only on the nodes targeted, that is, the database node list matches the plan target list, then the component performs an attach. The other component variables are ignored. This means that you cannot change redundancy levels, add new disks or change the enterprise management method, and so forth. For these operations, the standard Oracle tools should be used.
- If database is installed on nodes which form a subset of the nodes targeted, then the plug-in assumes you want to perform a database expansion. Database instances are then installed on all of the nodes that it is not currently present on. In the latter two cases, the plug-in does not distinguish between databases that have previously been configured on ASM and other storage options. You should therefore exercise caution when you use the attach and expand options.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes you want the component on in the "To Be" state. |
The plan has seven plan variables:
- The password for the ASM database sys user.
- The password to assign to the sys database user.
- The password to assign to the system database user.
- The password to assign to the DBSNMP database user (defaults to sysPassword if blank).
- The password to assign to the sysman database user (defaults to sysPassword if blank).
- The password for host user backup jobs (only required if backups are scheduled).
- The cluster root ssh passphrase.
The Database_on_ASM component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables are null.
- The emConfiguration component variable has not been set to CENTRAL, LOCAL, ALL, NOBACKUP, NOEMAIL, or NONE.
- The node list has a space in the list (it should be comma separated only).
- The emConfiguration is CENTRAL but centralAgent is not set.
- The emConfiguration component variable is not NOBACKUP or NONE and the backupSchedule does not match [0-9][0-9]:[0-9][0-9].
- The initParams or listeners have a space in the list (it should be comma separated only).
- The memoryPercentage component variable is set but is not a number between 1 and 100.
- The diskGroupName is null.
- The ASM component is not installed on the node.
- The database creation returns an Oracle error.
| Note
Check the Oracle dbca output log created as a result of this plan for any non-fatal errors. The name of this log can be found in the standard output of the lowest cluster node id targeted by the plan. |
If the database is created successfully, but the instances do not start, check the shared memory parameters and if necessary restart CRS or the system with appropriate settings.
Top
Oracle Database Stored on ASM Installation Plan (Database_on_ASM.remove)
The Database_on_ASM.remove plan removes an Oracle database or instance, whose storage is managed by ASM, from one or more Sun Cluster nodes. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has contract and remove semantics that enable it to handle cases where the database might have been removed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If a Database_on_ASM instance is not installed on a target node then the component is removed.
- If the database is only installed on the nodes targeted by the plan, then the plug-in assumes you want to completely remove the database.
- If the nodes targeted by the plan form a subset of the current nodes on which the database is installed, then the plug-in assumes you want to shrink the deploy. Database instances will only be removed from those nodes that have been targeted.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has three plan variables:
- The password to assign to the sys database user.
- The global database name of the instance to remove.
- The ssh root passphrase.
The Database_on_ASM component deinstallation will fail if any of the following conditions exist:
- The ssh root passphrase has not been set up correctly.
- Any part of the database deinstallation returns an Oracle error.
Top
Oracle Database Stored on Shared QFS File System Installation Plan (Database_on_QFS.create)
The Database_on_QFS.create plan installs an Oracle database whose storage is located on shared QFS file systems on one or more Sun Cluster nodes. The component must only be deployed after the Oracle_User, RAC_framework_RG and associated RAC_framework, RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm or RAC_hwraid, CRS, RAC, and optionally Shared_QFS, components have been deployed. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has install, attach, and expand semantics that enable it to handle cases where the database might have been installed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If database is not installed on any node in the cluster by using the given installPath (ORACLE_HOME), then a fresh installation is performed.
- If the database exists for the specified installPath (ORACLE_HOME) only on the nodes targeted, that is, the database node list matches the plan target list, then the component performs an attach. The other component variables are ignored. This means that you cannot change the data file location or change the enterprise management method, and so forth. For these operations, the standard Oracle tools should be used.
- If database is installed on nodes which form a subset of the nodes targeted, then the plug-in assumes you want to perform a database expansion. Database instances are then installed on all of the nodes that it is not currently present on. In the latter two cases, the plug-in does not distinguish between databases that have previously been configured on shared QFS and other storage options. You should therefore exercise caution when you use the attach and expand options.
| Note
This component uses a synchronized installation or attach plan. Target all the nodes you want the component on in the "To Be" state. |
The plan has six plan variables:
- The password to assign to the sys database user.
- The password to assign to the system database user.
- The password to assign to the DBSNMP database user (defaults to sysPassword if blank).
- The password to assign to the sysman database user (defaults to sysPassword if blank).
- The password for host user backup jobs (only required if backups are scheduled).
- The cluster root ssh passphrase.
The Database_on_QFS component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables are null.
- The emConfiguration component variable has not been set to CENTRAL, LOCAL, ALL, NOBACKUP, NOEMAIL or NONE.
- The node list has a space in the list (it should be comma separated only).
- The emConfiguration is CENTRAL but centralAgent is not set.
- The emConfiguration component variable is not NOBACKUP or NONE and the backupSchedule does not match [0-9][0-9]:[0-9][0-9].
- The initParams or listeners have a space in the list (it should be comma separated only).
- The memoryPercentage component variable is set but is not a number between 1 and 100.
- The datafileDestination component variable is null.
- The SUNWqfsr or SUNWqfsu packages are not installed on the nodes.
- The RAC component is not installed on the nodes.
- The database creation returns an Oracle error.
| Note
Check the Oracle dbca output log created as a result of this plan for any non-fatal errors. The name of this log can be found in the standard output of the lowest cluster node id targeted by the plan. |
If the database is created successfully, but the instances do not start, check the shared memory parameters and if necessary restart CRS or the system with appropriate settings.
Top
Oracle Database Stored on Shared QFS File System Installation Plan (Database_on_QFS.remove)
The Database_on_QFS.remove plan removes an Oracle database or instance, whose data files are stored on shared QFS, from one or more Sun Cluster nodes. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has contract and remove semantics that enable it to handle cases where the database might have been removed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If a Database_on_QFS instance is not installed on a target node then the component is removed.
- If the database is only installed on the nodes targeted by the plan, then the plug-in assumes you want to completely remove the database.
- If the nodes targeted by the plan form a subset of the current nodes on which the database is installed, then the plug-in assumes you want to shrink the deploy. Database instances will only be removed from those nodes that have been targeted.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has three plan variables:
- The password to assign to the sys database user.
- The global database name of the instance to remove.
- The ssh root passphrase.
The Database_on_QFS component deinstallation will fail if any of the following conditions exist:
- The ssh root passphrase has not been set up correctly.
- Any part of the database deinstallation returns an Oracle error.
Top
Oracle Database Stored on raw Disk Installation Plan (Database_on_RAW.create)
The Database_on_RAW.create plan installs an Oracle database whose storage is located on raw global LUNs or device group volumes, on one or more Sun Cluster nodes. The component must only be deployed after the Oracle_User, RAC_framework_RG and associated RAC_framework, RAC_udlm (SPARC only) and volume manager, RAC_svm, RAC_cvm or RAC_hwraid, CRS, RAC components have been deployed. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has install and attach semantics that enable it to handle cases where the database might have been installed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If database is not installed on any node in the cluster by using the given installPath (ORACLE_HOME), then a fresh installation is performed.
- If the database exists for the specified installPath (ORACLE_HOME) only on the nodes that are targeted, that is, the database node list matches the plan target list, then the component performs an attach. The other component variables are ignored. This means that you cannot change redundancy levels, add new disks or change the enterprise management method. For these operations, the standard Oracle tools should be used.
| Note
This component does not currently support instance expansion. In the latter two cases, the plug-in does not distinguish between databases that have previously been configured on raw disk and other storage options. You should therefore exercise caution when you use the attach option.
This component uses a synchronized installation or attach plan. Target all the nodes you want the component on in the "To Be" state. |
The plan has six plan variables:
- The password to assign to the sys database user.
- The password to assign to the system database user.
- The password to assign to the DBSNMP database user (defaults to sysPassword if blank).
- The password to assign to the sysman database user (defaults to sysPassword if blank).
- The password for host user backup jobs (only required if backups are scheduled).
- The cluster root ssh passphrase.
The Database_on_RAW component installation will fail if any of the following conditions exist:
- Any of the mandatory component variables are null.
- The emConfiguration component variable has not been set to CENTRAL, LOCAL, ALL, NOBACKUP, NOEMAIL, or NONE.
- The node list has a space in the list (it should be comma separated only).
- The emConfiguration is CENTRAL but centralAgent is not set.
- The emConfiguration component variable is not NOBACKUP or NONE and the backupSchedule does not match [0-9][0-9]:[0-9][0-9].
- The initParams or listeners have a space in the list (it should be comma separated only).
- The memoryPercentage component variable is set but is not a number between 1 and 100.
- The datafileNames component variable is null or does not have an absolute path name.
- The datafilesNames file does not contain entries for the data files for: system, sysaux, example, users, temp, control1 , control2, spfile, pwdfile, undotbs (one per instance) and redoX_{1,2} (two per instance).
- The device given is not readable from all nodes.
- The RAC component is not installed on the nodes.
- The database creation returns an Oracle error.
| Note
Check the Oracle dbca output log created as a result of this plan for any nonfatal errors. The name of this log can be found in the standard output of the lowest cluster node id targeted by the plan. |
If the database is created successfully, but the instances do not start, check the shared memory parameters and if necessary restart CRS or the system with appropriate settings.
Top
Oracle Database Stored on raw Disk Installation Plan (Database_on_RAW.remove)
The Database_on_RAW.remove plan removes an Oracle database or instance, whose data files are stored on raw global LUNs or shared device group volumes, from one or more Sun Cluster nodes. Target nodes must be of type com.sun.oracle10g_RAC#OracleCRS_HT. The component has contract and remove semantics that enable it to handle cases where the database might have been removed or modified outside the N1 SPS environment.
The rules for these semantics are as follows:
- If a Database_on_RAW instance is not installed on a target node then the component is removed.
- If the database is only installed on the nodes targeted by the plan, then the plug-in assumes you want to completely remove the database.
- If the nodes targeted by the plan form a subset of the current nodes on which the database is installed, then the plug-in assumes you want to shrink the deploy. Database instances will only be removed from those nodes that have been targeted.
| Note
This component uses a synchronized removal plan. Target only the nodes that you want to delete from the current configuration. |
The plan has three plan variables:
- The password to assign to the sys database user.
- The global database name of the instance to remove.
- The ssh root passphrase.
The Database_on_RAW component deinstallation will fail if any of the following conditions exist:
- The ssh root passphrase has not been set up correctly.
- Any part of the database deinstallation returns an Oracle error.
| 
Sign up or Log in to add a comment or watch this page.