B
Configuration Files

This appendix contains information on the following configuration files:

Oracle9i Real Application Clusters Guard Pack Configuration Template File

This section shows the Oracle9i Real Application Clusters Guard Pack configuration template file. Entries that you need to edit are shown in bold font.

# ident "@(#)savsetup.dat       3.3     01/03/08"
#
#######################################################################
#                                                                     # 
# Oracle Real Application Clusters Guard Release 9.0.1.0.0 Production #
#                                                                     #
# Copyright (c) 2000, 2001, Oracle Corporation.  All rights reserved. #
#                                                                     #
#######################################################################
#
# Filename
# savsetup.dat
# Description:
#       This file is Real Application Clusters Guard Installation 
#       Configuration File
#
# HISTORY:
# Date              Remarks                          Author
#                   created
# 03/07/2001        Fixed 1676001                    kzhu
# 03/28/2001        Fixed 1691999 (SSH support)      pbhat
#
# Oracle Real Application Clusters Guard
# Installation Configuration File
#
# For complete details about Oracle Real Application Clusters Guard 
# parameters and how to set them, consult the Oracle Real Application 
# Clusters Guard documentation. 
#
#######################################################################

# NOTE: This file MUST be edited before Oracle Real Application Clusters Guard
# can be GENERATED and DEPLOYED. Uncomment the parameters as you set
# them. There cannot be any spaces around the equal signs "=".
#

# ======================================================================
# When you modify parameters in this section, you must:
#   1) Generate "All the files"
#   2) Deploy "All the files"
#   3) Delete the existing Real Application Clusters Guard packs by running 
#      deletepacks 
#   4) Recreate the Real Application Clusters Guard packs by running 
#      createpacks
# ======================================================================

# PLATFORM
# --------
# Range of values: SUN, HP
# Default setting: NONE
#
# Specify the hardware cluster platform.
#
# Example:
#       PLATFORM=SUN
#
PLATFORM=

# PFS_CLUSTER_NAME
# ----------------
# Enter the cluster name. This name should be unique among all the
# clusters which run on the same network.
#
PFS_CLUSTER_NAME=


# PFS_HOSTA and PFS_HOSTB
# -----------------------
# Range of values: Any valid hostnames (as returned by hostname command) that
#                  is part of the cluster where Oracle Real Application 
#                  Clusters Guard resides.
# Default setting: NONE
#
PFS_HOSTA=
PFS_HOSTB=

# ORACLE_BASE
# -----------
# Range of values: Any valid directory
# Default setting: NONE
#
# Specify the directory at the top of the Oracle software and
# administrative file structure. The OFA-recommended value is
#       software_mount_point/app/oracle
#
# Example:
#       ORACLE_BASE=/u01/app/oracle
#
# The ORACLE_BASE must be identical for all nodes of a cluster
# accessing the database. If OFA is not being used, comment out
# this parameter.
#
ORACLE_BASE=

# ORACLE_HOME
# -----------
# Range of values: Any valid directory
# Default setting: NONE
#
# Specify the directory containing the Oracle software for a given 
# Oracle Server release. The OFA-recommended value is
#       ${ORACLE_BASE}/product/release
#
# Example:
#       ORACLE_HOME=/u01/app/oracle/product/9i
#
# The ORACLE_HOME must be identical for all nodes of a cluster accessing
# the database.
#
ORACLE_HOME=

# DB_NAME
# -------
# Range of values: Valid database name
# Default setting: NONE
#
# Specify the value of the initialization parameter DB_NAME entered
# during installation or database creation.
#
# Example:
#       DB_NAME=PRO
#
# Multiple instances MUST have the same value for DB_NAME.
#
DB_NAME=

# PFS_IP_PACK_HOSTA and PFS_IP_PACK_HOSTB
# ---------------------------------------
# Specify the IP addresses that you want added to a LAN interface
# card, which will be moved with the pack in the event that the
# pack is moved to another node. 
#
PFS_IP_PACK_HOSTA=
PFS_IP_PACK_HOSTB=

