Oracle Real Application Clusters Guard Administration and Reference Guide
Release 9.0.1

Part Number A88810-02
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to next page

1
Oracle Real Application Clusters Guard Configuration Parameters

This chapter describes the Oracle Real Application Clusters Guard configuration parameters. It contains the following sections:

Overview of the Oracle Real Application Clusters Guard Configuration File

Oracle Real Application Clusters Guard provides a set of templates that allow Oracle Real Application Clusters Guard to be easily configured. The templates contain tested configurations for such settings as Oracle Net Service parameters and initialization parameters. The Oracle Real Application Clusters Guard Setup Utility (PFSSETUP) generates and deploys the files that are required by Oracle Real Application Clusters Guard. The files are automatically generated with the correct values, derived from the customized configuration file ($ORACLE_SERVICE.conf).

The Oracle Real Application Clusters Guard configuration file template is located in:

$ORACLE_HOME/pfs/setup/conf/savusetup.dat

The information in this file corresponds to a single Oracle9i Real Application Clusters database. If multiple databases are part of your Oracle Real Application Clusters Guard configuration, then a separate configuration file must be created for each database.

Copy the configuration file template:

$ cd $ORACLE_HOME/pfs/setup/conf
$ cp savusetup.dat $ORACLE_SERVICE.conf

Use a text editor to modify the new configuration file.

See Also:

Your platform-specific Oracle Real Application Clusters Guard installation guide for more information about using the configuration file 

The configuration parameters are grouped by the method that must be employed to modify the parameters. You may want to change the relocatable IP address, for example, if it conflicts with another IP address in the network, or you may want to turn on debugging to do some troubleshooting. Depending on the parameter that needs to be changed, there are different methods that you must employ to make the changes.

The methods of changing Oracle Real Application Clusters Guard parameters are summarized in Table 1-1.

Table 1-1 How to Modify the Oracle Real Application Clusters Guard Configuration Parameter File  
Type of Configuration Parameter  PFSSETUP  Operating System  Oracle 

Permanent Cluster and Database Parameters 

Generate and deploy all the files (option 6). 

Recreate the existing packs by using the DELETEPACKS and CREATEPACKS scripts. 

Shut down the database. 

Operating System Specific Configuration Parameters 

Generate and deploy the user definitions file (option 1). 

Recreate the existing packs by using the DELETEPACKS and CREATEPACKS scripts. 

Shut down the database. 

Database and Oracle Real Application Clusters Guard Configuration Parameters 

Generate and deploy all the files (option 6). 

Halt the packs. 

Run the catpfs.sql script. 

Oracle Real Application Clusters Guard Configuration Parameters 

Generate and deploy the user definitions file (option 1). 

Halt the packs. 

Shut down the database. 

Network Configuration Parameters 

Generate and deploy the user definitions file (option 1) and the Oracle network files (option 3). 

Halt the packs. 

Shut down the database and the listeners. 

Database Configuration Parameters 

Generate and deploy the Oracle instance files (option 4). 

Halt the packs. 

Shut down the database and the listeners. 

See Also:

"Changing Oracle Real Application Clusters Guard Configuration Parameters" for detailed steps for changing each type of configuration parameter 

Oracle Real Application Clusters Guard Configuration Parameters

The Oracle Real Application Clusters Guard configuration parameters are described in the following sections:

Permanent Cluster and Database Parameters

Table 1-2 contains the permanent cluster and database parameters.

Table 1-2 Permanent Cluster and Database Configuration Parameters  
Parameter Name  Value  Description 

PLATFORM 

Example: HP, SUN

Default: None 

Specifies the hardware cluster platform 

PFS_CLUSTER_NAME 

Range of values: A valid cluster name that does not include a dash (-)

Default: None 

Specifies the cluster name. It should be unique among the clusters that run on the same network. 

PFS_HOSTA 

Range of values: A valid host name that does not include a dash (-)

Default: None 

Specifies a host that is part of the Oracle Real Application Clusters Guard cluster 

PFS_HOSTB 

Range of values: A valid host name that does not include a dash (-)

Default: None 

Specifies a host that is part of the Oracle Real Application Clusters Guard cluster 

ORACLE_BASE 

Range of values: Any valid directory

Default: None

