3
Post-Installation Tasks

This chapter describes post-installation tasks. It contains the following sections:

• Post-Installation Tasks for the oracle User

• Post-Installation Tasks for the root User

• Starting Oracle9i Real Application Clusters Guard

• Troubleshooting

  Note: 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 Net Services configuration files.

Post-Installation Tasks for the oracle User

Perform the following steps as the oracle user:

1. Log in as the Oracle software owner, typically, the oracle user.

2. Configure the server using the network configuration files generated by the PFSSETUP utility.

   During the Oracle9i Real Application Clusters Guard setup, the following network configuration files are created:

   File	Description
   listener.ora.ded.pfs	Dedicated server (IS_MTS parameter is set to false) configuration file for the listeners that identifies the Oracle9i Real Application Clusters Guard listener name and the service it is listening for
   listener.ora.mts.pfs	Shared server (IS_MTS parameter is set to true) configuration file for the listeners that identifies the Oracle9i Real Application Clusters Guard listener name and the service it is listening for
   tnsnames.ora.ded.pfs	Dedicated server (IS_MTS parameter is set to false) configuration file that contains net service names mapped to connect descriptors
   tnsnames.ora.ded.clnt.pfs	Dedicated server client (IS_MTS parameter is set to false) configuration file that contains net service names mapped to connect descriptors
   tnsnames.ora.mts.pfs	Shared server (IS_MTS parameter is set to true) configuration file that contains net service names mapped to connect descriptors
   tnsnames.ora.mts.clnt.pfs	Shared server client (IS_MTS parameter is set to true) configuration file that contains net service names mapped to connect descriptors

   The files in the preceeding table are 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.

   1. If network configuration files do not already exist, copy or rename the files to the correct suffix. For example:

      $ cd $TNS_ADMIN
      $ ls
      listener.ora.ded.pfs tnsnames.ora.ded.pfs tnsnames.ora.ded.clnt.pfs
      $ cp listener.ora.ded.pfs listener.ora
      $ cp tnsnames.ora.ded.pfs tnsnames.ora
      
      

   2. Copy the client configuration file, tnsnames.ora.ded.clnt.pfs, to all of the client systems.

   3. If network configuration files already exist, append the Oracle9i Real Application Clusters Guard entries to the existing network configuration files. Ensure that all entries in the network configuration files are unique.

3. Set up the Oracle instance parameter files for Oracle9i Real Application Clusters Guard.

   During the Oracle9i Real Application Clusters Guard setup, the following parameter files are created:

   Filename	Description
   init_ORACLE_SERVICE_HOSTA.pfs	Sample initialization parameter file for host A.
   init_ORACLE_SERVICE_HOSTB.pfs	Sample initialization parameter file for host B.
   ORACLE_SERVICE_config.pfs	Common configuration parameter file containing recommended Oracle9i Real Application Clusters Guard initialization and configuration parameter settings. Parameters for this file should be set for both instances on host A and host B. This file contains two parameters, PFILE_HOSTA and PFILE_HOSTB. These parameters are set to indicate the location of the initialization parameter files for the two hosts. Ensure that these files exist or create a link from the files you want to use to the locations specified by these parameters.
   ORACLE_SERVICE_config_HOSTA.mts.pfs	Host A configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings for a system running shared server configuration.
   ORACLE_SERVICE_config_HOSTA.ded.pfs	Host A configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings for a system running dedicated server configuration.
   ORACLE_SERVICE_config_HOSTB.mts.pfs	Host B configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings for a system running shared server configuration.
   ORACLE_SERVICE_config_HOSTB.ded.pfs	Host B configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings for a system running dedicated server configuration.

   The files in the preceeding table are created in the $ORACLE_BASE/admin/$DB_NAME/pfile directory for an OFA installation, or in the $ORACLE_HOME/pfs/$DB_NAME/pfile for a non OFA installation.

   If you already have initialization parameter files set up for the Oracle9i Real Application Clusters database, you can use the IFILE parameter to include the initialization parameter files created by Oracle9i Real Application Clusters Guard.

   The following example initSALES1.ora file shows a sample initialization parameter file for the first instance:

   ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
   rollback_segments=(rbs1_1, rbs1_2)
   thread=1
   cluster_database=true
   instance_name=SALES1
   
   

   The following example initSALES2.ora file shows a sample initialization parameter file for the second instance:

   ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
   rollback_segments=(rbs2_1, rbs2_2)
   thread=2
   cluster_database=true
   instance_name=SALES2
   
   

   The following example shows the contents of the initSALES1.ora file for the first instance after embedding the Oracle9i Real Application Clusters Guard parameter files within an existing parameter file. Make sure not to include multiple entries for the same initialization parameter. Because they are included in the embedded parameter files, the THREAD and CLUSTER_DATABASE parameters have been removed.

   ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
   ifile=/u01/oracle/admin/SALES/pfile/init_SALES_nodeA.ora
   ifile=/u01/oracle/admin/SALES/pfile/SALES_config.pfs
   ifile=/u01/oracle/admin/SALES/pfile/SALES_config_nodeA.ded.pfs
   rollback_segments=(rbs1_1, rbs1_2)
   
   

   The following example shows the contents of the initSALES2.ora file for the second instance after embedding the Oracle9i Real Application Clusters Guard parameter files within an existing parameter file. Make sure that you only have single entries for each initialization parameter. Because they are included in the embedded parameter files, the THREAD and CLUSTER_DATABASE parameters have been removed.

   ifile=/u01/oracle/admin/SALES/pfile/initSALES.ora
   ifile=/u01/oracle/admin/SALES/pfile/init_SALES_nodeB.ora
   ifile=/u01/oracle/admin/SALES/pfile/SALES_config.pfs
   ifile=/u01/oracle/admin/SALES/pfile/SALES_config_nodeB.ded.pfs 
   rollback_segments=(rbs2_1, rbs2_2)
   
   

   For more information about these configuration files, refer to Appendix B.

