3.5.1 MxDB-Oracle-HiAv Installation and Administration Guide

Chapter 2: Operations 48

After implementing these steps, the Intelligent Agent will be started each

time the

PILOT database is started.

The sample script can be renamed to support starting the Intelligent

Agent for any database under MxDB-Oracle-HiAv control.

Add Code to the Supplemental Script

It is completely up to the administrator to determine any other

supplemental startup code that should be implemented in the script.

Provided the code can execute with the above listed caveats, the script

will perform satisfactorily.

Data Guard Support

Without either Real Application Clusters or a product such as

MxDB-Oracle-HiAv, a server outage on a Data Guard Primary database

will cause a switchover to the Data Guard Standby. In order to handle

server outages without triggering the disaster recovery action associated

with a Data Guard switchover, MxDB-Oracle-HiAv can be used. In

practicality, it is most advantageous to have at least the Data Guard

Primary covered with some aspect of high availability to prevent

unnecessary Data Guard switchovers. In some cases it may be desirable

to provide high availability services to a Data Guard Standby as well. The

product supports both so the decision can be made on a site-by-site basis.

Configure MxDB-Oracle-HiAv for a Data Guard

Standby Database

The default start/stop and probe scripts included in the product are

functional with a Data Guard Primary without change. However, Data

Guard Standby databases require different start/stop and probe actions.

To that end, the product ships with a set of scripts that can be used for a

Data Guard Standby.

As is the case with custom start/stop and probe scripts, Data Guard

Standby databases require you to deploy copies of the supplied Data

Guard scripts under the ${

ORACLE_BASE}/admin/<DBNAME>/scripts

directory.