Skip Headers
Oracle® Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide
10g Release 2 (10.2) for AIX

Part Number B14201-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Feedback

Go to previous page
Previous
Go to next page
Next
View PDF

8 Configuring the Server Parameter File in Oracle Real Application Clusters Environments

This chapter describes server parameter file (SPFILE) placement and configuration in Real Application Clusters (RAC) environments. The topics in this chapter are:

8.1 Parameter Files and Real Application Clusters

Oracle uses parameter settings in parameter files to determine how to control various database resources. You can use two types of files for parameter administration: the server parameter file (SPFILE) or one or more traditional client-side parameter files.

Oracle recommends that you manage parameters using an SPFILE. If you use client-side parameter files, then Oracle does not preserve parameter changes made for self-tuning after shutdown.


See Also:

Oracle Database 10g Real Application Clusters documentation for more information about using client-side parameter files

8.2 Using Server Parameter Files in Real Application Clusters

By default, Oracle creates the server parameter file based on one SPFILE. You can change parameter settings in the server parameter file only by using Oracle Enterprise Manager or ALTER SYSTEM SET SQL statements; the server parameter file is a binary file that you should not edit.


Note:

Oracle recommends that you avoid modifying the values for self-tuning parameters; overriding these settings can adversely affect performance.

If you are upgrading from a previous Oracle release, then create and configure the server parameter file for RAC using the procedures described in the following section.

8.2.1 Location of The Server Parameter File

The default location of the server parameter file (SPFILE) when the database creates it from a PFILE is platform-dependent.

The default location of the server parameter file is:

$ORACLE_HOME/dbs/spfile$ORACLE_sid.ora 

The default location of the server parameter file is inappropriate for RAC databases and ASM instances if you use raw devices, because all instances must use the same server parameter file.

Instead, Oracle recommends that you use a PFILE in this directory:

$ORACLE_HOME/dbs/init$ORACLE_sid.ora

This path is valid for each instance and it refers to a single, shared initialization parameter file. If you use raw storage, then the file must contain the following entry where n is a numeric value:

SPFILE='/dev/rlracclvn

However, if you use a cluster file system, then use one of the following file location:

  • SPFILE='$ORACLE_HOME/dbs/spfile.ora'
    
    

If you use ASM, then the SPFILE value will be:

SPFILE='+disk_group_name/dbunique_name/spfiledbname.ora'

where dbunique_name is the unique database name and dbname is the database name.

You must use the same value of SPFILE so that all instances use the same server parameter file at startup.

To use DBCA to create your database and to use the server parameter file, on the Initialization Parameters page select Create server parameter file (SPFILE) under the File Locations tab which is visible only if you are using raw storage. Then enter either a shared file system filename or the raw device path name in the Server Parameters Filename field.


Note:

When you use DBCA to create the server parameter file, the default PFILE file name is $ORACLE_HOME/dbs/init$ORACLE_sid.ora.

8.3 Parameter File Search Order in Real Application Clusters

Oracle searches for your parameter file in the following order:

  1. $ORACLE_HOME/dbs/spfilesid.ora

  2. $ORACLE_HOME/dbs/spfile.ora

  3. $ORACLE_HOME/dbs/initsid.ora

8.4 Migrating to the Server Parameter File in Real Application Clusters Environments

Migrate to the server parameter file by creating and editing the server parameter file using the procedures described in this section.

8.4.1 Server Parameter File Placement in Real Application Clusters

For single-node cluster-enabled configurations, or if you are using ASM disk groups or a cluster file system, place the server parameter file in an ASM disk group or on a file system. Otherwise, place the server parameter file on a shared raw device that is at least 5MB in size.

8.4.2 Procedures for Migrating to the Server Parameter File

Migrate to the server parameter file (SPFILE) file by completing the following procedures:

  1. Combine the initialization parameter files for all instances into one initdbname.ora file by copying all shared IFILE contents as is. All parameters defined in your IFILE parameter files are global. Therefore, create them as "parameter=value" without system identifier (sid) prefixes.

  2. Copy all instance-specific parameter definitions from initsid.ora files using the following syntax, where the variable sid is the system identifier (SID) of the instance:

    sid.parameter=value 
    
  3. If you are using a cluster file system, then create the server parameter file using the CREATE SPFILE statement as in the following example:

    CREATE SPFILE='?/dbs/spfile_dbname.ora'
    FROM PFILE='?/dbs/initdbname.ora'
    
    

    If you use ASM, then use the following syntax to create the server parameter file:

    CREATE SPFILE='+disk_group_name/db_uniquename/spfiledbname.ora'
    FROM PFILE='?/dbs/initdbname.ora'
    
    

    If you use raw storage, then use the following syntax to create the server parameter file on a raw device where n is a numeric value:

    CREATE SPFILE='/dev/rlracclvn
    FROM PFILE='?/dbs/initdbname.ora'
    
    

    These statements read your combined initdbname.ora file that you created by merging your IFILEs. Then it transfers the settings for the parameters from the merged file into your server parameter file.

  4. Oracle recommends that you use the SPFILE by using the PFILE as a pointer to the SPFILE. Do this by running the STARTUP command as in the following example, where the SID variable sid in the file initsid.ora is the SID that you use in the SPFILE entry from Step 3. For example:

    STARTUP PFILE=$ORACLE_HOME/dbs/initsid.ora
    
    

    If you use this STARTUP command syntax, then Oracle uses the server parameter file entry specified in initsid.ora.


    Note:

    the SPFILE for ASM instance cannot be stored in ASM, as it is used to start the ASM instance. You can place an ASM instance SPFILE on a shared raw device or in a cluster file system for ASM, or you can have a traditional client-side parameter file for each ASM instance.

8.5 Server Parameter File Errors in Real Application Clusters

Oracle reports errors that occur during server parameter file creation or while reading the file during startup. If an error occurs during a parameter update, then Oracle records the error in your ALERT.LOG file and ignores subsequent parameter updates to the file. If this happens, then do either of the following:

Oracle displays errors for parameter changes that you attempt when you incorrectly use the ALTER SYSTEM SET statement. Oracle does this when an error occurs while reading from or writing to the server parameter file.


See Also:

The Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide for more information about backing up the SPFILE