Oracle Post-installation Tasks
Post-Installation Tasks for the oracle User
To avoid interference 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, append the files generated by the PFSSETUP utility to the current Net Services configuration files.
Perform the following steps as the oracle user:
- Log in as the Oracle software owner, typically, the oracle user.
- 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:
Filename Description listener.ora.ded.pfs Dedicated configuration (IS_MTS is set to false) file for the listeners that identifies the Oracle9i Real Application Clusters Guard listener name and service it is listening for. listener.ora.mts.pfs Shared Servers configuration (IS_MTS is set to true) file for the listeners that identifies the Oracle9i Real Application Clusters Guard listener name and service it is listening for. tnsnames.ora.ded.pfs Dedicated configuration (IS_MTS is set to false) file that contains net service names mapped to connect descriptors. tnsnames.ora.mts.pfs Shared Servers configuration (IS_MTS is set to true) file that contains net service names mapped to connect descriptors. tnsnames.ora.ded.clnt.pfs Dedicated client configuration (IS_MTS is set to false) file that contains net service names mapped to connect descriptors. tnsnames.ora.mts.clnt.pfs Shared Servers client configuration (IS_MTS is set to true) file that contains net service names mapped to connect descriptors. The files in the preceeding table are created in the $TNS_ADMIN directory if TNS_ADMIN is defined, or in the $ORACLE_HOME/network/admin directory if TNS_ADMIN is not defined.
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.oraCopy the client configuration file, tnsnames.ora.ded.clnt.pfs, to all of the client systems.
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.
- Set up the oracle instance parameter files for Oracle9i Real Application Clusters Guard.
During the Oracle9i Real Application Clusters Guard setup, the following instance 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 if running Shared Servers. ORACLE_SERVICE_config_HOSTA.ded.pfs Host A configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings for non Shared Servers environments. ORACLE_SERVICE_config_HOSTB.mts.pfs Host B configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings if running Shared Servers. ORACLE_SERVICE_config_HOSTB.ded.pfs Host B configuration parameter file containing required Oracle9i Real Application Clusters Guard parameter settings for non Shared Servers environments. 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 shows sample initialization parameter files for the first instance:
initsales1.ora: ifile=/u01/oracle/admin/sales/pfile/initsales.ora rollback_segments=(rbs1_1, rbs1_2) thread=1 cluster_database=true instance_name=sales1The following example shows sample initialization parameter files for the second instance:
initsales2.ora: ifile=/u01/oracle/admin/sales/pfile/initsales.ora rollback_segments=(rbs2_1, rbs2_2) thread=2 cluster_database=true instance_name=sales2The following example shows the contents of the initsid.ora files 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 following parameters have been removed thread, parallel_server, cluster_database.
initsales1.ora 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 initsid.ora files for the second 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 following parameters have been removed thread, parallel_server, cluster_database: initsales2.ora 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.
- Run the catpfs.sql script to create the required Oracle9i Real Application Clusters Guard objects in the database, as follows:
- Make sure all user tables are available.
- Change to the $ORACLE_HOME/pfs/admin directory:
$ cd $ORACLE_HOME/pfs/admin- Connect using SQL*Plus as the SYS user and run the catpfs.sql script:
$ sqlplus `SYS/CHANGE_ON_INSTALL AS SYSDBA' SQL> @catpfs.sqlThe following is sample output from running the catpfs.sql script:
Enter the PFS software owner [Default: OPS$ORACLE]:ops$oracle Dropping ops$oracle.. DROP USER ops$oracleCASCADE * 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.- To ensure the Oracle9i Real Application Clusters database is functioning properly, shutdown and startup all oracle instances manually before starting the Oracle9i Real Application Clusters Guard Packs.
Post-Installation Tasks for the root User
Perform the following steps as the root user:
Perform the tasks described in "Post-Installation Tasks for the oracle User" before attempting the tasks described in this section.
- 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- Set the ORACLE_SERVICE and DB_NAME environment variables.
- If you have created a database manually, ensure that the system configuration is reflected in the oratab file.
Add an entry for each server instance on the system in the following format:
DB_NAME:ORACLE_HOME:{Y|N}where Y or N indicates whether you want to activate the dbstart and dbshut scripts. Always enter the N option so that Oracle9i Real Application Clusters Guard can control startup and shutdown of the database.
- Change to the $ORACLE_HOME/pfs/setup directory and run the pfsroot_ORACLE_SERVICE.sh script on each node of the cluster.
- 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:
# cd $ORACLE_HOME/pfs/setup" # ./createpacks
Run the createpacks script on only one of the nodes of the cluster.
Starting Oracle9i Real Application Clusters Guard
To start the Oracle9i Real Application Clusters Guard, perform the following:
- Log in as the root user.
- Shut down all listeners associated with the Oracle9i Real Application Clusters Guard database on the cluster.
- Ensure that the ORACLE_SERVICE and DB_NAME environment variables are set correctly.
- The Oracle9i Real Application Clusters Guard software is controlled from the command line. To enter Oracle9i Real Application Clusters Guard commands, enter the following command as the root user:
# pfsctl- Start Oracle9i Real Application Clusters Guard from the PFSCTL prompt:
PFSCTL> pfsboot- Check the Oracle9i Real Application Clusters Guard packs log for any errors.
- For an OFA installation check pfs_ORACLE_SERVICE_hostname.log in the $ORACLE_BASE/admin/db_name/pfs/pfsdump directory.
- For an non-OFA installation check pfs_ORACLE_SERVICE_hostname.log in the $ORACLE_HOME/pfs/db_name/log/ directory.
- Check the Oracle Heartbeat Monitor logs for errors.
- For an OFA installation check pfs_ORACLE_SERVICE_hostname_ping.log in the $PFS_HOME/pfsdump directory.
- For an non-OFA installation check pfs_ORACLE_SERVICE_hostname_ping.log in the $PFS_HOME/log directory.