Recommended OFA value: software_mount_point/app/oracle

Example: /u01/app/oracle 

Specifies the directory at the top of the Oracle software and administrative file structure. It must be identical for all nodes of a cluster that access the database. 

ORACLE_HOME 

Range of values: Any valid directory

Default: None

Recommended OFA value:
$ORACLE_BASE/product/release

Example: /u01/app/oracle/product/9.0.1 

Specifies the directory containing the Oracle software for a specific Oracle Server release. It must be identical for all nodes of a cluster that access the database. 

DB_NAME 

Range of values: Valid database name

Default: None

Example: PRO 

Specifies the value of the DB_NAME initialization parameter entered during installation or database creation. Multiple instances must have the same value for DB_NAME

PFS_IP_PACK_HOSTA 

 

Specifies an IP address that you want to add to a LAN interface card. The IP address will move with the pack if the pack is moved to another node. 

PFS_IP_PACK_HOSTB 

 

Specifies an IP address that you want to add to a LAN interface card. The IP address will move with the pack if the pack is moved to another node. 

PFS_IP_SUBNET_HOSTA 

 

Specifies the subnet for the IP address that is added to a LAN interface card. The IP address will move with the pack if the pack is moved to another node. 

PFS_IP_SUBNET_HOSTB 

 

Specifies the subnet for the IP address that is added to a LAN interface card. The IP address will move with the pack if the pack is moved to another node. 

Operating System Specific Configuration Parameters

This section contains parameters that are specific to the Sun and HP platforms. Table 1-3 contains parameters that are specific to the Sun platform.

Table 1-3 Sun-Specific Configuration Parameters  
Parameter Name  Value  Description 

PFS_NET_IF_A 

 

Specifies a network controller interface. The hme0 interfaces are typically used for the primary public network. The value varies depending on the public network configuration. 

PFS_NET_IF_B 

 

Specifies a network controller interface. The hme0 interfaces are typically used for the primary public network. The value varies depending on the public network configuration. 

START_NET_TIMEOUT 

Default: 180 

Specifies the maximum time in seconds for Sun Cluster to start the pack 

STOP_NET_TIMEOUT 

Default: 180 

Specifies the maximum time in seconds for Sun Cluster to stop the pack 

Table 1-4 contains parameters that are specific to the HP platform.

Table 1-4 HP-Specific Configuration Parameters
Parameter Name  Value  Description 

PFS_VG_HOSTA 

Example:
"emc1 emc2 emc3" 

Specifies the disk/volume groups used by the database. The value must be enclosed in double quotes. 

PFS_VG_HOSTB 

Example:
"emc1 emc2 emc3" 

Specifies the disk/volume groups used by the database. The value must be enclosed in double quotes. 

Database and Oracle Real Application Clusters Guard Configuration Parameters

Table 1-5 contains database and Oracle Real Application Clusters Guard parameters.

Table 1-5 Database and Oracle Real Application Clusters Guard Configuration Parameters  
Parameter Name  Value  Description 

ORACLE_SERVICE 

 

Specifies the name of the service. Must be unique in the cluster. Oracle Corporation recommends restricting the name to 4 characters to avoid filename problems on heterogeneous systems. 

ORACLE_USER 

Range of values: Any valid operating system (OS) user that is part of the OS DBA group 

Specifies the name of the operating system oracle user. This is the user that owns the Oracle Real Application Clusters Guard software. 

ORACLE_SID_HOSTA 

Range of values: Any valid ORACLE_SID string

Default: None

Example: PRO1 

Specifies the Oracle System Identifier (SID), which is the same as the Oracle server instance. Because the SID is incorporated into many 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 an Oracle9i Real Application Clusters cluster should be unique and should incorporate the name of the database it manipulates. 

ORACLE_SID_HOSTB 

Range of values: Any valid ORACLE_SID string

Default: None

Example: PRO2 

Specifies the Oracle System Identifier (SID), which is the same as the Oracle server instance. Because the SID is incorporated into many 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 an Oracle9i Real Application Clusters cluster should be unique and should incorporate the name of the database it manipulates. 

INSTANCE_NAME_HOSTA 

Default: None

Example: PRO1 

Specifies 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 initialization parameter file. The INSTANCE_NAME for each instance in an Oracle9i Real Application Clusters cluster must be unique. 

