HP Serviceguard Toolkits for Database Replication Solutions Configuring Oracle Data Guard toolkit

Page 23

Table 5 Package attributes (continued)

Variable Name

Description

START_STANDBY_AS_PRIMARY

This parameter specifies whether the standby database

 

must be started as the primary database or not. It has to

 

be set to [yes] in the recovery package of the

 

Continentalclusters' recovery group. When primary

 

package goes down, the user must run the command

 

cmrecovercl to bring up the recovery package on the

 

recovery cluster. The recovery package executes the failover

 

commands and starts the new primary database (which

 

was originally the standby database before recovery

 

package startup).

 

NOTE: The toolkit displays a warning message during

 

package validation (In package apply cmapplyconf -P

 

and package check cmacheckconf -Pwhen this

 

parameter is set to [yes], stating that the parameter must

 

be used only in the recovery package of the

 

Continentalclusters environment. The toolkit thus alerts the

 

user to change its value to [no] if it is not a recovery

 

package.

ALERT_MAIL_ID

This parameter is used to specify the email address for

 

sending alerts.

NOTE:

The other parameters required by the ODG toolkit are sourced from ECMT Oracle/SGeRAC toolkit module.

While using ECMT Oracle/SGeRAC toolkit module with ODG toolkit module, the package configuration parameter START_MODE must always be set to [mount].

Configuring Oracle Data Guard toolkit

To create the logical volume infrastructure on shared disks, follow the instructions in the chapter Building an HA Cluster Configuration in the manual Managing HP Serviceguard. The disk must be available to all clustered nodes that are configured to run the ODG toolkit. Create file systems on all logical volumes on the volume groups.

The ODG toolkit can be configured in one of the following methods:

Install directory method: Scripts remain in the installation directory.

Configuration directory method: You must copy the scripts from the installation directory (including contents of subdirectories) to the configuration directory and define this location in the parameter TKIT_DIR in the package configuration file. You can modify the scripts in the configuration directory to add any specific requirements. Serviceguard first attempts to use the hadg.sh (or hadg_rac.sh) script in the configuration directory. If the script is not found in the configuration directory, it takes it from the installation directory.

Setting up Oracle Data Guard toolkit 23

Image 23
Contents HP Part Number Published August Edition Page Contents Glossary Index Introduction Advantages OverviewSingle-instance Oracle database Supported configurationDependencies Cmmakepkg -i pkgasciifile -m modulefilename outputfilename RAC environment RAC environmentServiceguard toolkit for Oracle Data Guard Data Guard replication between RAC primary and RAC standby Continentalclusters environment Continentalclusters environment Metrocluster and extended distance cluster environments Supported configuration Data Guard setup in an EDC environment Three data center configuration Multiple Data Guard instances in each Serviceguard cluster Configuring multiple instances of Oracle Data GuardHigh availability for data guard broker Setting up Oracle Data Guard toolkitInstalling and uninstalling Oracle Data Guard toolkit # swinstall -s depot path # swlist -l product T2259AA Files for the ADF module Activestandby Package attributes Configuring Oracle Data Guard toolkitFor example, /etc/cmcluster/pkg/dgpkg Single-instance environmentSetting up Oracle Data Guard toolkit #ecmt/oracle/oracle/LISTENERRESTART Servicefailfastenabled no servicehalttimeout For example, /etc/cmluster/pkg/racdgpkg RAC environmentWhere ocmnp is the Smnp package for Oracle CLusterware Maintaining Oracle Data Guard toolkit Adding the package to the Serviceguard clusterSingle-instance environment Cluster verification for Oracle Data Guard toolkitLimitations TroubleshootingPkg.conf command Startstandbyasprimary to yes Prerequisites Supported configuration Using the DB2 Hadr toolkitEvent 1 Standby database or Hadr goes down When primary and standby packages are in the same clusterEvent 2 Primary package fails Primary and Standby Packages in Different Clusters When primary and standby packages are in different clustersCmmakepkg -m ecmt/db2/db2 -m tkit/db2hadr/db2hadr pkg.conf Creating packagesTo provide high availability only to primary database Go to the /etc/cmcluster/hadrprimary directoryInstancename Hadrip And, $ cmmodpkg -e hadrpkg Managing packagesRunning packages Maintaining packages# cmhaltpkg packagename Halting packagesHost key verification failed. Lost connection Limitations Information to collect before contacting HP How to contact HPRelated information Typographic conventions Warranty informationHP authorized resellers Documentation feedbackTIP Node2# /usr/bin/ssh-keygen -t rsa Db2 get db cfg for db2 database name grep -i hardNode3# /usr/bin/ssh-keygen -t rsa Node3# /usr/bin/ssh-keygen -t dsaPage To add a new key to/home/user/.ssh/knownhosts Page Glossary Index