3.5.1 MxDB-Oracle-HiAv Installation and Administration Guide

Chapter 2: Operations 12

Naming Conventions

The associations among the Virtual Oracle Server, service monitor,

Database Instance, and Database Name can become confusing if certain

conventions are not followed. It is generally best practice to use the

following naming scheme:

• The names of the database and the

ORACLE_SID should be the same,

including case sensitivity.

• The names of the service monitor and the database should be the

same. To accomplish this, enter the database name in the “Database

Name” block when you configure the database via the

MxDB-Oracle-HiAv GUI.

• Because the Virtual Oracle Service name must be entered in DNS,

selecting the name is typically not entirely under DBA control. The

Database Administrator may need to negotiate with the System or

Network Administrator to agree on a name that makes sense for the

site.

In general, we recommend that the Virtual Oracle Service name

consist of the database name followed by the domain suffix. For

example, if the database instance, database name, and service monitor

are all called PROD and the domain suffix is mycompany.com, the

Virtual Oracle Service name would be PROD.mycompany.com.

Configuration File

MxDB-Oracle-HiAv supports an optional configuration file that uses the

naming convention mxdbha_<

DBNAME>.conf where <DBNAME> is the

name of the Service Monitor under the Virtual Oracle Service. If the file is

used, it must be placed in

$ORACLE_HOME/dbs. For example:

$ cd $ORACLE_HOME/dbs

$ ls -l *PROD*conf

-rw-r--r-- 1 root root 75 Feb 8 17:12 mxdbha_PROD.conf

The convention for assigning values to parameters in the

mxdbha_<DBNAME>.conf file is as follows:

Parameter <white space> value