INSTANCE_NAME_HOSTB 

Default: None

Example: PRO2 

Specifies 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 initialization parameter file. The INSTANCE_NAME for each instance in an Oracle9i Real Application Clusters cluster must be unique. 

SERVICE_NAMES 

Range of values: Any ASCII string

Example: PRO.oracle.com, where PRO is the database name and oracle.com is the database domain 

Specifies the name of the database service on the network. By default, Oracle Universal Installer and Oracle Database Configuration Assistant create a service name that includes the entire global database name, a name comprised of the database name (DB_NAME) and the 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 uses of an instance can be identified separately. 

IS_MTS 

Range of values:
$PFS_TRUE (1),
$PFS_FALSE (0)

Default: $PFS_FALSE 

Specify $PFS_TRUE if you are running a shared server process 

TNS_ADMIN 

Range of values: Any valid directory

Default: $ORACLE_HOME/network/admin 

Specifies the directory containing the Oracle Net configuration files. It must be identical for all nodes of a cluster that access the database. 

Oracle Real Application Clusters Guard Configuration Parameters

Table 1-6 contains Oracle Real Application Clusters Guard configuration parameters.

Table 1-6 Oracle Real Application Clusters Guard Configuration Parameters  
Parameter Name  Value  Description 

PFILE_HOSTA 

Range of values: Any valid initialization parameter file that references control files

Default setting for OFA configuration:
$ORACLE_BASE
/admin/$DB_NAME
/pfile
/init$ORACLE_SID_HOSTA.ora

Default setting for non-OFA configuration:
$ORACLE_HOME
/dbs/init$ORACLE_SID_HOSTA.ora
 

Specifies the initialization parameter file that is used when Oracle Real Application Clusters Guard starts the instance 

PFILE_HOSTB 

Range of values: Any valid initialization parameter file that references control files

Default setting for OFA configuration:
$ORACLE_BASE
/admin/$DB_NAME
/pfile
/init$ORACLE_SID_HOSTB.ora

Default setting for non-OFA configuration:
$ORACLE_HOME
/dbs/init$ORACLE_SID_HOSTB.ora
 

Specifies the initialization parameter file that is used when Oracle Real Application Clusters Guard starts the instance 

PFS_PREFERRED_PRIMARY 

Range of values: $PFS_HOSTA, $PFS_HOSTB

Default: $PFS_HOSTA 

Specifies the preferred primary node of the cluster 

PFS_PREFERRED_SECONDARY 

Range of values: $PFS_HOSTA, $PFS_HOSTB

Default: $PFS_HOSTB 

Specifies the preferred secondary node of the cluster 

PFS_LANGUAGE 

Range of values: Any valid language name

Default: AMERICAN 

The NLS_LANG environment variable has three components: language, territory, and character set. The format of the NLS_LANG environment variable is LANGUAGE_TERRITORY.CHARSET.

PFS_LANGUAGE specifies language conventions for Oracle messages, day names, and month names. Each supported language has a unique name such as AMERICAN or JAPANESE.

PFS_TERRITORY specifies conventions such as calendar, date, monetary, and numeric formats. Each supported territory has a unique name such as AMERICA or JAPAN.

CHARSET specifies the character set used by the client application. Each supported character set has a unique acronym such as US7ASCII or UTF8.

See Also: Oracle9i Globalization Support Guide 

PFS_TERRITORY 

Range of values: Any valid territory name

Default: AMERICA 

CHARSET 

Range of values: Any valid character set

Default: US7ASCII 

PFS_KEEP_PRIMARY 

Range of values: $PFS_TRUE (1), $PFS_FALSE (0)

Default: $PFS_TRUE 

Specifies whether to leave the primary pack up when the secondary pack does not come up during PFSBOOT.

See Also: "Changing the PFS_KEEP_PRIMARY Parameter" 

PFS_DEBUGGING 

Range of values: $PFS_TRUE (1), $PFS_FALSE (0)

Default: $PFS_FALSE 

Specifies whether to enable or disable Oracle Real Application Clusters Guard debugging 

LISTENER_CHECK_INTERVAL 

Range: At least 0

Default: 5 

Specifies in seconds the frequency with which the listener monitor checks the public listener 