4. Run the catpfs.sql script to create the required Oracle9i Real Application Clusters Guard objects in the database.

   To run this script, you must have SYSDBA privileges. Run the script as follows:

   1. Make sure that all user tables are available.

   2. Change to the $ORACLE_HOME/pfs/admin directory:

      $ cd $ORACLE_HOME/pfs/admin
      
      

   3. Use SQL*Plus to connect to the database as the SYS user and run the catpfs.sql script, where sys_password is the password(for example, CHANGE_ON_INSTALL) :

      $ sqlplus 'SYS/sys_password AS SYSDBA'
      SQL> @catpfs.sql
      
      

      The catpfs.sql script creates the following:

      • Oracle9i Real Application Clusters Guard user

      • CUSTOMER_QUERY package for Oracle Heartbeat Monitor

      • ORAPING_CONFIG and ORAPING_HEARTBEAT tables for Oracle Heartbeat Monitor

      • PFS$ORAPING_CONFIG and PFS$ORAPING_HEARTBEAT views for Oracle Heartbeat Monitor

      • PFS_UP_INSTANCE_NAME tables for the Oracle instance monitor

      The following example shows output from the catpfs.sql script:

      Enter the PFS software owner [Default: OPS$ORACLE]:ops$oracle
      
      Dropping ops$oracle..
      DROP USER ops$oracle CASCADE
                *
      ERROR at line 1:
      ORA-01918: user 'OPS$ORACLE' does not exist
      
      Creating ops$oracle..
      User created.
      
      Grant succeeded.
      
      Below are the list of online tablespaces in this database.
      Decide which tablespace you wish to create the PFS tables and
      indexes.  It is NOT recommended to use the system tablespace
      for storing PFS objects.
      
      TABLESPACE_NAME
      ------------------------------
      INDX
      TEMP
      TOOLS
      USERS
      RBS
      
      Specify ops$oracle user's default tablespace:users
      
      User altered.
      
      Specify ops$oracle user's temporary tablespace:temp
      
      User altered.
      
      Creating Customer Query Package...
      
      Specify owner of the customer query table:scott
      
      Specify customer query table:emp
      
      Connected.
      
      Grant succeeded.
      
      Connected.
      
      Creating synonym for the customer query table...
      Specify synonym for customer query table:emp
      DROP SYNONYM emp
                   *
      ERROR at line 1:
      ORA-01434: private synonym to be dropped does not exist
      
      Synonym created.
      
      Creating CUSTOMER_QUERY package
      
      Package created.
      
      Package body created.
      
      Creating tables and views for Oracle heartbeat monitor.
      DROP PUBLIC SYNONYM pfs$oraping_config
                          *
      ERROR at line 1:
      ORA-01432: public synonym to be dropped does not exist
      
      DROP PUBLIC SYNONYM pfs$oraping_heartbeat
                          *
      ERROR at line 1:
      ORA-01432: public synonym to be dropped does not exist
      
      DROP PUBLIC SYNONYM oraping_heartbeat
                          *
      ERROR at line 1:
      ORA-01432: public synonym to be dropped does not exist
      
      DROP VIEW pfs$oraping_config
      *
      ERROR at line 1:
      ORA-00942: table or view does not exist
      
      DROP VIEW pfs$oraping_heartbeat
      *
      ERROR at line 1:
      ORA-00942: table or view does not exist
      
      DROP TABLE oraping_config
                 *
      ERROR at line 1:
      ORA-00942: table or view does not exist
      
      DROP TABLE oraping_heartbeat
                 *
      ERROR at line 1:
      ORA-00942: table or view does not exist
      
      Table created.
      1 row created.
      
      Commit complete.
      
      Table created.
      
      Table altered.
      1 row created.
      Commit complete.
      View created.
      View created.
      Synonym created.
      Synonym created.
      Synonym created.
      View created.
      View created.
      Creating tables and views for Oracle instance monitor.
      
      Specify instance_name for instance on PFS_HOSTA: prod1
      DROP TABLE pfs_up_prod1
                 *
      ERROR at line 1:
      ORA-00942: table or view does not exist
      
      Table created.
      1 row created.
      
      Specify instance_name for instance on PFS_HOSTB: prod2
      DROP TABLE pfs_up_prod2
                 *
      ERROR at line 1:
      ORA-00942: table or view does not exist
      
      Table created.
      1 row created.
      
      NOTE:
      catpfs complete. Please check catpfs.log for any errors.
      
      

