Oracle9i Data Guard Concepts and Administration Release 2 (9.2) Part Number A96653-01 |
|
This chapter describes Oracle initialization parameters for Oracle instances, including the primary database and each standby database in a Data Guard configuration.
All initialization parameters are either contained in an initialization file, the name of which is a variation of init.ora
depending on your operating system, or a server parameter file (SPFILE). As an alternative to specifying parameters in the initialization file or if you are using an SPFILE, you can modify dynamic parameters at runtime using the ALTER SYSTEM SET
or ALTER SESSION SET
statements.
See Also:
Oracle9i Database Reference and your Oracle operating system-specific documentation for more information about setting initialization parameters |
Table 11-1 shows the initialization parameters that affect instances in a Data Guard environment. Some parameters are directly related to Data Guard, while others have additional implications when the instance is part of a Data Guard environment.
Each parameter description indicates whether the parameter applies to the primary database role, the standby database role, or both. For parameters that apply to the standby database role, most of the parameters pertain to both physical and logical standby databases. Any differences are noted in the table descriptions.
Parameter | Description | For More Information |
---|---|---|
|
Applies to the primary database role. Limits the amount of data that can be lost and effectively increases the availability of the standby database by forcing a log switch after the amount of time you specify (in seconds) elapses. That way, the standby database will not miss redo logs generated from a time range longer than a value of the |
|
|
Applies to the primary database and standby database roles. Set to 9.0.0.0.0 or higher to use the Data Guard broker, logical standby databases, and the enhanced features of physical standby databases. Always set this parameter to the same value on the primary database and standby databases. If the values differ, you may not be able to archive the redo logs from your primary database to the standby database. |
|
|
Applies to the primary database and standby database roles. Prevents reusing archived redo log control file information for a specified period of time. |
See Section 5.5.1.3 |
|
Applies to the primary database and standby database roles. Uniquely names the database control file. Always set this parameter on the standby database to a different value from the |
|
|
Applies to the physical standby database role. Set this parameter to distinguish standby datafile filenames from primary datafile filenames. Because the standby database control file is a copy of the primary database control file, you must convert the standby database filenames if the standby database is on the same system as the primary database or on a separate system using different path names. This parameter must be set for all physical standby databases that share the same site as the primary database or use different path names. |
See Section 6.3.4 |
|
Applies to the primary database and standby database roles. Specifies the maximum number of database files that can be open for this database. |
|
|
Applies to the primary database and standby database roles. Specifies a database identifier of up to eight characters. For physical standby databases, set it to the same value in the standby and primary database initialization files. For logical standby databases, set it using the DBNEWID (nid) utility, as specified in Section 4.2. |
|
|
Applies to the physical standby database in managed recovery mode. Assigns the FAL (fetch archive log) client name used by the FAL server to refer to the FAL client. This is the Oracle Net service name that the FAL server should use to refer to the standby database. This parameter is set on the standby site. This parameter is not used with logical standby databases. |
See Section 6.5 |
|
Applies to the physical standby database in managed recovery mode. Assigns the Oracle Net service name that the standby database should use to connect to the FAL server. This parameter is set on the standby site. This parameter is not used with logical standby databases. |
See Section 6.5 |
|
Applies to the primary database and standby database roles. Specifies the name space that the distributed lock manager (DLM) uses to generate lock names. Set this parameter if the standby database has the same name as the primary database and is on the same system or cluster. Note: When multiple (primary or standby) databases with the same database name (DBNAME) are configured on the same system, you must set this initialization parameter to a unique value on each database. |
|
|
Applies to the primary database and standby database roles. Defines a destination and attributes for the log transport services. |
See Section 5.3.1.1 |
|
Applies to the primary database and standby database roles. Specifies the state of the destination specified by the Possible attributes are:
|
See Section 5.3.1.2 |
|
Applies to the primary database and standby database roles. Indicates the format for log filenames.
|
See Section 5.5.2.7 and Section 5.8.4.5 |
|
Applies to the primary database and standby database roles. Specifies the number of archiver processes to be invoked. This value is evaluated at instance startup if the |
|
|
Applies to the primary database and standby database roles. Defines the minimum number of destinations that must succeed in order for the online log file on the primary database to be available for reuse. |
See Section 5.5.2.4 |
|
Applies to the primary database and standby database roles. Enables automatic archiving of filled groups when |
|
|
Applies to the primary database and standby database roles. Optionally, set this parameter to an integer value to see the progression of the archiving of redo logs to the standby site. The Oracle database server writes an audit trail of the redo logs received from the primary database into a trace file. This parameter controls output generated by the ARCn, LGWR, and foreground processes on the primary database, and the RFS and FAL server processes on the standby database. |
See Section 6.4.8 |
|
Applies to the physical standby database role. Distinguishes the redo log filenames on the standby database from primary database redo log filenames. The parameter value converts the filename of a new log file on the primary database to the filename of a log file on the standby database. Adding a log file to the primary database necessitates adding a corresponding file to the standby database. When the standby database is updated, this parameter is used to convert the log filename from the primary database to the log filename on the standby database. This parameter is necessary if the standby database is on the same system as the primary database or on a separate system that uses different path names. |
See Section 6.3.4 |
|
Applies to the logical standby database role only. Specifies the level of concurrency for redo allocation. Set this value to 1, which is the default. |
|
|
Applies to the primary database and logical standby database roles. Log apply services use parallel query processes to perform processing, and use parallel apply algorithms to maintain a high level of database apply performance. A minimum of 5 parallel query processes is required for a logical standby database. Thus, the value of the This parameter specifies the maximum number of parallel servers working on log apply services on the logical standby database. This parameter is not used with physical standby databases. |
|
|
Applies to the primary database and standby database roles. Set this parameter to Set this parameter to To independently enable and disable the sending and receiving of remote archived redo logs, use the
The |
See Section 5.5.2 |
|
Set on the primary database and logical standby databases. Log apply services of logical standby databases use shared pool system global area (SGA) to stage the information read from the redo logs. The more SGA that is available, the more information that can be staged. By default, one quarter of the value set for the |
See Oracle9i Database Reference and Oracle9i Supplied PL/SQL Packages and Types Reference |
|
Applies to the primary database and standby database roles. Set this parameter to execute the |
See Section 6.3.6.3 |
|
Applies to the standby database role. Used by a standby database to determine the archive location of online redo logs received from the primary database. The RFS process uses this value in conjunction with the
|
See Section 5.5.2.7 and Section 5.8.4.5 |
|
Applies to the primary database and standby database roles. When set to Use this parameter with the |
See Section 6.3.4 |
|
Applies to the primary database and standby database roles. Determines the location of trace files for a database. |
|
Copyright © 1999, 2002 Oracle Corporation. All Rights Reserved. |
|