PRIV_LSNR_CHECK_INTERVAL 

Range: At least 0

Default: 60 

Specifies in seconds the frequency with which the listener monitor checks the private listener 

MAX_LSNR_RESTART 

Range of values: At least 0

Default: 3 

Specifies the maximum number of times the listener can be restarted 

MIN_LSNR_RESTART_INTERVAL 

Range of values: At least 0

Default: 300 

Specifies in seconds the time period in which Oracle Real Application Clusters Guard can try to restart the listener. If Oracle Real Application Clusters Guard tries to restart the listener more than MAX_LSNR_RESTART times within MIN_LSNR_RESTART_INTERVAL, then Oracle Real Application Clusters Guard exits the listener monitor. 

DUMPLSNR_TIMEOUT 

Range of values: At least 0

Default: 60 

Specifies in seconds how long to wait for the NETSTAT -rn command to complete 

ORACLE_ARCH_TIMEOUT 

Range of values: At least 0

Default: 60 

Specifies in seconds how long to wait for ALTER DATABASE ARCHIVE LOG ALL statement to complete 

ORACLE_CKPT_TIMEOUT 

Range of values: At least 0

Default: 60 

Specifies in seconds how long to wait for ALTER SYSTEM CHECKPOINT GLOBAL statement to complete 

PFS_DUMP_LEVEL 

Range of values: 0 to 10

Default: 10 

Specifies the dump level associated with Oracle system state dumps 

ORACLE_DUMP_TIMEOUT 

Range of values: At least 0

Default: 60 

Specifies in seconds how long to wait for Oracle SYSTEMSTATE and Oracle9i Real Application Clusters lock tree dump to complete 

Network Configuration Parameters

Table 1-7 contains network configuration parameters.

Table 1-7 Network Configuration Parameters
Parameter Names  Value  Description 

PFS_IP_HOSTA 

 

Specifies the static IP address on PFS_HOSTA 

PFS_IP_HOSTB 

 

Specifies the static IP address on PFS_HOSTB 

PFS_PORT_DED_HOSTA 

Range of values: 1025 to 65535 

Specifies the port setting for a dedicated configuration on PFS_HOSTA. Many operating systems reserve port numbers below 1024 for use by privileged processes. 

PFS_PORT_DED_HOSTB 

Range of values: 1025 to 65535 

Specifies the port setting for a dedicated configuration on PFS_HOSTB. Many operating systems reserve port numbers below 1024 for use by privileged processes. 

PFS_PORT_MTS_HOSTA 

Range of values: 1025 to 65535 

Specifies the port setting for a shared server configuration on PFS_HOSTA. Many operating systems reserve port numbers below 1024 for use by privileged processes. 

PFS_PORT_MTS_HOSTB 

Range of values: 1025 to 65535 

Specifies the port setting for a shared server configuration on PFS_HOSTB. Many operating systems reserve port numbers below 1024 for use by privileged processes. 

Database Configuration Parameters

Table 1-8 contains database configuration parameters.

Table 1-8 Database Configuration Parameters  
Parameter Name  Value  Description 

DB_DOMAIN 

Range of values: Any legal string of name components, separated by periods, and up to 128 characters long. This value cannot be null.

Default: WORLD

Example: oracle.com 

Specifies the database domain in which the database is located, entered during installation or database creation. When possible, Oracle Corporation recommends that the database domain mirror the network domain. 

INSTANCE_NUMBER_HOSTA 

Example: 1 

Specifies a unique number that maps the instance to one free list group for each database object created with the FREELIST_GROUPS storage parameter. Oracle Corporation recommends setting INSTANCE_NUMBER_HOSTn to the same value as the THREAD_HOSTn parameter. 

INSTANCE_NUMBER HOSTB 

Example: 2 

Specifies a unique number that maps the instance to one free list group for each database object created with the FREELIST_GROUPS storage parameter. Oracle Corporation recommends setting INSTANCE_NUMBER_HOSTn to the same value as the THREAD_HOSTn parameter. 

THREAD_HOSTA 

Range of values: 0 to maximum number of enabled threads

Example: 1 

Specifies the number of the redo thread 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 instance. Also, an instance cannot start when its redo thread is disabled. A value of 0 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.

Multiple instance must have different values for THREAD_HOSTA and THREAD_HOSTB

