| Oracle® Data Guard Broker 10g Release 1 (10.1) Part Number B10822-01 |
|
|
View PDF |
| Oracle® Data Guard Broker 10g Release 1 (10.1) Part Number B10822-01 |
|
|
View PDF |
Database properties help you to view and control the behavior of databases, log transport services, and log apply services in a broker configuration. This chapter provides the following sections about the monitorable and configurable properties:
The scope of some properties is said to be database-wide. If the database (primary or standby) is a RAC database consisting of multiple instances, the value of such a property applies uniformly across all of the instances sharing that database. The scope of other properties is said to be instance-specific. Such a property exists for all instances of the RAC database, but its value may differ from one specific instance to another.
|
Note: This chapter presents properties primarily from the point of view of the DGMGRL CLI. Using the CLI, the properties described in this chapter may be viewed or modified using discrete CLI commands.The Data Guard GUI explicitly presents some of these properties on the Edit Properties page. Information from other properties may be implicitly incorporated into other pages displayed by the GUI. Each property's description in this chapter indicates how the GUI presents that property to the user. |
Monitorable properties allow you to view information related to the database or the instance, but you cannot change the values of these properties. You can view all of the monitorable properties using CLI SHOW commands.
|
Note: Information for monitorable properties can be seen only when broker management of the database is enabled and the database is in an online state. The Data Guard GUI displays the information obtained from these properties on the Property page. |
If the database is a RAC database, the output values of some properties may also show instance-specific information. For example if the primary database is a RAC database, LogXptStatus may show Instance1 transmitting redo data to Standby2 has an error and Instance2 transmitting redo data to Standby4 has an error.
The following sections describe the database monitorable properties:
InconsistentLogXptProps (Inconsistent Log Transport Properties)
LsbyFailedTxnInfo (Logical Standby Failed Transaction Information)
The InconsistentLogXptProps property returns a table that shows all properties related to log transport services whose values are inconsistent between the broker configuration file and the runtime value in the database.
The properties reported in this table can be either database-specific properties or instance-specific properties. A database-specific property only ensures that there is one value in the broker's configuration file for all instances sharing the database, but the runtime values among the instances can be different. This means that a database-specific property may be inconsistent only on some instances.
This property pertains to the primary database. The table contains the following columns:
INSTANCE_NAME
The value matching the SID for the instance.
STANDBY_NAME
The database unique name (DB_UNIQUE_NAME) of the standby database to which this log transport services property pertains.
PROPERTY_NAME
The name of the log transport services property with an inconsistent value.
MEMORY_VALUE
The runtime value being used in the database.
BROKER_VALUE
The value of the log transport services property saved in the broker configuration file.
The InconsistentProperties property returns a table that shows all database properties whose values contained in the broker configuration file are inconsistent with the values in the corresponding server parameter file or the runtime values in the database.
The properties reported in this table can be either database-specific properties or instance-specific properties. A database-specific property only ensures that there is one value in the broker's configuration file for all instances sharing the database, but the runtime memory values or SPFILE values among the instances can be different. This means that a database-specific property may be inconsistent only on some instances.
Each individual database has this property. The table contains the following columns:
INSTANCE_NAME
The value matching the SID for the instance.
PROPERTY_NAME
The name of the database property with the inconsistent value.
MEMORY_VALUE
The corresponding runtime value being used in the database.
SPFILE_VALUE
The corresponding value saved in the server parameter file (SPFILE).
BROKER_VALUE
The value of the database property saved in the broker configuration file.
Specifies the last 20 lines in the Data Guard broker log file of the specified instance. The LatestLog property is an instance level monitorable property. The table name is the full path of the Data Guard broker log file on the host on which the instance is running. Each instance in the configuration has this property. The table contains the following columns in the order shown:
Line No.
The line number of the log in the Data Guard broker log file.
Timestamp
The time when the log is generated.
LogText
The detailed text of the log.
For example, the following example shows output from a SHOW INSTANCE command:
DGMGRL> SHOW INSTANCE sales1 'LatestLog' /home/oracle10g/log/drcsales1.log
Line No. Timestamp Log Text
431 2003-06-09-15:51:28 DMON: Entered rfm_release_chief_lock for CTL_GET_STATUS
432 2003-06-09-15:51:28 DMON: Releasing lock
433 2003-06-09-15:52:18 DMON: ENUM_DRC: success. (len = 610)
434 2003-06-09-15:52:18 DMON: ENUM_DRC operation completed
435 2003-06-09-15:52:27 DMON: Entered rfm_get_chief_lock() for CTL_GET_STATUS, reason 0
436 2003-06-09-15:52:27 DMON: acquiring lock 105 in 5 mode
437 2003-06-09-15:52:27 DMON: chief lock convert for healthcheck
438 2003-06-09-15:52:27 DMON: status from rfi_post_instances() = ORA-00000
439 2003-06-09-15:52:27 INSV: message for req_id 1.1.496252113, opcode CTL_GET_STATUS, phase 1, flags 5
440 2003-06-09-15:52:27 DMON: Entered rfmhcexinst
441 2003-06-09-15:52:27 DMON: rfmhcexinst calling RSMs
442 2003-06-09-15:52:28 DMON: Setting db status after H/C aggregation
443 2003-06-09-15:52:28 INSV: message for req_id 1.1.496252113, opcode CTL_GET_STATUS, phase 5, flags 5
444 2003-06-09-15:52:28 DMON: Setting db status after H/C aggregation
445 2003-06-09-15:52:28 INSV: message for req_id 1.1.496252113, opcode CTL_GET_STATUS, phase 3, flags 65541
446 2003-06-09-15:52:28 DMON: Entered rfm_release_chief_lock for CTL_GET_STATUS
447 2003-06-09-15:52:28 DMON: Releasing lock
448 2003-06-09-15:52:43 DMON: ENUM_DRC: success. (len = 610)
449 2003-06-09-15:52:43 DMON: ENUM_DRC operation completed
450 2003-06-09-15:52:43 RSM 0 received GETPROP request: rid=0x01010001, pid=11
This property supplants the obsolete SHOW LOG command in Oracle 9iR2.
The LogXptStatus property returns a table that contains the error status of log transport services for each of the enabled standby databases. This property pertains to the primary database.
The table contains the following columns:
PRIMARY_INSTANCE_NAME
The value matching the SID for the instance on the primary database.
STANDBY_DATABASE_NAME
The database unique name (DB_UNIQUE_NAME) of the standby database.
ERROR
The text of the log transport error. If there is no error, the field is empty.
Each entry in the table indicates the status of log transport services on one primary instance to one standby database.
The format of the error status is as follows:
"standby1_sitename=error_status, standby2_sitename=error_status,..."
The error status can be an empty string, which indicates there is no error.
In the following example, the STATUS from DR_Sales is empty because there is no error for the DR_Sales destination. The South_Report destination returned the ORA-01034 message.
DGMGRL> SHOW DATABASE 'North_Sales' 'LogXptStatus' ;
LOG TRANSPORT STATUS
PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
sales1 DR_Sales
sales1 South_Report ORA-01034: ORACLE not available
The LsbyFailedTxnInfo property identifies a failed transaction that caused log apply services to stop. This property contains a string with the following values from the DBA_LOGSTDBY_EVENTS view:
XIDUSN: Transaction ID undo segment number
XIDSLT: Transaction ID slot number
XIDSQN: Transaction ID sequence number
STATUS_CODE: Status (or Oracle error code) belonging to the STATUS message
STATUS: Description of the current activity of the process or the reason why log apply services stopped
The transaction IDs and status information are separated by a string of number signs (###). This property pertains to a logical standby database.
The LsbyParameters property contains a string that identifies the value of MAX_SGA (maximum system global area) and MAX_SERVERS (maximum number of parallel query servers) specifically reserved for log apply services. These values are separated by a string of number signs (###) in the LsbyParameters property.
This property pertains to a logical standby database.
The LsbySkipTable property lists the logical apply skip specifications. These skip specifications specify filters for log apply services to skip applying a certain class of online redo log files on the logical standby database. This property returns a table with the following columns from the DBA_LOGSTDBY_SKIP view:
ERROR
Indicates if the statement should be skipped (Y) or if errors should be returned for the statement (N)
STATEMENT_OPT
Indicates the type of statement that should be skipped
SCHEMA
The schema name for which this skip option should be used
NAME
Name of the object for which this skip option should be used
PROCEDURE
Name of the stored procedure to execute when processing the skip option
The LsbySkipTxnTable lists the skip settings chosen. This property returns a table with following columns:
XIDUSN: Transaction ID undo segment number
XIDSLT: Transaction ID slot number
XIDSQN: Transaction ID sequence number
ACTIVE: Description of the current activity of the process or the reason why log apply services stopped
This property pertains to a logical standby database.
The RecvQEntries property returns a table indicating all log files that were received by the standby database but have not yet been applied. If no rows are returned, it implies all log files received have been applied. This property pertains to a standby database.
The table contains the following columns in the order shown:
STATUS
The STATUS column is set to one of the following values for a log file on a logical standby database:
NOT_APPLIED: No redo records in this log file have been applied.
PARTIALLY_APPLIED: Some of the redo records in this log file have been applied while others have not.
COMMITTED_TRANSACTIONS_APPLIED: This status value only applies to a logical standby database. All redo records belonging to the committed transactions have been applied. Redo records belonging to uncommitted transactions have not been read by logminer and may still be needed when the transactions are committed in the future. Therefore, it is not safe yet to discard this online redo log file.
RESETLOGS_ID
Resetlogs identifier associated with the archived redo log file
THREAD
The redo thread number
LOG_SEQ
The online redo log file sequence number
TIME_GENERATED
The first time when the online redo log file was written to the primary database
TIME_COMPLETED
The next time when the log file was archived on the primary database (corresponds to the NEXT_CHANGE# column)
FIRST_CHANGE#
First change number in the archived redo log file
NEXT_CHANGE#
First change in the next log file
SIZE (KBs)
The SIZE of the online redo log file in kilobytes
For example:
DGMGRL> SHOW DATABASE 'DR_Sales' 'RecvQEntries' ;
STATUS RESETLOGS_ID THREAD
LOG_SEQ TIME_GENERATED TIME_COMPLETED FIRST_CHANGE#
NEXT_CHANGE# SIZE (KBs)
NOT_APPLIED 497198843 1 5
06/20/2003 14:55:38 06/20/2003 16:31:26 202138
210718 7364
NOT_APPLIED 497198843 1 6
06/20/2003 16:31:26 06/20/2003 16:31:39 210718
210753 13
NOT_APPLIED 497198843 1 7
06/20/2003 16:31:39 06/20/2003 16:31:54 210753
210758 1
NOT_APPLIED 497198843 1 8
06/20/2003 16:31:54 06/20/2003 16:31:59 210758
210789 11
|
Note: In the Data Guard GUI, this information is displayed on the Log File Details page. |
The SendQEntries property returns a table that shows all log files on the primary database that were not successfully archived to one or more standby databases. This property pertains to the primary database.
The table contains the following columns:
STANDBY_NAME
The value can be empty or it can contain the database unique name (DB_UNIQUE_NAME) of the standby database. If empty, the STATUS column will contain a value of CURRENT or NOT_ARCHIVED.
STATUS
The STATUS column is set to one of the following values:
CURRENT: A log file to which online redo is currently being written.
NOT_ARCHIVED: A completed online redo log file that has not been archived locally.
ARCHIVED: A completed log file that has been archived locally but has not been transmitted to the standby database specified in the STANDBY_NAME column.
The table contains exactly one row with the value of STATUS=CURRENT. There can be multiple rows with the value STATUS=ARCHIVED or STATUS=NOT_ARCHIVED.
RESETLOGS_ID
Resetlogs identifier associated with the archived redo log file
THREAD
The redo thread number.
LOG_SEQ
The log sequence number. Multiple rows may have the same LOG_SEQ value (for different STANDBY_NAME values).
TIME_GENERATED
The first time when the online redo log file was written to the primary database.
TIME_COMPLETED
The next time when the log file was archived on the primary database (corresponds to the NEXT_CHANGE# column).
FIRST_CHANGE#
First change number in the archived redo log file.
NEXT_CHANGE#
First change in the next log file.
SIZE (KBs)
The SIZE of the online redo log file in kilobytes.
For example, the following shows output from a SHOW DATABASE command:
DGMGRL> SHOW DATABASE 'North_Sales' 'SendQEntries' ;
PRIMARY_SEND_QUEUE
STANDBY_NAME STATUS RESETLOGS_ID
THREAD LOG_SEQ TIME_GENERATED TIME_COMPLETED
FIRST_CHANGE# NEXT_CHANGE# SIZE (KBs)
reportdbade52 ARCHIVED 497198843
1 9 06/20/2003 16:31:59 06/20/2003 16:39:57
210789 211411 186
reportdbade52 ARCHIVED 497198843
1 10 06/20/2003 16:39:57 06/20/2003 16:40:01
211411 211415 1
reportdbade52 ARCHIVED 497198843
1 11 06/20/2003 16:40:01 06/20/2003 16:40:07
211415 211418 1
CURRENT 497198843
1 12 06/20/2003 16:40:07
211418 1
|
Note: In the Data Guard GUI, this information is displayed on the Log File Details page. |
The StatusReport property returns a table that provides a list of errors or warnings about the status of the database. In a RAC database environment, it also includes the status of all running instances. Each individual database has this property. The table contains the following columns in the order shown:
INSTANCE_NAME
The value matching the SID for the instance.
ERROR_TEXT
Formatted error text.
SEVERITY
The severity of the error message. The value is either WARNING or ERROR.
For example, the following shows output from a SHOW DATABASE command:
DGMGRL> SHOW DATABASE 'North_Sales' 'StatusReport' ;
STATUS REPORT
INSTANCE_NAME SEVERITY ERROR_TEXT
sales1 ERROR ORA-16737: The log transport service for
standby "DR_Sales" has an error.
* ERROR ORA-16745: unable to add DB_UNIQUE_NAME DR_Sales
into The DG_CONFIG list because it is full
Specifies the 5 events with the longest waiting time in the specified instance. The events and their waiting time are retrieved from V$SYSTEM_EVENT. Each instance in the configuration has this property. This property is an instance level monitorable property. The table contains the following columns in the order shown:
Event
The system wait event.
Wait Time
The total amount of time waited for this event in hundredths of a second.
The following example shows output from a SHOW INSTANCE command:
DGMGRL> show instance dg10 'TopWaitEvents';
TOP SYSTEM WAIT EVENTS
Event Wait Time
rdbms ipc message 671350
SQL*Net message from client 62390
pmon timer 47897
Queue Monitor Wait 43016
wakeup time manager 38508
Configurable database properties control the behavior of databases in a broker configuration. You can view and dynamically update the values of these properties using either the CLI or the Data Guard GUI. However, some properties can only be updated through the CLI.
In most cases, the configurable database property is said to have database scope; meaning the value you set for the property applies uniformly to each instance of the database. However, in a few cases, the configurable database property is said to have instance scope; meaning, for a multiple-instance database environment, it is possible that the values of some particular properties may differ from one instance of the database to the next. Table 8-1 lists each configurable database property and indicates if the scope of the property is database-wide or instance-specific. If the Scope column contains:
Database—The value of the property is database wide, not instance specific.
Instance—The value of the property is instance specific, not database wide.
Table 8-1 Configurable Properties
| Configurable Property Name | Scope | Pertains To |
|---|---|---|
| AlternateLocation |
Instance | Log transport services |
| ApplyInstanceTimeout |
Database | Log apply services |
| ApplyNext |
Database | Log apply services for physical standby databases |
| ApplyNoDelay |
Database | Log apply services for physical standby databases |
| ApplyParallel |
Database | Log apply services for physical standby databases |
| ArchiveLagTarget |
Database | Log transport services |
| AsyncBlocks |
Database | Log transport services |
| Binding |
Database | Log transport services |
| DbFileNameConvert |
Database | Log transport services |
| DelayMins |
Database | Log apply services |
| Dependency |
Database | Log transport services |
| HostName |
Instance | Instance identification |
| InitialConnectIdentifier |
Database | Broker communication |
| LocalListenerAddress |
Instance | Broker communication |
| LogArchiveFormat |
Instance | Log transport services |
| LogArchiveMaxProcesses |
Database | Log transport services |
| LogArchiveMinSucceedDest |
Database | Log transport services |
| LogArchiveTrace |
Instance | Diagnosis |
| LogFileNameConvert |
Database | Log transport services |
| LogShipping |
Database | Log transport services |
| LogXptMode |
Database | Log transport services |
| LsbyASkipCfgPr |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyASkipErrorCfgPr |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyASkipTxnCfgPr |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyDSkipCfgPr |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyDSkipErrorCfgPr |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyDSkipTxnCfgPr |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyMaxEventsRecorded |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyMaxSga |
Instance | Log apply services (SQL redo) for logical standby databases |
| LsbyMaxServers |
Instance | Log apply services (SQL redo) for logical standby databases |
| LsbyRecordAppliedDdl |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyRecordSkipDdl |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyRecordSkipErrors |
Database | Log apply services (SQL redo) for logical standby databases |
| LsbyTxnConsistency |
Database | Log apply services (SQL redo) for logical standby databases |
| MaxFailure |
Database | Log transport services |
| NetTimeout |
Database | Log transport services |
| PreferredApplyInstance |
Database | Log apply services |
| RealTimeApply |
Database | Log apply services |
| ReopenSecs |
Database | Log transport services |
| SidName |
Instance | Instance identification |
| StandbyArchiveLocation |
Instance | Log transport services |
| StandbyFileManagement |
Database | Log apply services |
|
Note: When a broker configuration with its primary database is created and standby databases are added to the configuration, the broker imports existing settings from the databases to set many of the properties. If importing an existing setting fails, or if a property value is not imported, then the broker uses a broker default value. The default values and whether or not a property is imported is indicated within each property description. |
Specifies an alternate disk location to store the archived redo log files in the standby when the location specified by the StandbyArchiveLocation fails. The property has an instance scope, and the location it specifies has to be accessible by the instance.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Directory specification on system where the standby instance is located |
| Broker default | Empty string |
| Imported? | No |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical or logical |
| Corresponds to ... |
|
| Scope | Instance |
| GUI name | Alternate Standby Location |
|
Note: On a logical standby database, Oracle recommends theLOCATION attribute of the LOG_ARCHIVE_DEST_n initialization parameter for the local destination be different from the value of AlternateLocation property. |
Specifies the number of seconds the broker waits after detecting the current apply instance failed and before initiating the apply instance failover.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 (seconds) |
| Broker default | 120 |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Physical or logical |
| Corresponds to ... | Not applicable |
| Scope | Database |
| GUI name | Not applicable |
Specifies the number of archived redo log files that log apply services should apply immediately to the physical standby database, temporarily overriding any apply delay interval previously specified by the DelayMins property. The ApplyNext property value is applied only at the point when you explicitly specify that value. Once the value is applied, the property no longer has any effect until the next time that its value is explicitly specified.
Specifying a value for this property has no effect and will be ignored if broker management of the standby database is disabled or if log apply services are offline at the time that a value is specified. Specifying a zero value for this property always has no effect on the current behavior of log apply services.
The last value specified for this property may be displayed using the CLI SHOW command.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 log files (no action taken if zero specified) |
| Broker default | 0 |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Physical |
| Corresponds to ... | NEXT n clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement |
| Scope | Database |
| GUI name | Not applicable |
Specifies whether or not to cancel the effect of the DelayMins property that was set on the standby database:
If log apply services are online and you set ApplyNoDelay=YES, log apply services apply the archived redo log files as soon as they are archived to the standby database. This property is equivalent to using the following SQL statements.
On a physical standby database:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
On a logical standby database:
ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
If log apply services are online and you set ApplyNoDelay=NO, log apply services respect the delay settings specified by the DelayMins property of the standby database. This property is equivalent to using the following SQL statements.
On a physical standby database:
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DEFAULT DELAY;
On a logical standby database:
EXECUTE DBMS_LOGSTDBY.APPLY_UNSET('APPLY DELAY');
If log apply services are offline, then setting the property has no immediate effect. However, when log apply services are online again, the value of the property is used to determine the apply delay behavior of log apply services.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | YES or NO |
| Broker default | NO |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Physical or logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
The value of the ApplyNoDelay property persists through role changes. For example, if the ApplyNoDelay property is set to YES and the database undergoes a series of switchover operations, transitioning the database from the standby role to the primary role and then back again, the ApplyNoDelay property will continue to be set to YES throughout all of the role changes.
Specifies the number of concurrent processes log apply services can use on the physical standby database for Redo Apply. If log apply services are offline, then setting the property has no immediate effect. However, when log apply services are online again, the value of the property is used to determine the parallel apply behavior of log apply services.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values |
|
| Broker default | AUTO |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Physical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
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 records generated from a time range longer than the value set for the ARCHIVE_LAG_TARGET initialization parameter.
Specifies the size of the SGA buffer to be used when network I/O operations are to be done asynchronously using the log writer process (LGWR). The value you set for AsyncBlocks property takes effect only when the LogXptMode property is set to ASYNC.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | 0 to 1,024,000 blocks |
| Broker default | 61,440 |
| Imported? | Yes, from the ASYNC_BLOCKS column of the V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
LOG_ARCHIVE_DEST_n value of the primary database.|
See Also: Oracle Data Guard Concepts and Administration for information about theASYNC attribute of the LOG_ARCHIVE_DEST_n initialization parameter |
Specifies whether or not the standby destination is MANDATORY or OPTIONAL.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values |
|
| Broker default | OPTIONAL |
| Imported? | Yes, from the BINDING column of the V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
LOG_ARCHIVE_DEST_n value of the primary database.Distinguishes standby datafile filenames from primary datafile filenames. You must set this property on all standby databases. If you add a datafile to the primary database, this property converts the datafile name on the primary database to the datafile on the standby database.
This property is used in the following situations:
At standby mount time, it is used to rename primary datafile filenames to standby datafile filenames if the datafile file path on the standby system is different from the primary database system.
When a new datafile is created on the primary database, a corresponding new datafile will be created on the standby database if the StandbyFileManagement property is set to 'AUTO'. Oracle uses the datafile file path mapping information from the DbFileNameConvert property to determine the standby file path of the new standby datafile. If the StandbyFileManagement property is set to 'MANUAL', you must add a corresponding file to the standby database.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Set the value of this parameter to a list of string pairs:
For example, Where:
|
| Broker default | ' ' |
| Imported? | Yes, from the DB_FILE_NAME_CONVERT initialization parameter |
| Parameter class | Static |
| Role | Standby |
| Standby type | Physical |
| Corresponds to ... | DB_FILE_NAME_CONVERT initialization parameter |
| Scope | Database |
| GUI name | DB File Name Convert |
Specifies the number of minutes log apply services will delay applying the archived redo log files on the standby database.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 (minutes) |
| Broker default | 0 |
| Imported? | Yes, from the DELAY_MINS column of the V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Apply Delay (mins) |
LOG_ARCHIVE_DEST_n value of the primary database.Specifies the database unique (DB_UNIQUE_NAME) name (can be the primary or a standby database name) on which this database depends for receiving archived redo log files.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Database unique name (DB_UNIQUE_NAME), except for the standby database itself, or you can set this property to an empty string. |
| Broker default | ' ' |
| Imported? | No |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical or logical |
| Corresponds to ... | DEPENDENCY attribute for the LOG_ARCHIVE_DEST_n initialization parameter of the primary database |
| Scope | Database |
| GUI name | Not applicable |
LOG_ARCHIVE_DEST_n value of the primary database.Specifies the name of the host on which the instance is running. The property can only be updated when broker management of the database is disabled. You should only update the value when the host is renamed, in which case you need to disable broker management of the database, update the HostName property to match with the new host name, and then reenable broker management of the database.
|
Note: If the value of theHostName property does not match the actual name of the host, broker management of the database cannot be enabled. |
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Name of the host on which the instance is running |
| Broker default | Not applicable |
| Imported? | Yes |
| Parameter class | Not applicable |
| Role | Primary and standby |
| Standby type | Physical or logical |
| Corresponds to ... | HOST_NAME column of the V$INSTANCE view |
| Scope | Instance |
| GUI name | Not applicable |
Specifies the initial connection identifier the broker uses to make the first connection to a database. If using the CLI, you supply the value when you enter the CREATE CONFIGURATION or ADD DATABASE command. If using the GUI, the value is supplied by the GUI automatically. You should only update the value of this property when the original value has an error and the broker cannot connect to the database when creating the configuration or adding a database.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | A connect identifier that can be used to connect to this database |
| Broker default | Not applicable |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Primary and standby |
| Standby type | Physical or logical |
| Corresponds to ... | Not applicable |
| Scope | Database |
| GUI name | Not applicable |
Specifies the listener address at which the instance is registered. The property can only be updated when broker management of the database is disabled. You should only update the value when the LOCAL_LISTENER initialization parameter value is being changed, in which case you need to:
Disable broker management of the database
Update the LOCAL_LISTENER initialization parameter value
Update the LocalListenerAddress property in listener ADDRESS format to match with the new LOCAL_LISTENER address
Reenable broker management of the database
In the event that the LOCAL_LISTENER initialization parameter value of instances belonging to more than one database is being changed, it is recommended to:
Disable the configuration
Make the LOCAL_LISTENER initialization parameter value changes at all of the instances
Make the LocalListenerAddress property changes for all of the affected instances
Enable the configuration
|
Note: If the value of theLocalListenerAddress property does not match the actual address of the listener at which the instance is registered, broker management of the database cannot be enabled. |
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Listener address, in ADDRESS format |
| Broker default | (ADDRESS=(PROTOCOL=tcp) (HOST=<host_name>) (PORT=1521)) |
| Imported? | Yes, from the LOCAL_LISTENER initialization parameter and translated into ADDRESS format if the initialization parameter value is a new service name |
| Parameter class | Dynamic |
| Role | Primary and standby |
| Standby type | Physical or logical |
| Corresponds to ... | LOCAL_LISTENER initialization parameter |
| Scope | Instance |
| GUI name | Not applicable |
Specifies the format for filenames of archived redo log files using a database ID (%d), thread (%t), sequence number (%s), and resetlogs ID (%r).
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | %d_%t_%s_%r |
| Broker default | Empty string |
| Imported? | Yes, from the LOG_ARCHIVE_FORMAT initialization parameter on the primary database |
| Parameter class | Static |
| Role | Primary and standby |
| Standby type | Physical and logical |
| Corresponds to ... | LOG_ARCHIVE_FORMAT initialization parameter |
| Scope | Instance |
| GUI name | Not applicable |
Specifies the initial number of archiver background processes (ARC0 through ARC9) the Oracle database invokes. The actual number of archiver processes in use may increase subsequently based on archive workload.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | 1 to 10 |
| Broker default | 2 |
| Imported? | Yes, from the LOG_ARCHIVE_MAX_PROCESSES initialization parameter |
| Parameter class | Dynamic |
| Role | Primary and standby |
| Standby type | Physical and logical |
| Corresponds to ... | LOG_ARCHIVE_MAX_PROCESSES initialization parameter |
| Scope | Database |
| GUI name | Archiver Processes |
Controls when online redo log files are available for reuse. For the online redo log files to be available for reuse, archiving must succeed to a minimum number of destinations.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | 1 to 10 |
| Broker default | 1 |
| Imported? | Yes, from the LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter |
| Parameter class | Dynamic |
| Role | Primary |
| Standby type | Not applicable |
| Corresponds to ... | LOG_ARCHIVE_MIN_SUCCEED_DEST initialization parameter |
| Scope | Database |
| GUI name | Not applicable |
Set this parameter to an integer value to see the progression of the archiving of online redo log files on the primary and the standby databases. The Oracle database writes an audit trail of the archived redo log files received from the primary database into process trace files.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | A valid value is any combination of any of the following values:
0: Disable archive redo log tracing 1: Track archiving of online redo log file 2: Track archiving status of each archive redo log destination 4: Track archiving operational phase 8: Track 16: Track detailed 32: Track 64: Track ARC 128: Track FAL (fetch archive log) server related activities 256: Supported in a future release 512: Tracks asynchronous LGWR activity 1024: RFS physical client tracking 2048: ARC |
| Broker default | 255 |
| Imported? | Yes, from the LOG_ARCHIVE_TRACE initialization parameter |
| Parameter class | Dynamic |
| Role | Primary and standby |
| Standby type | Physical and logical |
| Corresponds to... | LOG_ARCHIVE_TRACE initialization parameter |
| Scope | Instance |
| GUI name | Log Archive Trace |
Converts the filename of an online redo log file on the primary database to the filename of a corresponding online redo log file on the standby database.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Set the value of this parameter to a list of an even number of string pairs, separated by commas.
For example, Where:
|
| Broker default | ' ' |
| Imported? | Yes, from the LOG_FILE_NAME_CONVERT initialization parameter |
| Parameter class | Static |
| Role | Standby |
| Standby type | Physical |
| Corresponds to ... | LOG_FILE_NAME_CONVERT initialization parameter |
| Scope | Database |
| GUI name | Log File Name Convert |
Specifies whether or not log transport services can send archived redo log files to the particular standby database. The broker uses the value of the LogShipping property only when the primary database is in the ONLINE state:
If the primary database is in the LOG-TRANSPORT-OFF state, then log transport services are offline to all standby databases, regardless of whether or not the LogShipping property is set to ON or OFF.
If the primary database is in the ONLINE state and the value of the LogShipping property is ON, then log transport services are enabled to send archived redo log files to the particular standby database. If the LogShipping property is OFF, then log transport services are disabled to send archived redo log files to the particular standby database.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | ON or OFF |
| Broker default | ON |
| Imported? | No |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... | ENABLE and DEFER values for the LOG_ARCHIVE_DEST_STATE_n initialization parameter of the primary database |
| Scope | Database |
| GUI name | Log Shipping |
LOG_ARCHIVE_DEST_n value of the primary database.Enables you to set the log transport mode. You set the log transport services on each standby database to one of the following modes:
Configures log transport services for this standby database using the LGWR, SYNC, and AFFIRM attributes of the LOG_ARCHIVE_DEST_n initialization parameter. Standby redo log files are required. This mode is required for the maximum protection or maximum availability data protection modes. This log transport mode enables the highest grade of data protection to the primary database, but also incurs the highest performance impact.
Configures log transport services for this standby database using the LGWR, ASYNC, and NOAFFIRM attributes of the LOG_ARCHIVE_DEST_n initialization parameter. Standby redo log files are required. This mode enables a moderate grade of data protection to the primary database, and incurs a lower performance impact than SYNC.
Configures log transport services for this standby database using the ARCH attribute of the LOG_ARCHIVE_DEST_n initialization parameter. Standby redo log files are not required. This mode enables the lowest grade of data protection to the primary database, and incurs the lowest performance impact. This is the default setting.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | SYNC or ASYNC or ARCH |
| Broker default |
|
| Imported? | Yes, from the ARCHIVER, TRANSMIT_MODE, and AFFIRM columns of V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical or logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Log Transport Mode |
LOG_ARCHIVE_DEST_n value of the primary database.|
See Also: Chapter 3 for more information about setting data protection modes for log transport services |
Adds a skip specification to log apply services. It provides a way to control the apply service to skip (ignore) SQL statements that you do not want to apply to the logical standby database. The SKIP operation:
Sets the criteria for identifying the SQL statements that will not be applied to the standby database
Specifies any additional processing that will be done, if necessary
Specifying a value for this property has no effect and will be ignored if management of the standby database is disabled.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | A valid set of arguments to the DBMS_LOGSTDBY.SKIP procedure |
| Broker default | Empty string |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.SKIP procedure |
| Scope | Database |
| GUI name | Add Skip Table Entries |
Adds a skip error specification to log apply services. It provides criteria to determine if an error should cause log apply services to stop. All errors to be skipped are stored in system tables that describe how exceptions should be handled.
Specifying a value for this property has no effect and will be ignored if management of the standby database is disabled.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | A valid set of arguments to the DBMS_LOGSTDBY.SKIP_ERROR procedure. The string must contain comma separators between the arguments. |
| Broker default | Empty string |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.SKIP_ERROR procedure |
| Scope | Database |
| GUI name | Add Skip Table Entries |
Skips over a transaction that caused the log apply services to stop applying transactions to the logical standby database. This property enables you to specify the transaction ID (XIDSQN NUMBER) of the problematic transaction that you want log apply services to ignore. Before you restart log apply services, you should issue a SQL transaction that will correctly update the logical standby database in place of the skipped transaction. Applying a compensating transaction will help keep the logical standby database transactionally consistent with the primary database.
Specifying a value for this property has no effect and will be ignored if management of the standby database is disabled.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | A valid set of arguments to the DBMS_LOGSTDBY.SKIP_TRANSACTION procedure. Use comma separators between the arguments. |
| Broker default | Empty string |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.SKIP_TRANSACTION procedure |
| Scope | Database |
| GUI name | Skip Edit Properties |
|
Note: Data Guard GUI indirectly supports skipping a transaction using the Skip Edit Properties page. |
Deletes an existing skip specification from log apply services. It reverses or removes the actions of the LsbyASkipCfgPr property by finding the record, matching all the parameters, and removing the record from the system table. The match must be exact, and multiple skip actions can be removed only by a matching number of unskip actions. You cannot remove multiple skip actions by using wildcard characters as a value to this property.
Specifying a value for this property has no effect and will be ignored if management of the standby database is disabled.
| Category | Description |
|---|---|
| Datatype | String |
| Valid Values | A valid set of arguments to the DBMS_LOGSTDBY.UNSKIP procedure |
| Broker Default | Empty string |
| Imported? | No |
| Parameter Class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.UNSKIP procedure |
| Scope | Database |
| GUI name | Remove Skip Table Entries |
Deletes an existing skip error specification from log apply services. It reverses or removes the actions of the LsbyASkipErrorCfgPr property by finding the record, matching all of the parameters and removing the record from the system table. The match must be exact, and multiple skip actions can be removed only by a matching number of unskip actions. You cannot remove multiple skip actions by using wildcard characters as a value to this property.
Specifying a value for this property has no effect and will be ignored if management of the standby database is disabled.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | A valid set of arguments to the DBMS_LOGSTDBY.UNSKIP_ERROR procedure. The string must contain comma separators between the arguments. |
| Broker default | Empty string |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.UNSKIP_ERROR procedure |
| Scope | Database |
| GUI name | Remove Skip Table Entries |
Reverses or removes the actions of the LsbyASkipTxnCfgPr property. The transaction IDs must match exactly, and multiple skip transaction actions can be removed only by a matching number of unskip transaction actions. You cannot remove multiple skip transaction actions by using wildcard characters as a value to this property.
Specifying a value for this property has no effect and will be ignored if management of the standby database is disabled.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | A valid set of arguments to the DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure |
| Broker default | Empty string |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure |
| Scope | Database |
| GUI name | Not applicable |
Specifies the number of events that will be stored in the DBA_LOGSTDBY_EVENTS table, which stores logical standby event information.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 |
| Broker default | 0 |
| Imported? | Yes, from the MAX_EVENTS_RECORDED row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.APPLY_SET('MAX_EVENTS_RECORDED') and the DBMS_LOGSTDBY.APPLY_UNSET('MAX_EVENTS_RECORDED') procedures |
| Scope | Database |
| GUI name | Max Events Recorded |
Specifies the number of megabytes for the allocation of log apply services cache in the system global area (SGA). If the value is 0, log apply services use one quarter of the value set for the SHARED_POOL_SIZE initialization parameter.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 |
| Broker default | 0 |
| Imported? | Yes, from the MAX_SGA row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.APPLY_SET('MAX_SGA') and the DBMS_LOGSTDBY.APPLY_UNSET('MAX_SGA') procedures |
| Scope | Instance |
| GUI name | Max SGA (MB) |
Specifies the number of parallel query servers specifically reserved for log apply services. If the value is 0, log apply services use all available parallel query servers to read the log files and apply changes.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 |
| Broker default | 0 |
| Imported? | Yes, from the MAX_SERVERS row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.APPLY_SET('MAX_SERVERS') and the DBMS_LOGSTDBY.APPLY_UNSET('MAX_SERVERS') procedures |
| Scope | Instance |
| GUI name | Max Servers |
Controls whether or not DDL statements that were applied to the logical standby database are recorded in the DBA_LOGSTDBY_EVENTS table. Specify one of the following values:
TRUE: DDL statements applied to the logical standby database are recorded in the DBA_LOGSTDBY_EVENTS table. This is the default parameter setting.
FALSE: Applied DDL statements are not recorded.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | TRUE or FALSE |
| Broker default | TRUE |
| Imported? | Yes, from the RECORD_APPLIED_DDL row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.APPLY_SET('RECORD_APPLIED_DDL') and the DBMS_LOGSTDBY.APPLY_UNSET('RECORD_APPLIED_DDL') procedures |
| Scope | Database |
| GUI name | Record Applied DDL |
Controls whether or not skipped DDL statements are recorded in the DBA_LOGSTDBY_EVENTS table. Specify one of the following values:
TRUE: Skipped DDL statements are recorded in the DBA_LOGSTDBY_EVENTS table. This is the default parameter setting.
FALSE: Skipped DDL statements are not recorded in the DBA_LOGSTDBY_EVENTS table.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | TRUE or FALSE |
| Broker default | TRUE |
| Imported? | Yes, from the RECORD_SKIP_DDL row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.APPLY_SET('RECORD_SKIP_DDL') and the DBMS_LOGSTDBY.APPLY_UNSET('RECORD_SKIP_DDL') procedures |
| Scope | Database |
| GUI name | Record Skip DDL |
Controls whether or not skipped errors (as described by the DBMS_LOGSTDBY.SKIP_ERROR procedure) are recorded in the DBA_LOGSTDBY_EVENTS table. Specify one of the following values:
TRUE: Skipped errors are recorded in the DBA_LOGSTDBY_EVENTS table.
FALSE: Skipped errors are not recorded in the DBA_LOGSTDBY_EVENTS table.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | TRUE or FALSE |
| Broker default | TRUE |
| Imported? | Yes, from the RECORD_SKIP_ERRORS row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to | DBMS_LOGSTDBY.APPLY_SET('RECORD_SKIP_ERRORS') and the DBMS_LOGSTDBY.APPLY_UNSET('RECORD_SKIP_ERRORS') procedures |
| Scope | Database |
| GUI name | Record Skip Errors |
Controls the level of transaction consistency maintained between the primary and standby databases. Specify one of the following values:
FULL: Transactions are applied to the logical standby database in the exact order in which they were committed on the primary database. This option may affect performance.
READ_ONLY: Transactions are committed out of order (which provides better performance). SQL SELECT statements return read-consistent results. This is particularly beneficial when the logical standby database is being used to generate reports.
|
Note: DML statements involving standby tables are not allowed in this mode. |
NONE: Transactions are committed out of order and no attempt is made to provide read-consistent results. This results in the best performance of the three modes. If applications reading the logical standby database make no assumptions about transaction order, this option works well.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | FULL or READ_ONLY or NONE |
| Broker default | FULL |
| Imported? | Yes, from the TRANSACTION_CONSISTENCY row of SYSTEM.LOGSTDBY$PARAMETERS |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Logical |
| Corresponds to ... | DBMS_LOGSTDBY.APPLY_SET('TRANSACTION_CONSISTENCY') and the DBMS_LOGSTDBY.APPLY_UNSET('TRANSACTION_CONSISTENCY') procedures |
| Scope | Database |
| GUI name | Transaction Consistency Level |
Specifies the maximum number of contiguous archiving failures before the log transport services stop trying to transport archived redo log files to the standby database. A value of zero indicates that an unlimited number of failures are allowed.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 |
| Broker default | 0 |
| Imported? | Yes, from the MAX_FAILURE column of V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
LOG_ARCHIVE_DEST_n value of the primary database.Specifies the number of seconds the LGWR waits for Oracle Net Services to respond to a LGWR request. It is used to bypass the long connection timeout in TCP. This property is only used when the LogXptMode property of the same database is set to SYNC or ASYNC.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | 0, 15 to 1200 |
| Broker default | 30 |
| Imported? | Yes, from the NET_TIMEOUT column of V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
LOG_ARCHIVE_DEST_n value of the primary database.Indicates that a particular instance is the preferred choice for serving log apply services. It is only used when the database is a standby RAC database. The value could be an empty string (default) which means the broker chooses the apply instance.
| Category | Description |
|---|---|
| Datatype | String |
| Valid Values | The instance name (SID) or empty string |
| Broker Default | Empty string |
| Imported? | No |
| Parameter Class | Not applicable |
| Role | Standby |
| Standby Type | Physical and logical |
| Corresponds to | Not applicable |
| Scope | Database |
| GUI Name | Apply Instance |
Turns on and off the real-time apply feature of the physical or logical standby database. You need to set up standby redo log files to use the real-time apply feature. Once real-time apply is turned on, the apply delay feature is automatically turned off.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | ON or OFF |
| Broker default | OFF |
| Imported? | No |
| Parameter class | Not applicable |
| Role | Standby |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Real Time Apply |
|
See Also: Section 3.5.1 and Oracle Data Guard Concepts and Administration for information about managing real-time apply |
Specifies the minimum number of seconds before the archiver process (ARCn, foreground, or log writer process) should try again to access a previously failed destination.
| Category | Description |
|---|---|
| Datatype | Integer |
| Valid values | >=0 seconds |
| Broker default | 0 |
| Imported? | Yes, from the REOPEN_SECS column of V$ARCHIVE_DEST view of the primary database |
| Parameter class | Dynamic |
| Role | StandbyFoot 1 |
| Standby type | Physical and logical |
| Corresponds to ... |
|
| Scope | Database |
| GUI name | Not applicable |
LOG_ARCHIVE_DEST_n value of the primary database.Specifies the SID of the instance. The property can only be updated when broker management of the database is disabled. You should only update the value when the SID is changed, in which case you need to disable broker management of the database, update the SidName property to match with the new SID, and reenable broker management of the database.
|
Note: If the value of theSidName property does not match the actual value of the SID, broker management of the database cannot be enabled. |
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | SID of the instance |
| Broker default | Not applicable |
| Imported? | Yes |
| Parameter class | Not applicable |
| Role | Primary and standby |
| Standby type | Physical or logical |
| Corresponds to ... | INSTANCE_NAME column of the V$INSTANCE view |
| Scope | Instance |
| GUI name | Not applicable |
Specifies the location of archived redo log files arriving from a primary database. Oracle recommends that you always explicitly set the value (if flash recovery area is not in use).
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | Nonempty file specification of the location of archived redo log files on the standby database |
| Broker default | dgsby_<db_unique_name> |
| Imported? | Yes, from the DESTINATION column of the V$ARCHIVE_DEST fixed view of the standby database where the destination is a local destination and where the VALID_FOR attribute is compatible with the string (STANDBY_ROLE, STANDBY_LOGFILE); if no such destination exists, import is from the STANDBY_ARCHIVE_DEST initialization parameter |
| Parameter class | Dynamic |
| Role | Standby |
| Standby type | Physical or logical |
| Corresponds to ... |
|
| Scope | Instance |
| GUI name | Standby Archive Location |
|
Note: On a logical standby database, Oracle recommends theLOCATION attribute of the LOG_ARCHIVE_DEST_n initialization parameter for the local destination be different from the value of StandbyArchiveLocation property. |
Affects how the add datafile operation on the primary database is applied on the standby database. If this property is set to AUTO, in conjunction with valid settings in the DbFileNameConvert property, a corresponding new datafile is automatically created on the standby database. The location of this new standby datafile is determined by the value of the DbFileNameConvert property.
If this property is set to MANUAL, you have to create the correct new datafile on the standby database manually.
| Category | Description |
|---|---|
| Datatype | String |
| Valid values | AUTO or MANUAL |
| Broker default | AUTO |
| Imported? | Yes, from the STANDBY_FILE_MANAGEMENT initialization parameter |
| Parameter class | Dynamic |
| Role | Standby |
| Standby type | Physical or logical |
| Corresponds to ... | STANDBY_FILE_MANAGEMENT initialization parameter |
| Scope | Database |
| GUI name | Not applicable |
|
 Copyright © 2000, 2003 Oracle Corporation All Rights Reserved. |
|