5. To ensure that the Oracle9i Real Application Clusters database is functioning properly, shut down and start up all Oracle instances manually.

   For example, enter the following commands where INIT.ORA_parameter_file is the name of the initialization file as defined by the PFILE variable in the PFS_ORACLE_SERVICE_User.def definition file.

   $ sqlplus "/ as sysdba"
   SQL> STARTUP pfile=INIT.ORA_parameter_file
   
   

   The definition file is located in the $ORACLE_HOME/pfs/DB_NAME/include directory for non-OFA compliant installations and in the $ORACLE_BASE/admin/DB_NAME/pfs/include directory for OFA compliant installations.

Post-Installation Tasks for the root User

Perform the following steps as the root user:

Note: Perform the tasks described in "Post-Installation Tasks for the oracle User" before starting the tasks described in this section.

1. To ensure that the oracle user's environment is available to the root user, log in as the oracle user and enter the following command:

   $ su root
   
   

2. Set the ORACLE_SERVICE and DB_NAME environment variables to the appropriate values.

3. If you have created a database manually, ensure that the system configuration is reflected in the oratab file. The oratab file is located in the /var/opt/oracle directory for Solaris and in the /etc directory for AIX, HP, and Tru64.

   Add an entry for each server instance on the system using the following format:

   DB_NAME:ORACLE_HOME:N
   
   

   In this example N indicates that the database should not be started at reboot time. Always enter the N option so that Oracle9i Real Application Clusters Guard can control startup and shutdown of the database.

4. Change to the $ORACLE_HOME/pfs/setup directory and register the Oracle9i Real Application Clusters Guard Packs with the cluster by running the createpacks script

   Ensure that the DB_NAME, ORACLE_SERVICE, ORACLE_HOME, and if necessary, the ORACLE_BASE environment variables are set correctly before running the script.

   # cd $ORACLE_HOME/pfs/setup
   # ./createpacks
   
   

   Note: Run the createpacks script on only one of the nodes of the cluster.

   Note: For HP 9000 Series HP-UX systems, you must shut down the cluster before running the createpacks script. To shut down the cluster, use the cmhaltcl command.

Starting Oracle9i Real Application Clusters Guard

The Oracle9i Real Application Clusters Guard software is controlled from the command line. To start Oracle9i Real Application Clusters Guard:

1. Log in as the root user.

2. Shut down all listeners associated with the Oracle9i Real Application Clusters Guard database on the cluster.

