Oracle9i Real Application Clusters Real Applications Clusters Guard I Configuration Guide Release 2 (9.2.0.1.0) for UNIX Systems: AIX-Based Systems, Compaq Tru64 UNIX, HP 9000 Series HP-UX, and Sun Solaris Part Number A95979-02 |
|
This chapter describes how to install and configure Oracle9i Real Application Clusters Guard. It contains the following sections:
The following sections describe how to complete a new Oracle9i Real Application Clusters Guard installation:
Oracle9i Real Application Clusters Guard is included with the Oracle9i Real Application Clusters software. Oracle Universal Installer automatically installs Oracle9i Real Application Clusters Guard when you choose to install Oracle9i Real Application Clusters software. For complete instructions on how to install Oracle9i Real Application Clusters, refer to the Oracle9i Real Application Clusters Installation and Configuration Guide.
See Appendix A for more information about Oracle9i Real Application Clusters Guard files and directories.
The following table describes the contents of the most important directories:
The information in the Oracle9i Real Application Clusters Guard configuration file corresponds to a single Oracle9i Real Application Clusters database. If you intend to use Oracle9i Real Application Clusters Guard with multiple databases, you must create a separate configuration file for each database. The parameters in the Oracle9i Real Application Clusters Guard configuration file are used to create the Oracle9i Real Application Clusters Guard Packs and environment.
The $ORACLE_HOME/pfs/setup/conf/savsetup.dat
file contains a template for the Oracle9i Real Application Clusters Guard configuration file.
To create a separate configuration file:
$ORACLE_HOME/pfs/setup/conf
directory:
$ cd $ORACLE_HOME/pfs/setup/conf
savsetup.dat
file to SALES.conf
, where SALES is the value of the $ORACLE_SERVICE variable. For example:
$ cp savsetup.dat SALES.conf
You can use the default values in the configuration file if those values are acceptable.
The Oracle9i Real Application Clusters configuration file is divided into six sections. Each section has been categorized based on the Oracle9i Real Application Clusters Guard parameters contained in that section. If you need to modify an Oracle9i Real Application Clusters Guard parameter, modify it using the Oracle9i Real Application Clusters Guard Setup utility (PFSSETUP). Depending on the parameter, different files and areas of the Oracle9i Real Application Clusters Guard environment are affected. Each section heading in the configuration file identifies the requirements for changing the parameters in that section. For example, changing the ORACLE_SERVICE parameter affects all of the Oracle9i Real Application Clusters Guard files, and therefore all files must be regenerated and redeployed using the Oracle9i Real Application Clusters Guard Setup utility.
See Also:
For more information on the configuration files, refer to Appendix B, "Configuration Files". |
For a detailed description of the the parameters in the Oracle9i Real Application Clusters Guard installation configuration parameter file, refer to the Oracle9i Real Application Clusters Guard Concepts and Administration Guide.
This section describes how to configure Oracle9i Real Application Clusters Guard using the Oracle9i Real Application Clusters Guard PFSSETUP utility. The PFSSETUP utility uses the Oracle9i Real Application Clusters Guard configuration file as described in "Setting Up the Configuration File". The PFSSETUP utility automatically searches for the ORACLE_SERVICE.conf
file.
To run the PFSSETUP utility:
The ORACLE_SERVICE environment variable specifies the Oracle9i Real Application Clusters Guard identifier. This identifier differentiates one Oracle9i Real Application Clusters Guard environment from another, and identifies the correct Oracle9i Real Application Clusters Guard configuration file. For example:
$ export ORACLE_SERVICE=SALES $ export DB_NAME=SALES
$ORACLE_HOME/pfs/setup
directory and run the PFSSETUP utility:
$ cd $ORACLE_HOME/pfs/setup $ ./pfssetup
The PFSSETUP utility version information is displayed:
PFS_SETUP for Solaris: Version 9.2.0.1.0 on Mon Mar 19 10:35:53 PST 2002 (c) Copyright 2002 Oracle Corporation. All rights reserved.
ORACLE_SERVICE is set to SALES DB_NAME is set to SALES Do you wish to continue? [Y/N] Y
Y
to continue or N
to exit the PFSSETUP utility.
The Oracle9i Real Application Clusters Guard Setup main menu appears:
Choose the set of files from the following: 1] User definitions file 2] ORACLE Real Application Clusters Guard files 3] ORACLE network files 4] ORACLE instance files 5] ORACLE network and instance files 6] All the files 7] Quit PFS_SETUP>
Options 1 to 5 in the preceding menu set up only the files specified in the option. For example, if you choose option 3, then only the ORACLE network files are set up.
The following menu appears:
Choose an operation on the selected files: 1] Generate only 2] Deploy only 3] Generate and deploy 4] Deinstall 5] List the affected files 6] Return to Main Menu PFS_SETUP>
The list of affected files appears:
The list of affected files is PFS_SALES.RUN PFS_SALES.HALT PFS_SALES.MONSTART PFS_SALES.MONSTOP PFS_SALES_User.def PFS_SALES_System.def listener.ora.ded.pfs tnsnames.ora.ded.pfs tnsnames.ora.ded.clnt.pfs SALES_config1.ded.pfs SALES_config2.ded.pfs SALES_config.pfs init_SALES1_hosta.ora init_SALES2_hostb.ora Do you wish to continue? [Y/N]
Y
to continue.
The PFSSETUP utility generates and deploys the files to each node in the cluster.
When this process is complete, the menu shown in step 5 reappears.
6
to return to the main menu.
7
to exit.
Do not start the Oracle9i Real Application Clusters Guard packs until you have created the Oracle9i Real Application Clusters database. For more information, refer to Chapter 3, "Post-Installation Tasks".
Note:
A description of how to configure the Oracle network is beyond the scope of this guide and is covered in detail in the Oracle Net Services Administrator's Guide and in Oracle9i Real Application Clusters Concepts. However, to configure a minimal network before exploring the features of Oracle9i Real Application Clusters Guard, verify that multiple copies of the tnsnames.ora
, sqlnet.ora
, and listener.ora
files do not exist.
The PFSSETUP utility creates the required Oracle Net Services configuration files for the Oracle9i Real Application Clusters Guard environment, based on the information entered in the Oracle9i Real Application Clusters Guard configuration file. During the deployment phase, the Oracle9i Real Application Clusters Guard setup utility automatically copies the generated Oracle Net Services files (tnsnames.ora
and listener.ora
) appended with a descriptive name and a .pfs
extension, into the $TNS_ADMIN
directory. The path for the $TNS_ADMIN
directory is specified in the Oracle9i Real Application Clusters Guard configuration file. The default setting for the TNS_ADMIN environment variable is $ORACLE_HOME/network/admin
.
To avoid interfering with a currently running Oracle9i Real Application Clusters environment, the PFSSETUP utility does not automatically replace or install newly generated network files. Before you can use Oracle9i Real Application Clusters Guard, you must append the files generated by the PFSSETUP utility to the current Oracle Net Services configuration files. See Chapter 3 for more information on using the Oracle9i Real Application Clusters Guard files.
The following Oracle Net Services files are generated by the PFSSETUP utility:
This section provides information on dedicated sessions.
During the Oracle9i Real Application Clusters Guard setup, a listener.ora.ded.pfs
file for the server nodes is created in the $TNS_ADMIN
directory if the TNS_ADMIN environment variable is defined, or in the $ORACLE_HOME/network/admin
directory if the TNS_ADMIN environment variable is not defined.
The following examples show sample listener configurations generated by the PFSSETUP utility.
SALES_hosta_LSNR= (DESCRIPTION= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.21)(PORT=2024)(QUEUESIZE=1024))) STARTUP_WAIT_TIME_SALES_hosta_LSNR=0 CONNECT_TIMEOUT_SALES_hosta_LSNR=10 #TRACE_LEVEL_SALES_hosta_LSNR=SUPPORT SALES_hostb_LSNR= (DESCRIPTION= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.22) (PORT=2024)(QUEUESIZE=1024))) STARTUP_WAIT_TIME_SALES_hostb_LSNR=0 CONNECT_TIMEOUT_SALES_hostb_LSNR=10 #TRACE_LEVEL_SALES_hostb_LSNR=SUPPORT
SID_LIST_SALES_hosta_PRIVLSNR= (SID_LIST= (SID_DESC=(ORACLE_HOME=/u01/app/oracle/SALES/92) (SID_NAME=SALES1))) SALES_hosta_PRIVLSNR= (DESCRIPTION= (ADDRESS=(PROTOCOL=TCP) (HOST=192.10.1.51) (PORT=2024) (QUEUESIZE=1024))) STARTUP_WAIT_TIME_SALES_hosta_PRIVLSNR=0 CONNECT_TIMEOUT_SALES_hosta_PRIVLSNR=10 #TRACE_LEVEL_SALES_hosta_PRIVLSNR=SUPPORT SID_LIST_SALES_hostb_PRIVLSNR= (SID_LIST= (SID_DESC=(ORACLE_HOME=/u01/app/oracle/SALES/92) (SID_NAME=SALES2))) SALES_hostb_PRIVLSNR= (DESCRIPTION= (ADDRESS=(PROTOCOL=TCP) (HOST=192.10.1.52) (PORT=2024) (QUEUESIZE=1024))) STARTUP_WAIT_TIME_SALES_hostb_PRIVLSNR=0 CONNECT_TIMEOUT_SALES_hostb_PRIVLSNR=10 #TRACE_LEVEL_SALES_hostb_PRIVLSNR=SUPPORT
During the Oracle9i Real Application Clusters Guard setup, a tnsnames.ora.ded.clnt.pfs
file for the client is created in the $TNS_ADMIN
directory if the TNS_ADMIN environment variable is defined, or in the $ORACLE_HOME/network/admin
directory if the TNS_ADMIN environment variable is not defined.
The following examples show sample service aliases in the client tnsnames.ora.ded.clnt
file generated by the PFSSETUP utility.
SALES_DED= (DESCRIPTION= (LOAD_BALANCE=OFF) (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.21)(PORT=2024)) (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.22)(PORT=2024)) ) (CONNECT_DATA= (SERVICE_NAME=SALES.oracle.com) (SERVER=DEDICATED) (INSTANCE_ROLE=PRIMARY) ) )
SALES_DED_BASIC= (DESCRIPTION= (LOAD_BALANCE=OFF) (FAILOVER=ON) (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.21)(PORT=2024)) (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.22)(PORT=2024))) (CONNECT_DATA= (SERVICE_NAME=SALES.oracle.com) (SERVER=DEDICATED) (INSTANCE_ROLE=PRIMARY) (FAILOVER_MODE= (BACKUP=SALES_DED_BASIC_BACKUP) (TYPE=SELECT) (METHOD=BASIC) (RETRIES=180) (DELAY=5) ))) SALES_DED_BASIC_BACKUP= (DESCRIPTION= (LOAD_BALANCE=OFF) (FAILOVER=ON) (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.22)(PORT=2024)) (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.21)(PORT=2024))) (CONNECT_DATA= (SERVICE_NAME=SALES.oracle.com) (SERVER=DEDICATED) (INSTANCE_ROLE=PRIMARY) (FAILOVER_MODE= (BACKUP=SALES_DED_BASIC) (TYPE=SELECT) (METHOD=BASIC) (RETRIES=180) (DELAY=5) )))
SALES_DED_PRE= (DESCRIPTION= (LOAD_BALANCE=OFF) (FAILOVER=ON) (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.21)(PORT=2024)) (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.22)(PORT=2024))) (CONNECT_DATA= (SERVICE_NAME=SALES.oracle.com) (SERVER=DEDICATED) (INSTANCE_ROLE=PRIMARY) (FAILOVER_MODE= (BACKUP=SALES_DED_PRE_SECONDARY) (TYPE=SELECT) (METHOD=PRECONNECT) (RETRIES=180) (DELAY=5) ))) SALES_DED_PRE_SECONDARY= (DESCRIPTION= (LOAD_BALANCE=OFF) (FAILOVER=ON) (ADDRESS_LIST= (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.22)(PORT=2024)) (ADDRESS=(PROTOCOL=TCP)(HOST=192.10.1.21)(PORT=2024)) (CONNECT_DATA= (SERVICE_NAME=SALES.oracle.com) (SERVER=DEDICATED) (INSTANCE_ROLE=SECONDARY) (FAILOVER_MODE= (BACKUP=SALES_DED_PRE) (TYPE=SELECT) (METHOD=PRECONNECT) (RETRIES=48) (DELAY=900)
|
![]() Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|