Oracle9i Data Guard Concepts and Administration Release 1 (9.0.1) Part Number A88808-01 |
|
This chapter describes Oracle initialization parameters for each Oracle instance, including the primary database and each standby database in the Data Guard environment.
The members of a standby configuration are transactionally consistent copies of the primary member. The remote archival functionality of the standby feature provides the mechanism by which the redo log files of the primary database are transported to the designated standby sites. Redo logs generated by the primary database are transported and applied to the standby databases.
All initialization parameters are contained in an initialization file, the name of which is a variation of init.ora
depending on your operating system. As an alternative to specifying parameters in the initialization file, 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 7-1 shows all of the initialization parameters that you need to implement a Data Guard environment. It describes whether a parameter applies to the primary database role, the standby database role, or both.
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 and standby database roles.
Always set the same value at the primary and standby databases. If different, you may not be able to archive the redo logs from your primary database to the standby database. |
|
|
Applies to the primary and standby database roles.
Uniquely names the database control file. Always set this parameter to a different value from the |
|
|
Applies to the standby database role. Prevents reusing archived redo logs for a specified period of days.
Setting this parameter prevents the |
See Section 3.4.1.3 |
|
Applies to the standby database role. Set to distinguish standby datafile filenames from primary datafile filenames. This parameter must be set on all standby databases. |
See Section 4.6 |
|
Applies to the primary and standby database roles. Specifies the maximum number of database files that can be open for this database. |
|
|
Applies to the primary and standby database roles. Specifies a database identifier of up to 8 characters. Set it to the same value in the standby and primary initialization files. |
|
|
Applies to the standby database role. 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 used by the primary database to refer to the standby database. |
See Section 4.5 |
|
Applies to the standby database role. Assigns the FAL (fetch archive log) server for the standby database. |
See Section 4.5 |
|
Applies to the standby database role. Specifies the name space that the distributed lock manager (DLM) uses to generate lock names. Set this value if the standby database has the same name on the same cluster as the primary database. |
|
|
Applies to the standby database role. Specifies the location of the archived logs for a standby database in recovery mode. |
See Section 3.6.3.4 |
|
Applies to the primary and standby database roles. Defines a destination and attributes for the archived redo log file group. |
See Section 3.3.1.1 |
|
Applies to the primary and standby database roles.
Specifies the state of the destination specified by the |
See Section 3.3.1.2 |
|
Applies to the primary and standby database roles. Indicates the format for filenames of log files.
|
See Section 3.6.3.4 |
|
Applies to the primary 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 and standby database roles. Defines the minimum number of destinations that must succeed in order for the online log file to be available for reuse. |
See Section 3.4.2.4 |
|
Applies to the primary and standby database roles.
Enables automatic archiving of filled groups each time an instance is started when |
|
|
Applies to the primary 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 archived logs received from the primary database into a trace file. |
See Section 4.9.5 |
|
Applies to the standby database role. Set to make your standby redo log filenames distinguishable 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. |
See Section 4.6 |
|
Applies to the primary and standby database roles.
Always set this parameter to |
See Section 3.4.2 |
|
Applies to the primary and standby database roles.
Set this parameter to execute the |
See Section 4.8.3 |
|
Applies to the standby database role. Defines the standby database destination for the archived redo log file group.
|
See Section 3.6.3.4 |
|
Applies to the primary and standby database roles.
When set to
Use this parameter with the |
See Section 4.6 |
|
Applies to the primary and standby database roles. Determines the location of trace files for a database. |
See Section 4.9.5 |
|
Copyright © 1996-2001, Oracle Corporation. All Rights Reserved. |
|