This chapter describes server parameter file (SPFILE) placement and configuration in Real Application Clusters (RAC) environments. This chapter contains the following:
Migrating to the Server Parameter File in Real Application Clusters Environments
Server Parameter File Errors in Real Application Clusters
See Also:
The Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide for more information about parameters and for a discussion of parallel execution-related parameters in RAC data warehouse environmentsOracle Database 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 filesBy 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. Do not try to edit this file manually.
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 Database release, then create and configure the server parameter file for RAC using the procedures described in the following section.
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 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'
The variable dbunique_name
is the unique database name, and the variable 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, start DBCA. When the Initialization Parameters page appears, select Create server parameter file (SPFILE) under the File Locations tab. This option is visible only if you are using raw storage. When you have made this selection, then enter either a shared file system filename, or enter the raw device path name in the Server Parameters Filename
field.
Note:
When you use DBCA to create the server parameter file, the defaultPFILE
file name is $ORACLE_HOME/dbs/init$ORACLE_
sid
.ora
.Oracle Database searches for your parameter file in the following order:
$ORACLE_HOME/dbs/spfilesid.ora
$ORACLE_HOME/dbs/spfile.ora
$ORACLE_HOME/dbs/initsid.ora
Migrate to the server parameter file by creating and editing the server parameter file using the procedures described in this section.
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 5 MB in size.
Migrate to the server parameter file (SPFILE) file by completing the following procedures:
Combine the initialization parameter files for all instances into one init
dbname
.ora
file by copying all shared IFILE contents as is. All parameters defined in your IFILE parameter files are global. Therefore, create them in the format parameter=value, without system identifier (sid) prefixes.
Copy all instance-specific parameter definitions from init
sid
.ora
files using the following syntax, where the variable sid
is the system identifier (SID) of the instance:
sid.parameter=value
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 init
dbname
.ora
file that you created by merging your IFILEs, and then transfer the settings for the parameters from the merged file into your server parameter file.
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 init
sid
.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 Database uses the server parameter file entry specified in the file init
sid
.ora
.
Note:
theSPFILE
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.Oracle Database 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:
Shut down the instance, recover the server parameter file, and restart the instance.
Enable the instance to continue running without regard for subsequent parameter updates.
Oracle Database displays errors for parameter changes that you attempt when you incorrectly use the ALTER SYSTEM SET
statement. Oracle Database 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