# PFS_IP_SUBNET_HOSTA and PFS_IP_SUBNET_HOSTB
# --------------------------------------------
#
# Specify the subnet for the IP addresses that you want added to a
# LAN interface card, which will be moved with the pack in the event
# that the pack is moved to another node.
#
PFS_IP_SUBNET_HOSTA=
PFS_IP_SUBNET_HOSTB=

# ======================================================================
# When you modify parameters in this section, you must:
#   1) Generate "User definitions file"
#   2) Deploy "User definitions file"
#   3) Delete the existing Real Application Clusters Guard packs by 
#      running deletepacks
#   4) Recreate the Real Application Clusters Guard packs by running 
#      createpacks
# ======================================================================

# SUN Specific
# ============

# PFS_NET_IF_A and PFS_NET_IF_B
# -----------------------------
# Specify the network controller interfaces.
# The hme0 interfaces will be used typically for the primary public network.
# The can vary depending on your public network configuration.
#
PFS_NET_IF_A=
PFS_NET_IF_B=

# START_NET_TIMEMOUT and STOP_NET_TIMEOUT
# ---------------------------------------
# Range of values:
# Default setting: 180
#
START_NET_TIMEOUT=180
STOP_NET_TIMEOUT=180

# HP Specific
# ===========

# PFS_VG_HOSTA and PFS_VG_HOSTB
# -----------------------------
#
# Enter the disk/volume groups used by the Real Application Clusters Guard
# database. The value must be enclosed within double quotes.
#
# Example:
#       PFS_VG_HOSTA="emc1 emc2 emc3"
#       PFS_VG_HOSTB="emc1 emc2 emc3"
#
PFS_VG_HOSTA=""
PFS_VG_HOSTB=""

# ======================================================================
# When you modify parameters in this section, you must:
#   1) Generate "All the files"
#   2) Deploy "All the files" 
#   3) Recreate the Real Application Clusters Guard schema by running 
#      catpfs.sql
# ======================================================================

# ORACLE_SERVICE
# --------------
#
# The name of the service has to be unique in the cluster.
# Oracle Corporation recommends restricting it to no more than 4 
# characters, to avoid filename problems on heterogeneous systems.
#
ORACLE_SERVICE=

# ORACLE_USER
# -----------
# Range of values: Any valid operating system user that is part of the
#                  OS DBA group.
#
# Specify the name of the operating system oracle user. This is the user
# that owns the Oracle Real Application Clusters Guard software.
#
ORACLE_USER=

# ORACLE_SID_HOSTA and ORACLE_SID_HOSTB
# --------------------------------------
# Range of values: Any valid ORACLE_SID string
# Default setting: NONE
#
# Specify the Oracle system identifier, or SID, which is the same of the
# Oracle Server instance. Because the SID is incorporated into may 
# filenames, Oracle Corporation recommends restricting it to no more than 
# 4 characters, to avoid filename problems on heterogeneous systems.
#
# The SID for each instance in a Real Application Clusters database should be 
# unique and should incorporate the name of the database it manipuluates.
#
# For example, the SID for the database PRO might be
#       ORACLE_SID_HOSTA=PRO1
#       ORACLE_SID_HOSTB=PRO2
#
ORACLE_SID_HOSTA=
ORACLE_SID_HOSTB=


# INSTANCE_NAME_HOSTA and INSTANCE_NAME_HOSTB
# -------------------------------------------
# Range of values:
# Default setting: NONE
#
# Specify the name of the instance and is used to uniquely identify a 
# specific instance when multiple instances share common service names.
# The instance name can be the same as the SID. It is indicated by the
# INSTANCE_NAME parameter in the initsid.ora file.
# The INSTANCE_NAME for each instance in a Real Application Clusters database
# must be unique.
#
# Example:
#       INSTANCE_NAME_HOSTA=PRO1
#       INSTANCE_NAME_HOSTB=PRO2
#
INSTANCE_NAME_HOSTA=
INSTANCE_NAME_HOSTB=

