How to Register and Configure HA for Oracle External Proxy

Complete the registration and configuration on any cluster member.

Before You Begin

Ensure that you have completed the requirements as described in Configuration Requirements.

1. On a cluster member, become an administrator that provides solaris.cluster.admin authorization.
2. Register the ORCL.oracle_external_proxy resource type for the data service.

   # clresourcetype register ORCL.oracle_external_proxy

3. Create either a scalable or a failover resource group for the Oracle External Proxy resource.

   For example, to create a scalable resource group, do the following:

   # clresourcegroup create -S [-n node-zone-list]  resource-group

   resource-group

   Specifies the name of the scalable service resource group to add.

   –n node-zone-list

   Specifies a comma-separated, ordered list of nodes that can master this resource group. This list is optional. If you omit this list, then all the nodes of the global cluster or zone cluster are used to master the resource group.

4. Create an Oracle External Proxy resource in the resource group that you created.

   # clresource create -g resource-group \
   -t ORCL.oracle_external_proxy  
   -p service_name=service-name \ 
   -p ons_nodes=ons-nodes \
   -p dbuser=dbuser \
   [-p plugin_name=plugin-name] \
   [-p tns_admin=tns-admin] \
   -d  \
   resource

   –g resource-group

   Specifies the name of the resource group .

   –t resource-type

   Specifies the resource type to add.

   –p service_name=service-name

   Specifies the Oracle Database or Real Application Clusters (RAC) service name that the Oracle External Proxy uses to connect to the database.

   –p ons_nodes=ons-nodes

   Specifies the Remote Oracle Notification Service (ONS) nodes that the Oracle External Proxy uses to connect to the database. For a remote Oracle database, specify ONS_NODES=scan:port or ONS_NODES=node:port[node:port]. For a local Oracle database, specify ONS_NODES=localhost:port.

   ---

   Note -  For a remote Oracle Database 11gR2 or later with Grid Infrastructure installed, it is recommended to use scan_name:port.

   ---

   –p dbuser=dbuser

   Specifies the server side Oracle database user that the Oracle External Proxy uses to connect to the database. If the database is being used as a standby database, you must grant the sysdba privilege to the user, and specify dbuser="hauser as sysdba" where hauser represents your entry for dbuser. For information on how to grant the sysdba privilege to the user, see Remote Database User.

   –p plugin_name=plugin-name

   Specifies the plugin module that the Oracle External Proxy uses to connect to the database. You can omit this entry as it will default to OracleExternalProxy.

   –p tns_admin=tns-admin

   Specifies the client-side location for the Oracle tns_admin path that the Oracle External Proxy uses to connect to the database. Omit this entry so that it defaults to the /var/opt/oracle directory.

   –d

   Creates the resource in the disabled state.

   resource

   Specifies your choice for the name of the resource to add.

   ---

   Note -  Optionally, you can set additional extension properties that belong to the Oracle External Proxy data service to override their default values. See Appendix A, HA for Oracle External Proxy Extension Properties for a list of extension properties.

   ---

5. Bring the resource group online.

   # clresourcegroup online -emM resource-group

   resource-group

   Specifies the name of the resource group.

   The Oracle Solaris Cluster resource is now configured and online, thereby interrogating the state of the remote database.

Example 1-5  Creating an ORCL.oracle_external_proxy Resource

This example shows the commands for performing the following operations which create a scalable multi-master ORCL.oracle_external_proxy resource on a two-node cluster.

• Creating the oep-rg resource group

• Registering the ORCL.oracle_external_proxy resource type

• Adding the oep-rs resource to the oep-rg resource group

This example assumes that default values are being used for the dbuser, tns_admin, and plugin_name extension properties. It also assumes that the dbuser password has been encrypted on each cluster node.

phys-schost-1# clresourcetype register ORCL.oracle_external_proxy
phys-schost-1# clresourcegroup create -S oep-rg
phys-schost-1# clresource create -g oep-rg \
-t ORCL.oracle_external_proxy \
-p service_name=orcl \
-p ons_nodes=binks-scan-lh:6200 \
-d \
oep-rs
phys-schost-1# clresourcegroup online -M oep-rg
phys-schost-1# clresource enable oep-rs

Example 1-6  Registering Failover HA for Oracle External Proxy

The following example shows how to register a failover Oracle External Proxy service.

phys-schost-1# clresourcetype register ORCL.oracle_external_proxy
phys-schost-1# clresourcegroup create oep-rg
phys-schost-1# clresource create -g oep-rg \
-t ORCL.oracle_external_proxy \
-p service_name=orcl \
-p ons_nodes=binks-scan-lh:6200 \
-d \
oep-rs
phys-schost-1# clresourcegroup online -M oep-rg
phys-schost-1# clresource enable oep-rs

Example 1-7  Creating an Oracle External Proxy Resource for a Local Oracle Database

The following example shows how to create an Oracle External Proxy resource for a local Oracle database.

phys-schost-1# clresourcetype register ORCL.oracle_external_proxy
phys-schost-1# clresourcegroup create -S oep-rg
phys-schost-1# clresource create -g oep-rg \
-t ORCL.oracle_external_proxy \
-p service_name=sales \
-p ons_nodes=localhost:6100 \
-d \
oep-rs
phys-schost-1# clresourcegroup online -M oep-rg
phys-schost-1# clresource enable oep-rs