HP Serviceguard Toolkits for Database Replication Solutions manual Startstandbyasprimary to yes

Page 33

•When using the ODG Broker toolkit in Continentalclusters environment, the “Fast Start Failover” feature of ODG Broker must be disabled. In case of a disaster at the primary site, the “Fast start failover” feature of ODG Broker enables automatic failover of the primary database to an available standby database. This may lead to Data Integrity issues when the toolkit attempts to failover the primary to a different standby. Hence, HP recommends that you disable “Fast Start Failover” in Continentalclusters environment where role transitions are supported.

•If the CRS package goes into maintenance mode, SGeRAC DB stops monitoring the database. You must manually put the Data Guard toolkit into the maintenance mode because it does not go into this mode automatically.

•Always set the attribute START_MODE in ECMT Oracle/SGeRAC toolkit to [mount] when you use it with ODG toolkit.

•It does not perform role transitions. if required, the role transitions must be manually performed. When the Primary cluster goes down, the toolkit supports automatic role transitions only in Continentalclusters environment (Both Single Instance and RAC environments).

•For a recovery package of Continentalclusters environment, set the attribute

START_STANDBY_AS_PRIMARY to [yes].

•The toolkit displays a warning message during package validation (in package apply cmapplyconf -pand package check cmacheckconf -p) when the parameter START_STANDBY_AS_PRIMARY is set to yes. The message suggests that the parameter must be used only in the recovery package of the Continentalclusters environment. Therefore, the toolkit alerts you to change its value to [no] if it is not a recovery package.

•To enable Active Data Guard, the user needs an optional license from Oracle. Therefore, this toolkit parameter must not be set to [yes] without the license.

•ODG Broker is not supported in single instance SG environment.

•If the attribute MONITOR_DG_BROKER is set to [yes], the toolkit does not monitor the mrp (lsp) process on the physical standby database (logical standby database).

•Broker configuration should not be enabled when the parameter MONITOR_DG_BROKER is set to [no]. If enabled, the toolkit fails the package startup to avoid issues.

Limitations 33

Page 32 Page 34
Image 33
Page 32 Page 34
Contents HP Part Number Published August Edition Page Contents Glossary Index Introduction Advantages OverviewSupported configuration DependenciesSingle-instance Oracle database 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 GuardInstalling and uninstalling Oracle Data Guard toolkit Setting up Oracle Data Guard toolkit# swinstall -s depot path High availability for data guard broker# 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 toolkitTroubleshooting Pkg.conf commandLimitations 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 clustersTo provide high availability only to primary database Creating packagesGo to the /etc/cmcluster/hadrprimary directory Cmmakepkg -m ecmt/db2/db2 -m tkit/db2hadr/db2hadr pkg.confInstancename Hadrip Running packages Managing packagesMaintaining packages And, $ cmmodpkg -e hadrpkg# cmhaltpkg packagename Halting packagesHost key verification failed. Lost connection Limitations Information to collect before contacting HP How to contact HPHP authorized resellers Warranty informationDocumentation feedback Related information Typographic conventionsTIP Node3# /usr/bin/ssh-keygen -t rsa Db2 get db cfg for db2 database name grep -i hardNode3# /usr/bin/ssh-keygen -t dsa Node2# /usr/bin/ssh-keygen -t rsaPage To add a new key to/home/user/.ssh/knownhosts Page Glossary Index
Top Page Image Contents