THREAD_HOSTB 

Range of values: 0 to maximum number of enabled threads

Example: 2 

Specifies the number of the redo thread 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 instance. Also, an instance cannot start when its redo thread is disabled. A value of 0 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.

Multiple instance must have different values for THREAD_HOSTA and THREAD_HOSTB

Changing Oracle Real Application Clusters Guard Configuration Parameters

Use different methods to change Oracle Real Application Clusters Guard configuration parameters. This section contains the following topics:

The procedures that are described in these sections use the PFSCTL command line.

See Also:

Chapter 2, "Using Oracle Real Application Cluster Guard Commands" 

Changing Permanent Cluster and Database Parameters

To modify the parameters in Table 1-2, you must:

  1. Generate and deploy all the files.

  2. Re-create the packs.

You may want to change these parameters in the following situations:

For example, you might need to change the relocatable IP address if it conflicts with another IP address in the network. Another example is changing $ORACLE_HOME if the original file system where $ORACLE_HOME resided becomes unavailable.

The following steps and examples show how to reinstall Oracle Real Application Clusters Guard after modifying the parameters in Table 1-2:

  1. Modify the parameters from Table 1-2 in the $ORACLE_SERVICE.conf file.

  2. Invoke the PFSCTL command line as root:

    # pfsctl
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
    (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    
  3. Shut down the packs:

    PFSCTL> pfshalt
    
    

    You should see output similar to the following:

    pfshalt command succeeded.
    
    
  4. Generate a new set of Oracle Real Application Clusters Guard files. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFSSETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
       
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N]
    
    
  5. Enter y to continue. You should see output similar to the following:

    PFSSETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 200
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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
    
    
  6. Choose option 6:

    PFS_SETUP> 6
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ALL_FILES
    
    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
    
    
  7. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     PFS_SALES_HOSTA.RUN 
     PFS_SALES_HOSTB.RUN 
     PFS_SALES_HOSTA.HALT 
     PFS_SALES_HOSTB.HALT 
     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]
    
    
  8. Enter y to continue. You should see output similar to the following:

    Backing up directory on /home_oracle/901_sales/pfs/setup/output/SALES/packs  
    HOSTA
    Backing up directory on
    /home_oracle/901_sales/pfs/setup/output/SALES/include HOSTA
    Generating ORACLE Real Application Clusters Guard files
    Generating Packs
    Backing up directory on /home_oracle/901_
    sales/pfs/setup/output/SALES/network HOSTA
    Generating ORACLE network files
    Backing up directory on /home_oracle/901_sales/pfs/setup/output/SALES/pfile 
    HOSTA
    Generating ORACLE instance files
    
    
  9. Deploy the new set of Oracle Real Application Clusters Guard files. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N]
    
    
  10. Enter y to continue. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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>
    
    
  11. Choose option 6:

    PFS_SETUP> 6
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ALL_FILES
    
    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
    
    
  12. Choose option 2:

    PFS_SETUP> 2
    
    
  13. Delete the existing packs as root:

    # deletepacks
    
    
  14. Create the new packs as root:

    # createpacks
    
    
  15. Start the packs, using PFSCTL as root.

    # pfsctl
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
    (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  16. Enter the PFSBOOT command:

    PFSCTL> pfsboot
    
    

    You should see output similar to the following:

    pfsboot command succeeded.
    

Changing Operating System Specific Configuration Parameters

To modify the parameters in Table 1-3 and Table 1-4, you must:

  1. Generate and deploy the user definitions file.

  2. Re-create the packs.

This is necessary in the following situations:

For example, you might need to change the maximum time in seconds to wait when Oracle Real Application Clusters Guard starts a relocatable IP address. Another example is needing to add more disk groups if you increase the number of datafiles in the database.

The following steps and examples show how to create a new user definitions file:

  1. Modify the parameters from Table 1-3 and Table 1-4 in the $ORACLE_SERVICE.conf file.

  2. Invoke PFSCTL as root.

    $ pfsctl        
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    
  3. Shut down the packs:

    PFSCTL> pfshalt
    
    

    You should see output similar to the following:

    pfshalt command succeeded.
    
    
  4. Generate a new user definitions file. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N]
    
    
  5. Enter y to continue. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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
    
    
  6. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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
    
    
  7. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     PFS_SALES_User.def
    
    Do you wish to continue? [Y/N] 
    
    
  8. Enter y to continue. You should see output similar to the following:

    Backing up directory on /home_oracle/901_
    sales/pfs/setup/output/SALES/include HOSTA
    
    
  9. Deploy a new user definitions file. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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
    
    
  10. Choose option 2:

    PFS_SETUP> 2
    
    

    You should see output similar to the following:

    The list of affected files is
    PFS_SALES_User.def
    
    Do you wish to continue? [Y/N]
    
    
  11. Enter y to continue. You should see output similar to the following:

    Deploying user file
    Backing up directory on /mnt1/oracle/admin/sales/pfs/include HOSTA
    Backing up directory on /mnt1/oracle/admin/sales/pfs/include HOSTB
    
    
  12. Delete the existing packs as root:

    # deletepacks
    
    
  13. Create the new packs as root:

    # createpacks
    
    
    
  14. Invoke PFSCTL as root.

    # pfsctl        
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    
  15. Start the packs:

    PFSCTL> pfsboot
    
    

    You should see output similar to the following:

    pfsboot command succeeded.
    