# SERVICE_NAMES
# -------------
# Range of values: Any ASCII string
# Default setting: DB_NAME.DB_DOMAIN
#
# Specify the name of the database service on the network, pro.oracle.com.
# By default, Oracle Universal Installer and Oracle Database Configuration
# Assistant creates a service name that includes the entire global database
# name, a name comprised of the database name (DB_NAME) and domain name
# (DB_DOMAIN), entered during installation or database creation.
#
# It is possible to provide multiple service names (by individual
# SERVICE_NAMES entries) so that different usages of an instance can be
# identified separately. 
#
# For example, the SERVICE_NAMES for a database name of PRO and database
# domain of oracle.com may be:
#       SERVICE_NAMES=PRO.oracle.com
# 
#
SERVICE_NAMES=${DB_NAME}.${DB_DOMAIN}

# IS_MTS
# ------
# Range of values: $PFS_TRUE (1), $PFS_FALSE (0)
# Default setting: $PFS_FALSE
#
# Specify IS_MTS=${PFS_TRUE} if running Oracle Shared Server.
#
IS_MTS=${PFS_FALSE}                

# TNS_ADMIN
# ---------
# Range of values: Any valid directory
# Default: ${ORACLE_HOME}/network/admin   
#
# Specify the directory containing the Oracle Net configuration files.
#
# The TNS_ADMIN must be identical for all nodes of a cluster accessing
# the database.
#
TNS_ADMIN=${ORACLE_HOME}/network/admin

# ======================================================================
# When you modify parameters in this section, you must:
#   1) Generate "User definitions file"
#   2) Deploy "User definitions file"
# ======================================================================

# PFILE_HOSTA and PFILE_HOSTB
# ---------------------------
# Range of values: Any valid init.ora file referencing control files. 
# Default setting: 
# For OFA Configuration:
# PFILE_HOSTA=${ORACLE_BASE}/admin/${DB_NAME}/pfile/init${ORACLE_SID_HOSTA}.ora
# PFILE_HOSTB=${ORACLE_BASE}/admin/${DB_NAME}/pfile/init${ORACLE_SID_HOSTB}.ora
#
# For non OFA Configuration:
# PFILE_HOSTA=${ORACLE_HOME}/dbs/init${ORACLE_SID_HOSTA}.ora
# PFILE_HOSTB=${ORACLE_HOME}/dbs/init${ORACLE_SID_HOSTB}.ora
#
# PFILE_HOSTA and PFILE_HOSTB is used when Oracle Real Application Clusters 
# Guard starts up the instance.
#
PFILE_HOSTA=
PFILE_HOSTB=

# PFS_PREFERRED_PRIMARY
# PFS_PREFERRED_SECONDARY
# -----------------------
# Range of values: $PFS_HOSTA, $PFS_HOSTB
# Default setting: PFS_PREFERRED_PRIMARY=$PFS_HOSTA and 
#                  PFS_PREFERRED_SECONDARY=$PFS_HOSTB
# 
# Specify the default preferred primary and secondary nodes of the cluster.
#
PFS_PREFERRED_PRIMARY=${PFS_HOSTA}          
PFS_PREFERRED_SECONDARY=${PFS_HOSTB}     


# PFS_LANGUAGE
# PFS_TERRITORY
# CHARSET
# ----------------
# PFS_LANGUAGE
# Range of values: Any valid language name
# Default setting: AMERICAN
#
# PFS_TERRITORY
# Range of values: Any valid territory name
# Default setting: AMERICA
#
# CHARSET
# Range of values: Any valid character set 
# Default setting: US7ASCII
#
# NLS_LANG environment variable has three components -- language, territory, 
# and charset -- in the form: NLS_LANG=language_territory.charset
#
# PFS_LANGUAGE specifies conventions such as the language used for Oracle 
# messages, day names, and month names. Each supported language has a 
# unique name -- for example, American, Japanese.
#
# PFS_TERRITORY specifies conventions such as the default calendar, collation, 
# date, monetory, and numeric formats. Each supported territory has a 
# unique  name -- for example: America, Japan
#
# Charset specifies the character set used by the client application. Each
# supported character set has a unique acronym. For example, US7ASCII, UTF8.
#
PFS_LANGUAGE=AMERICAN      
PFS_TERRITORY=AMERICA   
CHARSET=US7ASCII     

