8 Data Guard Broker Properties

8.1.1 BystandersFollowRoleChange

The BystandersFollowRoleChange configuration property allows the user to decide whether the broker should determine whether bystander standby databases will be viable standby databases for the new primary database as part of performing a complete failover. Setting the property to ALL directs the broker to evaluate and detect each standby database that can be a viable standby database to the new primary database, as part of failover processing. Setting the property to NONE directs the broker to perform failover without evaluating standby database viability. This option decreases the processing time for failover, but disables broker management of all databases in the configuration. If fast-start failover is enabled, the observer will automatically reinstate the standby databases after failover has completed. Otherwise, you will have to manually reinstate the standby databases after failover has completed.

8.1.2 CommunicationTimeout

The CommunicationTimeout configuration property allows you to decide how many seconds the broker should wait before timing out its network communication between databases in the configuration. A value of zero indicates that a network communication should never be timed out.

8.1.3 ExternalDestination1

The ExternalDestination1 configuration property is used to specify a redo transport destination that can receive redo data from the current primary database. To set up transport of redo data to the specified destination, the broker uses the values specified for this parameter to define a LOG_ARCHIVE_DEST_n initialization parameter on the primary database. The broker also monitors the health of the transport to the specified destination.

After a role change, the broker automatically sets up a LOG_ARCHIVE_DEST_n initialization parameter on the new primary database to ship redo data to the specified destination.

8.1.4 ExternalDestination2

The ExternalDestination2 configuration property is used to specify a redo transport destination that can receive redo data from the current primary database. To set up transport of redo data to the specified destination, the broker uses the values specified for this parameter to define a LOG_ARCHIVE_DEST_n initialization parameter on the primary database. The broker also monitors the health of the transport to the specified destination.

After a role change, the broker automatically sets up a LOG_ARCHIVE_DEST_n initialization parameter on the new primary database to ship redo data to the specified destination.

8.1.5 FastStartFailoverAutoReinstate

The FastStartFailoverAutoReinstate configuration property causes the former primary database to be automatically reinstated if a fast-start failover was initiated because the primary database was either isolated or had crashed. To prevent automatic reinstatement of the former primary database in these cases, set this configuration property to FALSE.

The broker never automatically reinstates the former primary database if a fast-start failover was initiated because a user configuration condition was detected or was requested by an application calling the DBMS_DG.INITIATE_FS_FAILOVER function.

8.1.6 FastStartFailoverLagLimit

The FastStartFailoverLagLimit configuration property establishes an acceptable limit, in seconds, that the standby is allowed to fall behind the primary in terms of redo applied, beyond which a fast-start failover will not be allowed. The lowest possible value is 10 seconds.

This property is used when fast-start failover is enabled and the configuration is operating in maximum performance mode.

8.1.7 FastStartFailoverPmyShutdown

The FastStartFailoverPmyShutdown configuration property causes the primary database to shut down if fast-start failover is enabled and V$DATABASE.FS_FAILOVER_STATUS indicates the primary has been STALLED for longer than FastStartFailoverThreshold seconds. In such a situation, it is likely that the primary has been isolated and a fast-start failover has already occurred. A value of TRUE helps to ensure that an isolated primary database cannot satisfy user queries.

Setting this property to FALSE will not prevent the primary database from shutting down if a fast-start failover occurred because a user configuration condition was detected or was requested by an application by calling the DBMS_DG.INITIATE_FS_FAILOVER function.

8.1.8 FastStartFailoverThreshold

The FastStartFailoverThreshold configuration property defines the number of seconds the observer attempts to reconnect to the primary database before initiating a fast-start failover to the target standby database. The time interval starts when the observer first loses connection with the primary database. If the observer is unable to regain a connection to the primary database within the specified time, then the observer initiates a fast-start failover. See Step 4 in Section 5.5.2 for more information about setting this property.

The observer ignores the threshold completely if a configurable fast-start failover condition is detected or an application has requested that fast-start failover be initiated.

For help in determining an appropriate value for this property, you can use the information provided in the V$FS_OBSERVER_HISTOGRAM view. This view displays statistics that are based on the frequency of successful pings between the observer and primary database for different time intervals. (See Oracle Database Reference for a description of the V$FS_OBSERVER_HISTOGRAM view.)