3. Ensure that the DB_NAME, ORACLE_SERVICE, ORACLE_HOME, and if necessary, the ORACLE_BASE environment variables are set correctly.

4. To enter Oracle9i Real Application Clusters Guard commands, enter the following command:

   # pfsctl
   
   

   See Also: Refer to the Oracle9i Real Application Clusters Guard Concepts and Administration Guide for information about the pfsctl script.

5. Start Oracle9i Real Application Clusters Guard from the PFSCTL prompt:

   PFSCTL> pfsboot
   
   

6. Check the Oracle9i Real Application Clusters Guard packs log file for any errors:
   • For an OFA compliant installation, check the pfs_ORACLE_SERVICE_hostname.log file in the $ORACLE_BASE/admin/db_name/pfs/pfsdump directory.

   • For an non-OFA compliant installation, check the pfs_ORACLE_SERVICE_hostname.log file in the $ORACLE_HOME/pfs/db_name/log/ directory.

7. Check the Oracle Heartbeat Monitor logs for errors:
   • For an OFA installation, check the pfs_ORACLE_SERVICE_hostname_ping.log file in the $ORACLE_BASE/admin/db_name/pfs/pfsdump directory.

   • For an non-OFA installation, check the pfs_ORACLE_SERVICE_hostname_ping.log file in the $ORACLE_HOME/pfs/db_name/log directory.

Troubleshooting

The following notes may help you to troubleshoot problems with Oracle9i Real Application Clusters Guard:

• The PFSCTL status output "Both nodes are part of cluster" does not indicate that both nodes are up and running. One of the nodes might be down. Check the state of a node using the following commands:
  • For Sun Cluster 3.0:

    /usr/cluster/bin/scstat
    
    

  • For HP:

    /usr/sbin/cmviewcl
    
    

  • For Tru64:

    /usr/bin/caa_stat
    
    

  • For AIX:

    /usr/es/sbin/cluster/clstat
    
    

• The following parameters are not used by Oracle9i Real Application Clusters Guard in Sun Cluster 3.0, but must be specified for compatibility:
  • START_NET_TIMEOUT

  • STOP_NET_TIMEOUT

  • PFS_NET_IF_A *

  • PFS_NET_IF_B *

  * Specify the actual network interface adapter (that is, hme0) for PFS_NET_IF_A and PFS_NET_IF_B, not the NAFO group.

• If you have problems with NAFO on Sun Solaris, note the following:
  • If no NAFO group exists, the system attempts to discover a network adapter on the subnet identified by the hostnames, and create single adapter NAFO groups.

  • If you want multiple net adapters as backups, get and use the adapter lists on the subnet identified by the hostnames, and read the "How to Configure Public Network Management (PNM)" chapter in the Sun Cluster 3.0 Installation Guide.

  • To check the status of the NAFO groups, enter the following command:

    $ /usr/cluster/bin/pnmstat -l 
    
    

    The output might look similar to the following:

       group   adapters        status  fo_time act_adp 
       nafo0   hme0            OK      NEVER   hme0 
    
    

  For further information on NAFO groups please refer to the Sun Cluster documentation or contact Sun support.

• If both the nodes of the cluster simultaneously fail, the Oracle Real Application Clusters Guard Packs start automatically when the nodes reboot. Enter the following command as the root user to stop the resources in the install environment:

     # cd $ORACLE_HOME/pfs/bin 
     # pfsctl 
     PFSCTL>pfshalt 
  
  

  Note: This problem can occur any time all nodes are stopped without first stopping the Oracle9i Real Application Clusters Guard Packs using pfsctl. For example, if you perform a Sun Clusters shutdown, which stops all nodes cleanly, it does not run pfsctl and stop the packs. When you later boot a node, the Oracle9i Real Application Clusters Guard Pack is restarted automatically.

• The following Oracle9i Real Application Clusters Guard error might be displayed because of inconsistencies between SC2.2 and SC3.0:

  Alert: could not generate file properly - Packs files 
  
  

  If it appears, remove all the files from the $ORACLE_HOME/pfs/setup/output/ORACLE_SERVICE/packs directory and reconfigure Oracle9i Real Application Clusters Guard.

• When using the OFA architecture, ensure any user-specific configuration files for Real Application Clusters Guard are backed up and removed, so thatthey do not conflict with the new Real Application Clusters Guard files.