# PFS_KEEP_PRIMARY
# ----------------
# Range of values: $PFS_TRUE (1), $PFS_FALSE (0)
# Default setting: $PFS_TRUE
#
# Specify whether to leave the primary Real Application Clusters Guard pack 
# up and running even when the secondary pack does not come up during PFSBOOT.
#
PFS_KEEP_PRIMARY=${PFS_TRUE} 

# PFS_DEBUGGING
# -------------
# Range of values: $PFS_TRUE (1), $PFS_FALSE (0)
# Default setting: $PFS_FALSE
#
# The value of PFS_DEBUGGING disables or enables Oracle Real Application 
# Clusters Guard debugging facility.
#
PFS_DEBUGGING=${PFS_FALSE}

# LISTENER_CHECK_INTERNVAL
# ------------------------
# Range of values: 0 -  (seconds)
# Default setting: 5
#
# Specify the frequency at which we poll the public listener to
# verify its health.
#
LISTENER_CHECK_INTERVAL=5

# PRIV_LSNR_CHECK_INTERVAL
# ------------------------
# Range of values: 0- (seconds)
# Default setting: 60
#
# Specify the frequency at which we poll the private listener to
# verify its health.
#
PRIV_LISTENER_CHECK_INTERVAL=60

# MAX_LSNR_RESTART
# ---------------
# Range of values: 0- 
# Default setting: 3
#
# Range of Specifies the maximum number of times the listener can be restarted.
#
MAX_LSNR_RESTART=3   

# MIN_LSNR_RESTART_INTERVAL
# ------------------------
# Range of values: 0- (seconds)
# Default setting: 300 
# 
# If Oracle Real Application Clusters Guard attempts to restart the listener 
# more than MAX_LSNR_RESTART times within MIN_LSNR_RESTART_INTERVAL seconds,
# then Oracle Real Application Clusters Guard exits the listener monitor.
#
MIN_LSNR_RESTART_INTERVAL=300

# DUMPLSNR_TIMEOUT
# ----------------
# Range of values: 0- (seconds)
# Default setting: 60
#
# Specify how long to wait for NETSTAT -rn command to complete.
#
DUMPLSNR_TIMEOUT=60  

# ORACLE_ARCH_TIMEOUT
# -------------------
# Range of values: 0- (seconds)
# Default setting: 60
#
# Specify how long to wait for ALTER DATABASE ARCHIVE LOG ALL command
# to complete.
#
ORACLE_ARCH_TIMEOUT=60   

# ORACLE_CKPT_TIMEOUT
# -------------------
# Range of values: 0- (seconds)
# Default setting: 60
#
# Specify how long to wait for ALTER SYSTEM CHECKPOINT GLOBAL command
# to complete.
#
ORACLE_CKPT_TIMEOUT=60 

# PFS_DUMP_LEVEL
# --------------
# Range of values: 0-10
# Default setting: 10
#
# Specify the dump level associated with Oracle system state dumps.
#
PFS_DUMP_LEVEL=10

# ORACLE_DUMP_TIMEOUT
# --------------------
# Range of values: 0- (seconds)
# Default setting: 60
#
# Specify how long to wait for Oracle SYSTEMSTATE and Real Application Clusters
# Lock Tree Dump to complete.
#
ORACLE_DUMP_TIMEOUT=60  

# ======================================================================
# When you modify parameters in this section, you must:
#   1) Generate "User definitions file"
#   2) Generate "Oracle network files"
#   3) Deploy "User definitions file"
#   4) Deploy "Oracle network files"
# ======================================================================

# PFS_IP_HOSTA and PFS_IP_HOSTB
# ------------------------------
#
# Specify the static IP address
#
PFS_IP_HOSTA=
PFS_IP_HOSTB=

# PFS_PORT_DED_HOSTA and PFS_PORT_DED_HOSTB
# PFS_PORT_MTS_HOSTA and PFS_PORT_MTS_HOSTB
# -----------------------------------------
# Range of values: 1025-65535
# Default setting:
#
# Specify the port numbers for the Real Application Clusters Guard public
# and private listeners.
#
# Port numbers below 1024 are reserved for use by privileged
# processes on many operating systems.
#
PFS_PORT_DED_HOSTA=
PFS_PORT_DED_HOSTB=

