B
Configuration Files

This appendix contains information on the following configuration files:

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 sample ORACLE_SERVICE_config.pfs file created by the PFSSETUP utility:

Note:

In the following example, the settings for the db_name, db_domain, and service_names parameters, 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 2 (9.2.0.1.0).
DB_NAME	Required	SALES, for example	The name specified must correspond with the name specified in the PFSSETUP utility file (`$ORACLE_SERVICE.conf`).
DB_DOMAIN	Required	WORLD, for example	The database domain specified must correspond with 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 with the service name specified in the Oracle9i Real Application Clusters installation configuration file (`$ORACLE_SERVICE.conf`). You can provide multiple service names (using 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 are authenticated using OPS$.
DB_BLOCK_CHECKING	Recommended	TRUE	Controls whether Oracle performs block checking for data blocks.
DB_BLOCK_CHECKSUM	Recommended	TRUE	Determines whether the DBWn processes and the direct loader 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 required 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.

ORACLE_SERVICE_config_HOSTNAME[A|B].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 Oracle9i 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 a Oracle Net local listener. 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 the Oracle9i Real Application Clusters Guard installation configuration parameter IS_MTS is set to 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 a listener address list through a tnsnames.ora file.

B Configuration Files