Changing Database and Oracle Real Application Clusters Guard Configuration Parameters

To modify the parameters in Table 1-5, you must:

  1. Generate and deploy all the files.

  2. Run catpfs.sql to re-create the Oracle Real Application Clusters Guard schema.

This is necessary in the following situations:

For example, you may need to change the $ORACLE_SID parameter, or you may want to configure Oracle Real Application Clusters Guard to support a shared server.

The following steps and examples show how to create new Oracle Real Application Clusters Guard files and Oracle Real Application Clusters Guard schema.

  1. Modify the parameters from Table 1-5 in the $ORACLE_SERVICE.conf file.

  2. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
    (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  3. Shut down the packs:

    PFSCTL> pfshalt
    
    

    You should see output similar to the following:

    pfshalt command succeeded.
    
    
  4. Generate a new set of Oracle Real Application Clusters Guard files. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N]
    
    
  5. Enter y to continue. You should see output similar to the following:

    
    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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> 
    
    
  6. Choose option 6:

    PFS_SETUP> 6
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ALL_FILES
    
    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> 
    
    
  7. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     PFS_SALES_HOSTA.RUN 
     PFS_SALES_HOSTB.RUN 
     PFS_SALES_HOSTA.HALT 
     PFS_SALES_HOSTB.HALT 
     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] 
    
    
  8. Enter y to continue. You should see output similar to the following:

    Backing up directory on /home_oracle/901_sales/pfs/setup/output/SALES/packs  
    HOSTA
    Backing up directory on /home_oracle/901_
    sales/pfs/setup/output/SALES/include  HOSTA
    Generating ORACLE Real Application Clusters Guard files
    Generating Packs
    Backing up directory on /home_oracle/901_
    sales/pfs/setup/output/SALES/network  HOSTA
    Generating ORACLE network files
    Backing up directory on /home_oracle/901_sales/pfs/setup/output/SALES/pfile  
    HOSTA
    Generating ORACLE instance files
    
    
  9. Deploy the new set of Oracle Real Application Clusters Guard files. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N] 
    
    
  10. Enter y to continue. You should see output similar to the following:

    
    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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> 
    
    
  11. Choose option 6:

    PFS_SETUP> 6
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ALL_FILES
    
    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> 
    
    
  12. Choose option 2:

    PFS_SETUP> 2
    
    
  13. Open the database outside of the packs.

  14. Run catpfs.sql to recreate the Oracle Real Application Clusters Guard schema. Enter the following commands:

    $ sqlplus "system/manager as sysdba"
    SQL> @?/pfs/admin/catpfs.sql
    
    
  15. Shut down the database.

  16. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  17. Start the packs:

    PFSCTL> pfsboot
    
    

    You should see output similar to the following:

    pfsboot command succeeded.
    

Changing Oracle Real Application Clusters Guard Configuration Parameters

To modify the parameters in Table 1-6, you must generate and deploy the user definitions file.

This is necessary if you want to change one of the Oracle Real Application Clusters Guard settings that was originally specified during Oracle Real Application Clusters Guard installation.