PFS_PORT_MTS_HOSTA=
PFS_PORT_MTS_HOSTB=

# ======================================================================
# When you modify parameters in this section, you must:
#   1) Generate "Oracle instance files"
#   2) Deploy "Oracle instance files"
# ======================================================================

# DB_DOMAIN
# ---------
# Range of values: Any legal string of name componets, separated by periods
#                  and up to 128 characters long. This value cannot be null.
# Default setting: WORLD
#
# Specify the database domain in which the database is located, entered 
# during installation or database creation. When possible, Oracle 
# Corporation recommends that your database domain mirror the network 
# domain.
# 
# Example:
#       DB_DOMAIN=oracle.com
# 
# Multiple instances MUST have the same value for DB_DOMAIN.
#
DB_DOMAIN=WORLD


# INSTANCE_NUMBER_HOSTA and INSTANCE_NUMBER_HOSTB
# -----------------------------------------------
# Range of values:
# Default setting:
#
# Specifies a unique number that maps the instance to one free list group 
# for each database object created with the storage parameter 
# FREELIST_GROUPS. Oracle Corporation recommends setting the 
# INSTANCE_NUMBER to the same value as the THREAD parameter.
#
# Example:
#       INSTANCE_NUMBER_HOSTA=THREAD_HOSTA=1
#       INSTANCE_NUMBER_HOSTB=THREAD_HOSTB=2
#
INSTANCE_NUMBER_HOSTA=
INSTANCE_NUMBER_HOSTB=

# THREAD_HOSTA and THREAD_HOSTB
# -----------------------------
# Range of values: 0 to maximum number of enabled threads
# Default setting:
#
# Specify the number of the redo thread that is to be used by the instance.
# Any available redo thread number can be used, but an instance cannot use 
# the same thread number as another instnace. Also, an instance cannot 
# start when its redo thread is disabled. A value of zero causes an 
# available, enabled public thread to be chosen. An instance cannot mount a 
# database if the thread is used  by another instance or if the thread is 
# disabled.
#
# Example:
#       THREAD_HOSTA=1
#       THREAD_HOSTB=2
#
# Multiple instances MUST have different value for THREAD_HOSTA and 
# THREAD_HOSTB.
#
THREAD_HOSTA=
THREAD_HOSTB=