8.1.9 ObserverOverride

The ObserverOverride configuration property, when set to TRUE, allows an automatic failover to occur when the observer has lost connectivity to the primary, even if the standby has a healthy connection to the primary.

The ObserverOverride configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4) and higher.

8.1.10 ObserverReconnect

The ObserverReconnect configuration property specifies how often the observer establishes a new connection to the primary database. When this property is set to the default value of 0, the observer creates and maintains a connection to the primary database, but it does not periodically create a new connection to the primary database. While this eliminates the processing overhead associated with periodically establishing a new observer connection to the primary database, it also prevents the observer from detecting that it is not possible to create new connections to the primary database. Oracle recommends that this property be set to a value that is small enough to allow timely detection of faults at the primary database, but large enough to limit the overhead associated with periodic observer connections to an acceptable level.

The ObserverReconnect configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4) and higher.

8.1.11 OperationTimeout

The OperationTimeout configuration property specifies the maximum amount of time the broker should wait for health check, get monitorable property, and set property operations to complete.

8.1.12 PrimaryLostWriteAction

The PrimaryLostWriteAction configuration property determines what action is taken if a standby database detects that a lost write has occurred at the primary database:

• CONTINUE - The primary database continues operating if a standby database detects that a lost write has occurred at the primary database. This is the default action.

• SHUTDOWN - The primary database performs a shutdown abort if a standby database detects that a lost write has occurred at the primary database.

Fast start failover is disabled if a standby detects that a lost write has occurred at the primary database. Automatic failover will therefore not occur if a standby detects that a lost write has occurred at the primary database, even if PrimaryLostWriteAction is set to SHUTDOWN.

Diagnostic information is written to the database alert and broker logs at the primary database and at the standby database where the lost write was detected.

If a lost write occurs at the primary database, then follow the guidelines in "Resolving ORA-752 or ORA-600 [3020] During Standby Recovery" in My Oracle Support Note 1265884.1 located at http://support.oracle.com.

The PrimaryLostWriteAction configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4).

8.1.13 TraceLevel

The TraceLevel configuration property is used to control the amount of tracing performed by the broker for every member in the configuration. Setting the property to USER limits the tracing to completed operations and to any warning or error messages resulting from an operation or health check. Setting the property to SUPPORT increases the amount of tracing to include lower-level information needed by Oracle Support Services.

The TraceLevel configuration property is available only in Oracle Database 11g Release 2 (11.2.0.3) and higher.

8.2.1 InconsistentLogXptProps (Inconsistent Redo Transport Properties)

The InconsistentLogXptProps monitorable database property returns a table that shows all properties related to redo transport services whose values are inconsistent between the broker configuration file and the runtime value in the database.

Although the properties reported in this table are database-specific properties, the inconsistency is reported on an instance-specific basis. 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 identifying the SID for the instance.

• STANDBY_NAME

  The database unique name (DB_UNIQUE_NAME) of the standby database to which this redo transport services property pertains.

• PROPERTY_NAME

  The name of the redo transport services property with an inconsistent value.

• MEMORY_VALUE

  The runtime value being used in the database.

• BROKER_VALUE

  The value of the redo transport services property saved in the broker configuration file.

8.2.2 InconsistentProperties (Inconsistent Database Properties)

The InconsistentProperties monitorable database 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 identifying 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.

8.2.3 LogXptStatus (Redo Transport Status)

The LogXptStatus monitorable database property returns a table that contains the error status of redo 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 identifying 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 redo transport error. If there is no error, the field is empty.

Each entry in the table indicates the status of redo transport services on one primary instance to one standby database.

The error status can be an empty string, which indicates there is no error.

In the following example, the STATUS from South_Sales is empty because there is no error for the South_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
         north_sales1           South_Sales
         north_sales1          South_Report    ORA-01034: ORACLE not available

8.2.4 LsbyFailedTxnInfo (Logical Standby Failed Transaction Information)

The LsbyFailedTxnInfo monitorable database 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.

8.2.5 LsbyParameters (Logical Standby Parameters)

The LsbyParameters monitorable database 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.

8.2.6 LsbySkipTable (Logical Standby Skip Table)

The LsbySkipTable monitorable database property lists the SQL Apply skip specifications. These skip specifications specify filters for SQL Apply 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

