| Oracle® Beehive Installation Guide Release 1 (1.2 and 1.3) for Linux Part Number E10481-06 |
|
|
View PDF |
| Oracle® Beehive Installation Guide Release 1 (1.2 and 1.3) for Linux Part Number E10481-06 |
|
|
View PDF |
This module describes how to install and configure Oracle Beehive to support deployment on multiple Oracle Real Application Clusters (RAC) nodes. It covers the following topics:
Adding Oracle RAC Nodes to an Existing Oracle Beehive Instance
Installing Multiple Oracle Beehive Instances with Oracle RAC
Note:
You may use Database Configuration Assistant (DBCA) to create Oracle RAC nodes. However, refer to OracleMetaLink Note 342419.1 to properly configure the LOCAL_LISTENER initialization parameter.This module uses the following naming conventions:
Global service name of the Oracle RAC database to be used: MYDB
Number of Oracle RAC nodes: R
SID of first Oracle RAC node: MyDB1
SID of second Oracle RAC node: MyDB2
SID of Rth Oracle RAC node: MyDBR
Virtual Internet Protocol (VIP) host names and listener port numbers for each Oracle RAC node: HOST-VIP1:PORT1 to HOST-VIPR:PORTR
Oracle Notification Services (ONS) host names and remote port numbers for each Oracle RAC node: ONS_HOST1:ONS_PORT1 to ONS_HOSTR:ONS_PORTR
Note:
The location of the archive redo logs for each Oracle RAC node must be accessible by all nodes in your Oracle RAC database.Refer to "Managing Archived Redo Logs Using RMAN in Oracle Real Application Clusters" in Chapter 5, "Configuring Recovery Manager And Archiving" in Oracle Real Application Clusters Administration and Deployment Guide for more information.
These steps consist of the following:
Step 1 Create Multiple Database Services
At any given time, the database service connects to only one instance of Oracle RAC. For proper load balancing, create multiple logical database services.
The number of database services to create should be between three times the number of Oracle RAC nodes to four times the number of Oracle RAC nodes.
In the following example, N is the number of database services to create. The names of these database services are Service1, Service2, to ServiceN.
The following command creates a database service for an Oracle RAC database with three nodes:
srvctl add service -d MYDB -s Service1 -r MyDB1 -a MyDB2, MyDB3
Service1 runs on MyDB1. If MyDB1 fails, the service will be failover to MyDB2. Do not use the same Oracle RAC node as the primary node for all the services. Use different RAC nodes as primary nodes and secondary nodes for proper load balancing in failover. The following examples demonstrate this:
srvctl add service -d MYDB -s Service2 -r MyDB2 -a MyDB3, MyDB1 srvctl add service -d MYDB -s Service3 -r MyDB3 -a MyDB1, MyDB2 srvctl add service -d MYDB -s Service4 -r MyDB1 -a MyDB3, MyDB2
Step 2 Start All Database Services
Start all database services that you created. The following command starts Service1:
srvctl start service -d MYDB -s Service1
Step 3 Enable DTP for Database Services
Enable X/Open Distributed Transaction Processing (DTP) for all database services. The following command enables DTP for Service1. Run this command in SQL*Plus with system privileges:
execute dbms_service.modify_service (service_name => 'Service1', dtp => true);
Step 4 Enable Secure ONS Notification
You may ignore this step if your deployment does not require SSL notification.
Note:
You must perform this step if you wish to install Oracle Beehive with Oracle Beehive Provisioning Application. Refer to "Installing Oracle Beehive with Provisioning Application" for more information.This step involves specifying the Oracle Wallet directory ons.config, As a result Oracle Cluster Ready Services (CRS) will use SSL when communicating with other nodes (other Oracle RAC nodes and Oracle Beehive instances) and require SSL certificate authentication from all Oracle Notification Services (ONS) instances that try to connect to it.
To enable SSL ONS notification, add the following line to all <Oracle Cluster Ready Services home>/opmn/conf/ons.config files of each Oracle RAC node:
walletfile=MY_SECURE_WALLER_DIR
MY_SECURE_WALLER_DIR is your Oracle Wallet directory. Refer to "Configuring TLS with Oracle Wallet" for information about configuring Oracle Wallet.
Step 5 Manually Create ORABPEL Tablespace
If your Oracle RAC database uses raw storage, you must manually create the tablespace ORABPEL before running the Oracle Beehive Install Wizard. To do this, run the following command:
CREATE TABLESPACE ORABPEL DATAFILE '/dev/raw/raw1' SIZE 100M
AUTOEXTEND ON NEXT 30M MAXSIZE UNLIMITED;
/dev/raw/raw1 is the name of the data file to create for the ORABPEL tablespace.
Install Oracle Beehive with the Oracle Beehive Install Wizard. Enter the following database information:
Host and Port: HOST-VIP1:PORT1^HOST-VIP2:PORT2^HOST-VIP3:PORT3
Service Name: Service1. Use the database service name you created in the step Step 1, "Create Multiple Database Services". (Do not use the actual service name. For example, do not use MYDB, use Service1.)
Note:
During the installation of Oracle Beehive, ensure the first Oracle RAC node (MyDB1) remains up. Otherwise, the install will fail due to bug 5693566 (Web Services Manager Configuration Assistant will fail).These steps update Oracle Beehive with the Oracle RAC global service name and the multiple database service names:
Step 1 Backup Bootstrap File
The file <Oracle home>/beehive/conf/beehiveconfig.xml contains the bootstrap database connect information. Make a backup of this file before applying any post-install steps.
Step 2 Retrieve Site and Database Object System Identifiers
Retrieve the following system identifiers. You will need them for the following steps:
Site System Identifier:Use the following beectl command to retrieve the Oracle Beehive site system identifier. In the following steps, <site_id> represents this value:
beectl list_components --type Site
Database Object System Identifier: Use the following beectl command to retrieve the default database system identifier. In the following steps, <database_system_object_id> represents this value:
beectl list_properties --component <site_id>
This command lists all the properties of <site_id>. The value of <database_system_object_id> is the value of the property Database.
Step 3 Modify Connect String
List the properties of <database_system_object_id> with the following command:
beectl list_properties --component <database_system_object_id>
Change the value of the ConnectDescriptor property. Substitute the database service name (in this example, Service1) with the global service name (MYDB). For example, suppose the following is the value of the ConnectDescriptor property (line breaks and extra spaces added for clarity):
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=yes)(FAILOVER=on)
(ADDRESS=(PROTOCOL=TCP)(HOST=HOST-VIP1)(PORT=PORT1))
(ADDRESS=(PROTOCOL=TCP)(HOST=HOST-VIP2)(PORT=PORT2))
)
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=Service1))
)
You would change it to the following:
(DESCRIPTION=
(ADDRESS_LIST=
(LOAD_BALANCE=yes)(FAILOVER=on)
(ADDRESS=(PROTOCOL=TCP)(HOST=HOST-VIP1)(PORT=PORT1))
(ADDRESS=(PROTOCOL=TCP)(HOST=HOST-VIP2)(PORT=PORT2))
)
(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=MYDB))
)
In the following steps <modified_connect_string> will represent this value.
Step 4 Update Bootstrap File with Connect String
Use the following command to update the database system object and the local bootstrap file with the connect string you modified in the previous step:
beectl modify_bootstrap_configuration --connect_string "<modified_connect_string>"
Note:
You must enclose the connect string with quotation marks.Step 5 Update Database System Object
Modify the database system object's configuration to specify the database services you created and the ONS remote ports that are listening on your Oracle RAC nodes. The following example specifies three database services with the xa_service_names option, and two ONS remote ports with the ons_entry option:
beectl modify_database --database <database_system_object_id> --xa_service_names Service1 --xa_service_names Service2 --xa_service_names Service3 --ons_entry ONS_HOST1:ONS_PORT1 --ons_entry ONS_HOST2:ONS_PORT2
Step 6 Commit Configuration Changes
Call beectl activate_configuration on your Oracle Beehive instance. Afterwards, call beectl modify_local_configuration_files on the same Oracle Beehive instance.
Note:
Thebeectl modify_local_configuration_files command will ask you to run this command on all your other Oracle Beehive instances. Do not run this command on all your other instances at this time.
If you have, or plan to have, more than Oracle Beehive instance, refer to "Installing Multiple Oracle Beehive Instances with Oracle RAC".
Step 7 Restart Oracle Beehive
Restart your Oracle Beehive instance. You may use the beectl restart --all command.
Note:
You must restart Oracle Beehive (after callingbeectl modify_local_configuration) if you modify the ONS details in the database system object's configuration (as you have done previously).Step 8 Register for ONS Notification
By default, Oracle Beehive is configured to receive secure ONS notifications, which is recommended. If your Oracle RAC nodes are configured for SSL ONS notification, you may ignore this step.
If not, update the file <Oracle home>/opmn/conf/opmn.xml as follows in all Oracle Beehive instances to disable SSL ONS notifications:
In the file opmn.xml, in the ssl element, set the enabled attribute to false:
<ssl enabled="false" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
After changing the opmn.xml file, run the following beectl commands:
beectl list_components --type OpmnCluster -----------------+-------------------------------------------------------------- Component type | Component identifier -----------------+-------------------------------------------------------------- OpmnCluster | 5987aa04-2984-43ab-8752-8c27e0c45130 -----------------+-------------------------------------------------------------- 1 Record(s) displayed. beectl list_properties --component 5987aa04-2984-43ab-8752-8c27e0c45130 -----------------------------+-------------------------------------------------- Property name | Property value -----------------------------+-------------------------------------------------- Alias | -----------------------------+-------------------------------------------------- NotificationServerSslEnabled | true -----------------------------+-------------------------------------------------- Opmns | opmn_Beehive_R1.example.com -----------------------------+-------------------------------------------------- Site | _CURRENT_SITE -----------------------------+-------------------------------------------------- 4 Record(s) displayed. beectl modify_property --component 5987aa04-2984-43ab-8752-8c27e0c45130 --name NotificationServerSslEnabled --value false Changes to configuration repository are not activated. Successfully stored the property for component id 5987aa04-2984-43ab-8752-8c27e0c45130. beectl activate_configuration Local configuration files are not in sync with system model. Please run "modify_local_configuration_files" manually. Proposed configuration is saved successfully and activated now. beectl modify_local_configuration_files
The following example adds an Oracle RAC node named MyDB3 to an Oracle Beehive instance with the following characteristics:
Contains two Oracle RAC nodes named MyDB1 and MyDB2
Contains six database services named Service1 through Service6
For Service1, Service3, and Service5, the preferred database instance is MyDB1 and the available database instance is MyDB2
For Service2, Service4, and Service6, the preferred database instance is MyDB2 and the available database instance is MyDB1
Shutdown MyDB2 and CRS.
Start CRS. Start ASM instances, the node applications, and the instance of MyDB3.
For Service1, Service3, and Service5, change the available database instance from MyDB2 to MyDB3:
srvctl modify service -d MYDB -s Service1 -n -i MyDB1 -a MyDB3 srvctl modify service -d MYDB -s Service3 -n -i MyDB1 -a MyDB3 srvctl modify service -d MYDB -s Service5 -n -i MyDB1 -a MyDB3
For Service2, Service4, and Service6, change the available database instance from MyDB2 to MyDB3:
srvctl modify service -d MYDB -s Service2 -n -i MyDB3 -a MyDB1 srvctl modify service -d MYDB -s Service4 -n -i MyDB3 -a MyDB1 srvctl modify service -d MYDB -s Service6 -n -i MyDB3 -a MyDB1
Start the databases that have stopped (Service1, Service3, and Service5).
Oracle Beehive supports the following ways to install multiple instances Oracle Beehive with Oracle RAC:
Install All Oracle Beehive Instances, then Apply Post-Install Steps
Install One Oracle Beehive Instance, Apply Post-Install Steps, then Add Additional Instances
You can install multiple Oracle Beehive instances, then run the post-install steps afterwards on all those instances as described in this module:
Install all your Oracle Beehive instances. When entering the database information for each instance, use the same service name.
For one instance, apply all the post-installation steps.
For all the other instances, run the following post-installation steps:
Alternatively, instead of installing multiple Oracle Beehive instances then running the post-install steps on each one, you may install one Oracle Beehive instance, apply the post-install steps on that instance, then add additional Oracle Beehive instances.
After installing one Oracle Beehive instance and applying post-install steps, follow these steps:
Install other Oracle Beehive instances. When entering the database information, use the global service name as the server name.
Apply Step 8, "Register for ONS Notification" to all new instances.