# SSH Support
# SSH_ENABLE, SSH_PROGRAM, SCP_PROGRAM, SSH_ENV_FILE
# --------------------------------------------------
# SSH_ENABLE
# Range of values: PFS_TRUE, PFS_FALSE
# Default setting: PFS_FALSE
#
# SSH_PROGRAM, SCP_PROGRAM
# Range of values: Empty, or full path to ssh/scp executable
# Default setting: Empty
#
# SSH_ENV_FILE
# Range of values: Empty, or full path to SSH environment file
# Default setting: Empty
#
# Real Application Clusters Guard can be configured to use ssh and scp 
# instead of the standard utilities remsh and rcp, respectively, provided 
# SSH is already installed and configured on both HOST1 and HOST2.  
# SSH must be configured such that neither a password nor a passphrase 
# is requested when connecting to the remote system using ssh or scp.
#
# If SSH_ENABLE=PFS_FALSE, Oracle Real Application Clusters Guard will use the 
# standard remote utilities remsh and rcp provided with the operating system.
#
# If SSH_ENABLE=PFS_TRUE, Oracle Real Application Clusters Guard will instead 
# use the SSH remote utilities ssh and scp as defined by SSH_PROGRAM 
# and SCP_PROGRAM.
#
# Depending on the SSH authentication method in use, SSH_ENV_FILE may
# need to be set.  If host-based authentication or RSA authentication with a
# plaintext key is being used, SSH_ENV_FILE should be unset.  In both
# these scenarios, ssh and scp commands from HOST1 to HOST2 and vice-versa 
# work without a password or passphrase prompt.  In addition, the environment
# variable SSH_AUTH_SOCK is not required for prompt-less access between the
# systems.  If, however, RSA authentication using an encrypted key is being 
# used, the only method of prompt-less remote access is using ssh-agent, 
# which requires the proper setting of the environment variable SSH_AUTH_SOCK.
# In order for Real Application Clusters Guard to use SSH with RSA 
# authentication using an encrypted key, the SSH_ENV_FILE parameters must 
# be set to the respective Oracle Read Application Clusters Guard SSH
# environment file on each HOST.  Within the user-created Oracle Real 
# Application Clusters Guard SSH environment file, SSH_AUTH_SOCK must be set to 
# a valid ssh-agent socket file.  The proper setting of SSH_AUTH_SOCK is given 
# as output when starting ssh-agent.
#
# Example if using SSH with host-based authentication or RSA authentication
# with a plaintext key:
#   SSH_ENABLE=$PFS_TRUE
#   SSH_PROGRAM=/usr/local/bin/ssh
#   SCP_PROGRAM=/usr/local/bin/scp
#   SSH_ENV_FILE=
#
# Example if using SSH with RSA authentication using an encrypted key:
#   SSH_ENABLE=$PFS_TRUE
#   SSH_PROGRAM=/usr/local/bin/ssh
#   SCP_PROGRAM=/usr/local/bin/scp
#   SSH_ENV_FILE=/home/oracle/.ssh/pfs_ssh_env
#
# Example contents of the Oracle Real Applications Clusters Guard SSH 
# environment files on both HOSTs
#   host1> cat /home/oracle/.ssh/pfs_ssh_env
#   SSH_AUTH_SOCK=/tmp/ssh-oracle/ssh-11007-agent
#
#   host2> cat /home/oracle/.ssh/pfs_ssh_env
#   SSH_AUTH_SOCK=/tmp/ssh-oracle/ssh-17893-agent
#
# IMPORTANT NOTE : 
#     Before changing the parameters for SSH please check the Oracle 
#     Real Application Clusters Guard README file located in
#     $ORACLE_HOME/pfs/doc for more information on SSH support.
#
SSH_ENABLE=${PFS_FALSE}
SSH_PROGRAM=
SCP_PROGRAM=
SSH_ENV_FILE=

init_ORACLE_SERVICE_HOSTNAME[A|B].ora

The init_ORACLE_SERVICE_PFS_HOST[A|B].ora file defines the following parameters for each instance:

Parameter	Definition
INSTANCE_NUMBER	Unique instance number. Maps the instance to one free list group for each database object created with the storage parameter FREELIST GROUPS. Oracle Corporation recommends setting the INSTANCE_NUMBER to the same value as the THREAD parameter.
THREAD	Unique thread number. Specifies the number of the redo thread used by the instance. You can specify any available redo thread number, but an instance cannot use the same thread number as another instance. Also, an instance cannot start when its redo thread is disabled. A value of zero causes an available, enabled public thread to be chosen. An instance cannot mount a database if the thread is used by another instance or if the thread is disabled.
INSTANCE_NAME	Unique instance name. Identifies the name of the instance and is used to uniquely identify a specific instance when multiple instances share common service names.

Example B-1 and Example B-2 show samples of the init_ORACLE_SERVICE_HOSTNAME[A|B].ora file that the PFSSETUP utility creates:

Example B-1 init_SALES_nodeA.ora

instance_number=1
thread=1
instance_name=SALES1

Example B-2 init_SALES_nodeB.ora

instance_number=2
thread=2
instance_name=SALES2

ORACLE_SERVICE_config.pfs

The ORACLE_SERVICE_config.pfs file contains the mandatory and recommended settings for selected initialization parameters for Oracle9i Real Application Clusters Guard. All instances must use the same ORACLE_SERVICE_config.pfs file.

Example B-3 shows a ORACLE_SERVICE_config.pfs file created by the PFSSETUP utility:

Note:

In the following example, db_name, db_domain, and service_names, are sample values and can vary, depending on your system and requirements.

Example B-3 SALES_config.pfs

active_instance_count=1
compatible=9.0.0
db_block_checking=true
db_block_checksum=true
db_name=<SALES>
db_domain=<WORLD>
service_names=<SALES.WORLD>
max_dump_file_size=unlimited
os_authent_prefix=OPS$
cluster_database=true
remote_os_authent=true
timed_statistics=true