This property pertains to a logical standby database.

8.2.7 LsbySkipTxnTable (SQL Apply Skip Transaction Table)

The LsbySkipTxnTable monitorable database property 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 SQL Apply stopped

This property pertains to SQL Apply.

8.2.8 RecvQEntries (Receive Queue Entries)

The RecvQEntries monitorable database 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 'South_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

8.2.9 SendQEntries (Send Queue Entries)

The SendQEntries monitorable database 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 a 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)
       South_Sales   ARCHIVED        497198843
1                    9  06/20/2003 16:31:59  06/20/2003 16:39:57
210789           211411              186
       South_Sales   ARCHIVED        497198843
1                   10  06/20/2003 16:39:57  06/20/2003 16:40:01
211411           211415                1
       South_Sales   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

8.2.10 TopWaitEvents

The TopWaitEvents monitorable database property 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-specific 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 north_sales1 '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

8.3.1 AlternateLocation

The AlternateLocation configurable database property specifies an alternate disk location to store the archived redo log files in the standby when the location specified by the StandbyArchiveLocation configurable database property fails. The property has instance-specific scope, and the location it specifies has to be accessible by the instance.

^Footnote 1 Although this property is set for the standby instance, it is indirectly related to redo transport services for the primary database. The broker sets up both an alternate local destination on the standby instance and an alternate remote destination on the primary database.

8.3.2 ApplyInstanceTimeout

The ApplyInstanceTimeout configurable database property specifies the number of seconds the broker waits after detecting the current apply instance failed before initiating the apply instance failover.

8.3.3 ApplyLagThreshold

The ApplyLagThreshold configurable database property generates a warning status for a logical or physical standby when the database's apply lag exceeds the value specified by the property. The property value is expressed in seconds. A value of 0 seconds results in no warnings being generated when an apply lag exists.

The ApplyLagThreshold configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4) and higher.

8.3.4 ApplyParallel

The ApplyParallel configurable database property specifies whether Redo Apply should use multiple processes to apply redo data to the physical standby database. If Redo Apply is shut off, then setting the property has no immediate effect. However, when Redo Apply is running again, the value of the property is used to determine the parallel apply behavior of Redo Apply.

8.3.5 ArchiveLagTarget

The ArchiveLagTarget configurable database property 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.

8.3.6 Binding

The Binding configurable database property specifies whether the standby destination is MANDATORY or OPTIONAL.

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.7 DbFileNameConvert

The DbFileNameConvert configurable database property distinguishes physical standby datafile filenames from primary datafile filenames. If you add a datafile to the primary database, this property converts the datafile name on the primary database to the datafile on the physical standby database.

This property is used in the following situations:

• At physical standby mount time, it is used to rename primary datafile filenames to standby datafile filenames if the datafile file path on the physical standby system is different from the primary database system.

• When a new data file is created on the primary database, a corresponding new data file will be created on the physical standby database if the StandbyFileManagement configurable database property is set to 'AUTO'. Oracle uses the data-file file-path mapping information from the DbFileNameConvert property to determine the standby file path of the new standby data file. If the StandbyFileManagement property is set to 'MANUAL', you must add a corresponding file to the physical standby database.

8.3.8 DelayMins

The DelayMins configurable database property specifies the number of minutes log apply services will delay applying the archived redo log data on the standby database. When the DelayMins property is set to the default value of 0 minutes, log apply services apply redo data as soon as possible.

If the DelayMins property is set to 0, start log apply services as follows:

• Start Redo Apply on physical standby databases using the following SQL statement:

  ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE;
  

• Start SQL Apply on logical standby databases using the following SQL statement:

  ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
  

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.9 DGConnectIdentifier

The DGConnectIdentifier configurable database property specifies the connection identifier the broker uses when making connections to a database. If using DGMGRL, you supply the value when you enter the CREATE CONFIGURATION or ADD DATABASE command. If you are using Enterprise Manager, the value is supplied automatically. The connect identifier for a database must:

• Allow all other databases in the configuration to reach it.

• Allow the database to reach itself.

• Allow all instances of an Oracle RAC database to be reached.

• Specify a service that all instances dynamically register with the listeners so that connect-time failover on an Oracle RAC database is possible.

