3.5.1 MxDB-Oracle-HiAv Installation and Administration Guide

Chapter 2: Operations 10

Service Loss

MxDB-Oracle-HiAv considers a Virtual Oracle Service to be in a down

state if the probe returns a failure, or if the probe times out. If a database

cannot satisfy the very rudimentary checks performed by the default

MxDB-Oracle-HiAv probe script (mxdb_probe.sql), there is likely

something very wrong with the instance. The default action taken by

MxDB-Oracle-HiAv is to reboot the instance. If this action is not

acceptable for your application, there are two options: tune the probe

timeout or change the probe actions. Both of these topics are covered later

in this document.

Management Applications

MxDB-Oracle-HiAv provides the following management applications:

MxDB-Oracle-HiAv Graphical User Interface. The GUI supports both

configuration and operations.

MxDB-Oracle Command Line Interface. The CLI supports operations

but cannot be used to configure Virtual Oracle Services.

MxDB-Oracle-HiAv GUI

The GUI is the central administration point for MxDB-Oracle-HiAv and

can be used for both configuration and operations.

Configuration

The GUI supports the following configuration actions:

• Creating a Virtual Oracle Service for an existing production database.

• Creating the demonstration database and the associated Virtual

Oracle Service.

During configuration, the GUI does the following:

• Configures Oracle Net Services file entries such as listener.ora and

tnsnames.ora if desired. This feature is provided as a convenience. The

use of Oracle Net Services tools such as netca and netmgr is also

supported.