The following table describes the parameters in the preceeding example:

Parameter	Requirement	Value	Description
ACTIVE_INSTANCE_COUNT	Required	1	A value of 1 designates one instance in a two-instance cluster as the primary instance and the other instance as the secondary instance.
COMPATIBLE	Required	9.0.0	The Oracle server must maintain compatibility with Oracle server Release 9.0.0.
DB_NAME	Required	SALES, for example	The name specified must correspond to the name specified in the PFSSETUP utility file (`$ORACLE_SERVICE.conf`).
DB_DOMAIN	Required	WORLD, for example	The database domain specified must correspond to the database domain specified in the PFSSETUP utility file (`$ORACLE_SERVICE.conf`).
CLUSTER_DATABASE	Required	TRUE	A value of TRUE enables Oracle9i Real Application Clusters Guard.
SERVICE_NAMES	Required	SALES.WORLD	The service name specified must correspond to the service name specified in the Oracle9i Real Application Clusters installation configuration file (`$ORACLE_SERVICE.conf`). It is possible to provide multiple services names (by individual SERVICE_NAMES entries) so that different usage of an instance can be identified separately. Oracle9i Real Application Clusters Guard supports only one service_names entry.
OS_AUTHENT_PREFIX	Required	OPS$	"OPS$" is the prefix that Oracle uses to authenticate users attempting to connect to the server.
REMOTE_OS_AUTHENT	Required	TRUE	Remote clients will be authenticated with "OPS$".
DB_BLOCK_CHECKING	Recommended	TRUE	Controls whether Oracle performs block checking for data blocks.
DB_BLOCK_CHECKSUM	Recommended	TRUE	Determines whether DBWn and the direct loader will calculate a checksum and store it in the cache header of every data block when writing it to disk.
FAST_START_MTTR_TARGET	Recommended	System-specific, application specific	Specifies the time in seconds that should be needed during crash or instance recovery.
MAX_DUMP_FILE_SIZE	Recommended	UNLIMITED	Specifies the maximum size of trace files.
TIMED_STATISTICS	Recommended	TRUE	Specifies whether statistics related to time are collected or not.

ORACLE_SERVICE_config_HOSTNAME.ded.pfs

The ORACLE_SERVICE_config_HOSTNAME[A|B].ded.pfs files contain the dedicated network initialization parameters for Oracle9i Real Application Clusters Guard. These files are generated when the Oracle Real Application Clusters Guard configuration parameter IS_MTS is set to false, which is the default setting.

Example B-4 and Example B-5 show samples of the ORACLE_SERVICE_config_HOSTNAME[A|B].ded.pfs fileS that the PFSSETUP utility creates:

Example B-4 SALES_config_nodea.ded.pfs

local_listener=listener_SALES_nodeA

Example B-5 SALES_config_nodeb.ded.pfs

local_listener=listener_SALES_nodeB

The local_listener parameter is required. It specifies a network name that resolves to an address of Oracle Net local listeners. The address is specified in the tnsnames.ora file.

ORACLE_SERVICE_config_HOSTNAME[A|B].mts.pfs

The ORACLE_SERVICE_config_HOSTNAME[A|B].mts.pfs files contain the Shared Servers network initialization parameters for Oracle9i Real Application Clusters Guard. These files are generated when Oracle9i Real Application Clusters Guard installation configuration parameter IS_MTS is set true.

Example B-6 and Example B-7 show samples of the ORACLE_SERVICE_config_HOSTNAME[A|B].mts.pfs file that the PFSSETUP utility creates:

Example B-6 sales_config_nodea.mts.pfs

dispatchers="(address=(protocol=tcp)(host=192.10.1.21)(lis=listener_sales)"

Example B-7 sales_config_nodeb.mts.pfs

dispatchers="(address=(protocol=tcp)(host=192.10.1.22)(lis=listener_sales)"

The lis=listener_sales setting enables an instance to register its instance information with remote listeners on the other nodes. The listener_sales value is resolved to listener address lists through a tnsnames.ora file.

B Configuration Files