• Have failover attributes set to allow the primary database's Redo Transport Services to continue shipping redo data to an Oracle RAC standby database, even if the receiving instance of that standby database has failed.

The value of this property is specified in the SERVICE attribute of the LOG_ARCHIVE_DEST_n parameter when the broker configures redo transport services on the primary database.

8.3.10 FastStartFailoverTarget

The FastStartFailoverTarget configuration property specifies the DB_UNIQUE_NAME of the database that will be the target of a fast-start failover when this database is the primary database. See Step 2 in Section 5.5.2 for more information about setting this property.

8.3.11 LogArchiveFormat

The LogArchiveFormat configurable instance-specific property specifies the format for filenames of archived redo log files using a database ID (%d), thread (%t), sequence number (%s), and resetlogs ID (%r).

8.3.12 LogArchiveMaxProcesses

The LogArchiveMaxProcesses configurable database property specifies the initial number of archiver processes (ARCn) the Oracle database invokes. The actual number of archiver processes in use may increase subsequently based on the archiving workload.

8.3.13 LogArchiveMinSucceedDest

The LogArchiveMinSucceedDest configurable database property 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.

8.3.14 LogArchiveTrace

Set the LogArchiveTrace configurable instance-specific property 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.

8.3.15 LogFileNameConvert

The LogFileNameConvert configurable database property 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 physical standby database.

8.3.16 LogShipping

The LogShipping configurable database property specifies whether or not redo transport services can send redo data to the particular standby database. The broker uses the value of the LogShipping property only when the primary database is in the TRANSPORT-ON state:

• If the primary database is in the TRANSPORT-OFF state, then redo transport services to all standby databases are disabled, regardless of whether or not the LogShipping property is set to ON or OFF.

• If the primary database is in the TRANSPORT-ON state and the value of the LogShipping property is ON, then redo transport services are enabled to send redo data to the particular standby database. If the LogShipping property is OFF, then redo transport services are disabled to send redo data to the particular standby database.

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.17 LogXptMode

The LogXptMode configurable database property enables you to set the redo transport service. You set the redo transport services on each standby database to one of the following modes:

• SYNC

  Configures redo transport services for this standby database using the 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 redo transport service enables the highest grade of data protection to the primary database, but also incurs the highest performance impact.

• ASYNC

  Configures redo transport services for this standby database using the 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.

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.18 LsbyASkipCfgPr

The LsbyASkipCfgPr configurable database property provides a way to add a skip specification to SQL Apply 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.

8.3.19 LsbyASkipErrorCfgPr

The LsbyASkipErrorCfgPr configurable database property adds a skip error specification to SQL Apply. It provides criteria to determine if an error should cause SQL Apply 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.

8.3.20 LsbyASkipTxnCfgPr

The LsbyASkipTxnCfgPr configurable database property skips over a transaction that caused SQL Apply 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 SQL Apply to ignore. Before you restart SQL Apply, 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.

8.3.21 LsbyDSkipCfgPr

The LsbyDSkipCfgPr configurable database property deletes an existing skip specification from SQL Apply. 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.

8.3.22 LsbyDSkipErrorCfgPr

The LsbyDSkipErrorCfgPr configurable database property deletes an existing skip error specification from SQL Apply. 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.

8.3.23 LsbyDSkipTxnCfgPr

The LsbyDSkipTxnCfgPr configurable database property 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.

8.3.24 LsbyMaxEventsRecorded

The LsbyMaxEventsRecorded configurable database property specifies the number of events that will be stored in the DBA_LOGSTDBY_EVENTS table, which stores logical standby event information.

8.3.25 LsbyMaxSga

The LsbyMaxSga configurable instance-specific property specifies the number of megabytes for the allocation of SQL Apply cache in the system global area (SGA). If the value is 0, SQL Apply uses one quarter of the value set for the SHARED_POOL_SIZE initialization parameter.

8.3.26 LsbyMaxServers

The LsbyMaxServers configurable instance-specific property specifies the number of parallel query servers specifically reserved for SQL Apply. If the value is 0, SQL Apply uses all available parallel query servers to read the log files and apply changes.

8.3.27 LsbyPreserveCommitOrder

The LsbyPreserveCommitOrder configurable database property controls whether transactions are committed on the logical standby database in the exact same order in which they were committed on the primary database. Specify one of the following values:

• TRUE: Transactions are applied to the logical standby database in the exact order in which they were committed on the primary database.

• FALSE: Transactions containing non-overlapping sets of rows may be committed in a different order than they were committed on the primary database.

8.3.28 LsbyRecordAppliedDdl

The LsbyRecordAppliedDdl configurable database property controls whether or not SQL 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 setting.

• FALSE: Applied DDL statements are not recorded.

8.3.29 LsbyRecordSkipDdl

The LsbyRecordSkipDdl configurable database property 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 setting.

• FALSE: Skipped DDL statements are not recorded in the DBA_LOGSTDBY_EVENTS table.

8.3.30 LsbyRecordSkipErrors

The LsbyRecordSkipErrors configurable database property 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.

8.3.31 MaxConnections

The MaxConnections configurable database property specifies how many ARCn processes will be used in parallel to transmit redo data from a single archived redo log on the primary database to the archived redo log at the remote site. If the MaxConnections property is set to a value greater than 1, redo transport services use multiple ARCn processes to transmit redo data to archived redo log files at the remote destinations.

^Footnote 1 The LOG_ARCHIVE_MAX_PROCESSES initialization parameter affects the actual number of ARCn processes used by an instance.

8.3.32 MaxFailure

The MaxFailure configurable database property specifies the maximum number of contiguous archiving failures before the redo 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.

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.33 NetTimeout

The NetTimeout configurable database property 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.

8.3.34 ObserverConnectIdentifier

The ObserverConnectIdentifier configurable database property specifies a connect identifier that can be used by the observer to connect to this database. This can pertain only to the primary database, or to the target standby database when fast-start failover is enabled.

^Footnote 1 When this is Empty String (not set by the user), the connect identifier specified by this database's DGConnectIdentifier property will be used by the observer.

8.3.35 PreferredApplyInstance

The PreferredApplyInstance configurable database property indicates that a particular instance is the preferred choice for serving log apply services. It is only used when the database is a standby Oracle RAC database. The value could be an empty string (default) which means the broker chooses the apply instance.

8.3.36 RedoCompression

The RedoCompression configurable database property is used to specify whether redo data is transmitted to a standby database in compressed or uncompressed form.

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.37 ReopenSecs

The ReopenSecs configurable database property 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.

^Footnote 1 Although this property is set for the standby database, it is indirectly related to the redo transport services for the primary database. The broker propagates the setting you specify on the standby database to the corresponding attributes of the LOG_ARCHIVE_DEST_n value of the primary database.

8.3.38 SidName

The SidName configurable database property specifies the Oracle System Identifier (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.

8.3.39 StandbyArchiveLocation

The StandbyArchiveLocation configurable database property specifies the location of archived redo log files arriving from a primary database. Oracle recommends that you always explicitly set the value.

8.3.40 StandbyFileManagement

The StandbyFileManagement configurable database 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 configurable database 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.

8.3.41 StaticConnectIdentifier

The StaticConnectIdentifier configurable instance-specific property specifies the connection identifier that the DGMGRL client will use when starting database instances.

^Footnote 1 If the instance specified by the SidName property is started on a different host (read from the HOST_NAME column of the V$INSTANCE view) than the host on which it had been previously started, the broker automatically updates the default value of the StaticConnectIdentifier property to incorporate the current ADDRESS attribute of the listener that is specified for the LOCAL_LISTENER initialization parameter.

8.3.42 TransportDisconnectedThreshold

The TransportDisconnectedThreshold configurable database property can be used to generate a warning status for a logical, physical, or snapshot standby when the last communication from the primary database exceeds the value specified by the property. The property value is expressed in seconds. A value of 0 seconds results in no warnings being generated.

The TransportDisconnectedThreshold configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4) and higher.

8.3.43 TransportLagThreshold

The TransportLagThreshold configurable database property can be used to generate a warning status for a logical, physical, or snapshot standby when the database's transport lag exceeds the value specified by the property. The property value is expressed in seconds. A value of 0 seconds results in no warnings being generated when a transport lag exists.

The TransportLagThreshold configuration property is available only in Oracle Database 11g Release 2 (11.2.0.4) and higher.