For example, you may need to change the location of the initialization parameter file that Oracle Real Application Clusters Guard uses to start up the instance, or you may need to turn on debugging to troubleshoot Oracle Real Application Clusters Guard.

The following steps and example show how to create a new user definitions file.

  1. Modify the parameters from Table 1-6 in the $ORACLE_SERVICE.conf file.

  2. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL>
    
    
  3. Shut down the packs:

    PFSCTL> pfshalt
    
    

    You should see output similar to the following:

    pfshalt command succeeded.
    
    
  4. Generate a new user definitions file. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N] 
    
    
  5. Enter y to continue. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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> 
    
    
  6. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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> 
    
    
  7. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     PFS_SALES_User.def
    
    Do you wish to continue? [Y/N] 
    
    
  8. Enter y to continue. You should see output similar to the following:

    Backing up directory on /home_oracle
    /901_sales/pfs/setup/output/SALES/include HOSTA
  9. Deploy a new user definitions file. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    	PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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> 
    
    
  10. Choose option 2:

    PFS_SETUP> 2
    
    

    You should see output similar to the following:

    The list of affected files is
    PFS_SALES_User.def
    
    Do you wish to continue? [Y/N] 
    
    
  11. Enter y to continue. You should see output similar to the following:

    Deploying user file
    Backing up directory on /mnt1/oracle/admin/sales/pfs/include HOSTA
    Backing up directory on /mnt1/oracle/admin/sales/pfs/include HOSTB
    
    
  12. Invoke PFSCTL as root.

    # pfsctl        
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
    (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  13. Start the packs:

    PFSCTL> pfsboot
    
    

    You should see output similar to the following:

    pfsboot command succeeded.
    

Changing Network Configuration Parameters

To modify the parameters in Table 1-7, you must:

  1. Generate and deploy the user definitions files.

  2. Generate and deploy the Oracle network files.

This is necessary when you want to change one of the network settings that was specified during Oracle Real Application Clusters Guard installation.

For example, you may need to change the port number for the Oracle Real Application Clusters Guard listener.

The following steps and examples show how to create a new user definitions file and new Oracle network files.

  1. Modify the parameters from table Table 1-7 in the $ORACLE_SERVICE.conf file.

  2. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  3. Shut down the packs:

    PFSCTL> pfshalt
    
    

    You should see output similar to the following:

    pfshalt command succeeded.
    
    
  4. Generate a new user definitions file and new Oracle Network files. Invoke PFSSETUP as $ORACLE_USER:

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N] 
    
    
  5. Enter y to continue. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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> 
    
    
  6. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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> 
    
    
  7. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     PFS_SALES_User.def
    
    Do you wish to continue? [Y/N] 
    
    
  8. Enter y to continue. You should output similar to the following:

    Backing up directory on /home_oracle/901_
    sales/pfs/setup/output/SALES/include HOSTA
    
    Press Enter to continue
    
    
  9. Press the Enter key. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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> 
    
    
  10. Choose option 6:

    PFS_SETUP> 6
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N] 
    
    
  11. Enter y to continue. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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>
    
    
  12. Choose option 3:

    PFS_SETUP> 3
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_NETWORK_FILE
    
    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> 
    
    
  13. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     listener.ora.ded.pfs 
     tnsnames.ora.ded.pfs 
     tnsnames.ora.ded.clnt.pfs 
    
    Do you wish to continue? [Y/N] 
    
    
  14. Enter y to continue.

  15. Deploy a new user definitions file. Invoke PFSSETUP as $ORACLE_USER.

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_USER_FILE
    
    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> 
    
    
  16. Choose option 2:

    PFS_SETUP> 2
    
    

    You should see output similar to the following:

    The list of affected files is
    PFS_SALES_User.def
    
    Do you wish to continue? [Y/N] 
    
    
  17. Enter y to continue. You should see output similar to the following:

    Deploying user file
    Backing up directory on /mnt1/oracle/admin/sales/pfs/include HOSTA
    Backing up directory on /mnt1/oracle/admin/sales/pfs/include HOSTB
     
    Press Enter to continue
    
    
  18. Press the Enter key. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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>
    
    
  19. Choose option 3:

    PFS_SETUP> 3
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_NETWORK_FILE
    
    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> 
    
    
  20. Choose option 2:

    PFS_SETUP> 2
    
    

    You should see output similar to the following:

    The list of affected files is
     listener.ora.ded.pfs 
     tnsnames.ora.ded.pfs 
     tnsnames.ora.ded.clnt.pfs 
    
    Do you wish to continue? [Y/N] 
    
    
  21. Enter y to continue.

  22. On both nodes, change the network file suffixes as follows:

    • From listener.ora.ded.pfs to listener.ora

    • From tnsnames.ora.ded.pfs to tnsnames.ora

  23. Distribute the tnsnames.ora.ded.clnt.pfs file to the client nodes.

  24. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
    (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL>
    
    
  25. Start the packs:

    PFSCTL> pfsboot 
    
    

    You should see output similar to the following:

    pfsboot command succeeded.
    

Changing Database Configuration Parameters

To modify the parameters in Table 1-8, you must generate and deploy the Oracle instance files.

This is necessary if you want to change one of the database settings that was specified during Oracle Real Application Clusters Guard installation.

For example, you may need to change the database domain to mirror the network domain.

The following steps and examples show how to create new Oracle instance files.

  1. Modify the parameters from Table 1-8 in the $ORACLE_SERVICE.conf file.

  2. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  3. Stop the packs:

    PFSCTL> pfshalt
    
    

    You should see output similar to the following:

    pfshalt command succeeded.
    
    
  4. Generate a new Oracle instance file. Invoke PFSSETUP as $ORACLE_USER.

    $ pfssetup
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:06 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    Do you wish to continue? [Y/N] 
    
    
  5. Enter y to continue. You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:32:54 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    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> 
    
    
  6. Choose option 4:

    PFS_SETUP> 4
    
    

    You should see output similar to the following:

    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_INSTANCE_FILE
    
    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> 
    
    
  7. Choose option 1:

    PFS_SETUP> 1
    
    

    You should see output similar to the following:

    The list of affected files is
     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] 
    
    
  8. Enter y to continue. You should see output similar to the following:

    Backing up directory on /home_oracle/901_sales/pfs/setup/output/SALES/pfile  
    HOSTA
    Generating ORACLE instance files.
    
    
  9. Deploy a new Oracle instance file. Invoke PFSSETUP as $ORACLE_USER.

    $ pfssetup
    
    

    You should see output similar to the following:

     
    PFS_SETUP for Solaris: Version 9.0.1.0_0 on Wed Feb  1 15:33:16 PST 2001
    (c) Copyright 2001 Oracle Corporation.  All rights reserved.
    
    ORACLE_BASE is set to /mnt1/oracle
    ORACLE_HOME is set to /home_oracle/901_sales
    PFS_HOME is set to /mnt1/oracle/admin/sales/pfs
    TNS_ADMIN is set to /mnt1/oracle/admin/sales/network/admin
    
    Selected option ORACLE_INSTANCE_FILE
    
    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> 
    
    
  10. Choose option 2:

    PFS_SETUP> 2
    
    

    You should see output similar to the following:

    The list of affected files is
     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] 
    
    
  11. Enter y to continue. You should see output similar to the following:

    Deploying user file
    Backing up directory on /mnt1/oracle/admin/sales/pfs/pfile HOSTA
    Backing up directory on /mnt1/oracle/admin/sales/pfs/pfile HOSTB
    
    
  12. Incorporate the Oracle Real Application Cluster Guard initialization parameter files into the existing initialization parameter files by using the IFILE initialization parameter.

    See Also:

    Oracle9i Database Reference for information about the IFILE initialization parameter 

  13. Invoke PFSCTL as root:

    # pfsctl 
    
    

    You should see output similar to the following:

    PFSCTL for HOSTA: Version 9.0.1.0_0 - Production on  Feb 01 2001 14:38:00
     (c) Copyright 2001 , Oracle Corporation.  All rights reserved.
    Welcome to PFSCTL. Type HELP for additional information.
    
    ORACLE_SERVICE is set to SALES
    DB_NAME is set to sales
    
    PFSCTL> 
    
    
  14. Start the packs:

    PFSCTL> pfsboot
    
    

    You should see output similar to the following:

    pfsboot command succeeded
    

Go to previous page Go to next page
Oracle
Copyright © 1996-2001, Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback