8
Database Resource Properties

Database resource properties help you to view and control the behavior of database resource objects, log transport services, and log apply services in a broker configuration. This chapter provides the following sections about the monitorable and configurable properties:

Section 8.1, "Monitorable (Read-Only) Properties for Database Resources"

Section 8.2, "Configurable Properties for Database Resources"

8.1 Monitorable (Read-Only) Properties for Database Resources

Monitorable properties allow you to view information related to resources, 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 resource is enabled and in an online state. Data Guard Manager displays the information obtained from these properties on the Properties page, except for the LsbySkipTable and the LsbySkipTxnTable properties, which can be seen on the Data Guard Manager Properties page.

The following sections describe the database resource monitorable properties:

8.1.1 InconsistentLogXptProps (Inconsistent Log Transport Properties)

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

Query this property on the primary database resource. The table contains the following columns:

STANDBY_SITE_NAME

The name of the standby site that contains the database resource to which this log transport services property pertains.
PROPERTY_NAME

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

The corresponding value saved in the database server parameter file.
SPFILE_VALUE

The corresponding value saved in the server parameter file (SPFILE).

METADATA_VALUE

The value of the log transport services property saved in the Data Guard configuration file.

Note:

In Oracle9i Data Guard Manager, information from InconsistentLogXptProps monitorable property is displayed on the Properties page for the database resource. The first column of the Properties page contains icons indicating a normal, error, or warning status for each property. If a property has an inconsistent property value, the first column will contain a triangular (yellow) warning icon. You can obtain further details about the warning by placing the mouse cursor over the warning sign.

8.1.2 InconsistentProperties (Inconsistent Database Properties)

The InconsistentProperties monitorable property returns a table that shows all database properties whose values contained in the Data Guard configuration file are inconsistent with the actual values in the database, and the values in the corresponding server parameter file (SPFILE) or the runtime values in the database.

Query this property on the each individual database resource. The table contains the following columns:

PROPERTY_NAME

The name of the database property with the inconsistent value.
DATABASE_VALUE

The corresponding runtime value being used in the database.
SPFILE_VALUE

The corresponding value saved in the server parameter file (SPFILE).

METADATA_VALUE

The value of the database property saved in the Data Guard configuration file.

Note:

In Oracle9i Data Guard Manager, information from the InconsistentProperties monitorable property is displayed on the Properties page for the database resource. The first column of the Properties page contains icons indicating a normal, error, or warning status for each property. If a property has an inconsistent property value, the first column will contain a triangular (yellow) warning icon. You can obtain further details about the warning by placing the mouse cursor over the warning sign.

8.1.3 LogXptStatus (Log Transport Status)

The LogXptStatus property contains the error status of log transport services for each of the currently enabled standby sites. You query this property on the primary database resource.

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 string for Standby1 is empty because there is no error for the Standby1 destination. The standby2 destination returned the ORA-01034 message.

DGMGRL> SHOW RESOURCE VERBOSE 'Sales_db' 'LogXptStatus';
  LogXptStatus ='Standby1=,standby2=ORA-01034: ORACLE not available'

Note:

In Oracle9i Data Guard Manager, information from the LogXptStatus property is displayed in the Log Transport Summary section of the General property page for the primary database resource.

8.1.4 LsbyFailedTxnInfo (Logical Standby Failed Transaction Information)

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 pound (###) signs.

8.1.5 LsbyParameters (Logical Standby Parameters)

The LsbyParameters property contains a string that identifies the MAX_SGA (maximum system global area) and MAX_SERVERS (maximum number of parallel query servers) specifically reserved for log apply services. The value contains the following information, separated by the "###" string:

MAX_SGA
MAX_SERVERS

8.1.6 LsbySkipTable (Logical Standby Skip Table)

The LsbySkipTable property returns a table with following columns from the DBA_LOGSTDBY_SKIP view:

ERROR

Indicates if the statement should be skipped or if errors should be returned for the statement
STATEMENT_OPT

Indicates the type of statement that should be skipped
SCHEMA

The schema name under 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
ACTIVE

The table separates the column information with the "###" string.

8.1.7 LsbySkipTxnTable (Logical Standby Skip Transaction Table)

The LsbySkipTxnTable 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

8.1.8 SbyLogQueue (Standby Log Queue)

The SbyLogQueue property returns a table that indicates all logs that were received by the standby site, but have not yet been applied. If no rows are returned, it implies all logs received have been applied. The table contains the following columns in the order shown:

LOG_SEQ

The log sequence number
TIME_GENERATED

The time when the log was generated
TIME_COMPLETED

The time when the log was completed

For example:

DGMGRL> SHOW RESOURCE VERBOSE 'reportingdb' 'SbyLogQueue';
STANDBY_RECEIVE_QUEUE
             LOG_SEQ  TIME_GENERATED       TIME_COMPLETED
                   6  11/21/2000 10:57:16  11/21/2000 10:57:41
                   7  11/21/2000 10:57:41  11/21/2000 10:57:43
                   8  11/21/2000 10:57:43  11/21/2000 10:57:49

In Data Guard Manager, this information is displayed on the Log Files property page.

8.1.9 SendQEntries (Send Queue Entries)

The SendQEntries property returns a table that shows all log files on the primary site that have not yet been successfully shipped to one or more standby sites. Query this property on a standby database resource. Query this property on the primary database resource. The table contains the following columns:

SITE_NAME

The value can be empty or it can contain the name of the site. 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 being written currently.
- 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 shipped to the standby site specified in the SITE_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.
LOG_SEQ

The log sequence number. Multiple rows may have the same LOG_SEQ value (for different SITE_NAME values).
TIME_GENERATED

The time when the log was generated.
TIME_COMPLETED

The time when the log was completed.

For example, the following shows output from a SHOW RESOURCE VERBOSE command:

DGMGRL> SHOW RESOURCE VERBOSE 'db' 'SendQEntries';
PRIMARY_SEND_QUEUE
SITE_NAME    STATUS              LOG_SEQ    TIME_GENERATED       TIME_COMPLETED
Standby      ARCHIVED             9         11/21/2001 10:57:49  11/21/2001 10:59:42
Standby      ARCHIVED            10         11/21/2001 10:59:42  11/21/2001 10:59:43
Standby      ARCHIVED            11         11/21/2001 10:59:43  11/21/2001 10:59:49
Standby      ARCHIVED            12         11/21/2001 10:59:49  11/21/2001 10:59:54
             CURRENT             13         11/21/2001 10:59:54

Note:

In Oracle9i Data Guard Manager, information from the SendQEntries property is displayed on the Log Files property page for the primary database resource.

8.2 Configurable Properties for Database Resources

The configurable properties include the following:

DbFileNameConvert

DelayMins

Dependency

LogArchiveFormat

LogArchiveMaxProcesses

LogArchiveMinSucceedDest

LogArchiveTrace

LogFileNameConvert

LogShipping

LogXptMode

LsbyASkipCfgPr

LsbyASkipErrorCfgPr

LsbyASkipTxnCfgPr

LsbyDSkipCfgPr

LsbyDSkipErrorCfgPr

LsbyDSkipTxnCfgPr

LsbyMaxEventsRecorded

LsbyMaxSga

LsbyMaxServers

LsbyRecordAppliedDdl

LsbyRecordSkipDdl

LsbyRecordSkipErrors

LsbyTxnConsistency

MaxFailure

ReopenSecs

StandbyArchiveDest

StandbyFileManagement

See Also:

Section 1.6.3 for more information about database property management

Note:

When a broker configuration is created and standby sites are added to the configuration, the broker imports existing settings for the database 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.

Alternate

Updates the ALTERNATE attribute for the LOG_ARCHIVE_DEST_n initialization parameter. With this property, you specify the name of the site to which log transport services should ship archived redo logs in case there is a problem shipping to the current site. The broker also updates the setting of the LOG_ARCHIVE_DEST_STATE_n initialization parameter to the specified ALTERNATE site.

Datatype	String
Valid Values	Site name (except for the primary site and the standby site itself)
Broker Default	Empty string
Imported?	No
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical and logical
Corresponds to	`ALTERNATE` attribute for the `LOG_ARCHIVE_DEST_``n` initialization parameter `ALTERNATE` column of the `V$ARCHIVE_DEST` view

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n and LOG_ARCHIVE_DEST_STATE_n values in the initialization parameter file for the primary database.

For example, if you are managing a configuration with the CLI you would issue the following SQL statement to set the standby site 'Chicago' to be an alternate site for the standby site 'San Francisco' with database 'reportingdb':

SQL> ALTER RESOURCE 'reportingdb' ON SITE 'San Francisco' SET PROPERTY   
  > 'Alternate' = 'Chicago';

ApplyNext

Specifies the number of archived redo logs that log apply services should apply immediately to the physical standby database, temporarily overriding any previously specified apply delay interval. 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 management of the standby database is disabled or if the log apply services are offline at the time that a value is specified.

Datatype	Integer
Valid Values	>=0 logs
Broker Default	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Physical
Corresponds to	`ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NEXT 2`

Note:

Oracle9i Data Guard Manager obtains information from the ApplyNext property and displays it on the Log Files property page for the standby database resource. The Log Files property page shows information about archived redo logs that have not been applied to the standby site.

ApplyNoDelay

Specifies whether or not to cancel the delay option that has been set on the primary database or on the standby database:

If log apply services are online and you set ApplyNoDelay=YES, then log apply services apply the archived redo logs as soon as they have been archived to the standby site. This property is equivalent to using the following SQL statement:
```
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY;
```
If log apply services are online and you set ApplyNoDelay=NO, then 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 statement:
```
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DEFAULT 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 mode of log apply services.

Datatype	String
Valid Values	`YES` or `NO`
Broker Default	NO
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Physical
Corresponds to	`YES=ALTER DATABASE RECOVER MANAGED STANDBY DATABASE NODELAY` `NO=ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DEFAULT DELAY`

The value of the ApplyNoDelay property persists through role changes. For example, if the ApplyNoDelay property is set to Yes and then the site 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.

ApplyParallel

Specifies the number of concurrent processes log apply services can use on the physical standby database for managed recovery. 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 mode of log apply services.

Datatype	Integer
Valid Values	>=1
Broker Default	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Physical
Corresponds to	`ALTER DATABASE RECOVER MANAGED STANDBY DATABASE PARALLEL...`

ArchiveLagTarget

Updates the ARCHIVE_LAG_TARGET initialization parameter setting. This 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.

Datatype	Number
Valid Values	Seconds (either 0 seconds, or any number from 60 to 7200 seconds)
Broker Default	0
Imported?	Yes, from the `ARCHIVE_LAG_TARGET` initialization parameter
Parameter Class	Dynamic
Role	Primary
Standby Type	Not applicable
Corresponds to	ARCHIVE_LAG_TARGET=`seconds` initialization parameter

AsyncBlocks

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.

Datatype	Integer
Valid Values	0 to 20,480 blocks
Broker Default	2048
Imported?	Yes, from the `ASYNCH_BLOCKS` column of the `V$ARCHIVE_DEST` view
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical and logical
Corresponds to	`ASYNC` attribute for the `LOG_ARCHIVE_DEST_``n` initialization parameter `ASYNCH_BLOCKS` column of the `V$ARCHIVE_DEST` view

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

Binding

Specifies whether or not the standby destination is mandatory or optional.

Datatype	String
Valid Values	`MANDATORY` or `OPTIONAL`
Broker Default	`OPTIONAL`
Imported?	Yes, from the `BINDING` column of the `V$ARCHIVE_DEST` view
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical and logical
Corresponds to	`MANDATORY` and `OPTIONAL` attributes for the `LOG_ARCHIVE_DEST_``n` initialization parameter `BINDING` column of the `V$ARCHIVE_DEST` view

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

DbFileNameConvert

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, you must add a corresponding file to the standby database. When the standby database is updated, this property converts the datafile name on the primary database to the datafile name on the standby database. The file on the standby database must exist and be writable, or the recovery process will halt with an error.

Datatype	String
Valid Values	Set the value of this parameter to two strings: The pattern found in the datafile names on the primary database The pattern found in the datafile names on the standby database `DB_FILE_NAME_CONVERT` = [(]'string1', 'string2', 'string3', 'string4',...[)] Where: string1 is the pattern of the primary database filename. string2 is the pattern of the standby database filename. string3 is the pattern of the primary database filename. string4 is the pattern of the standby database filename.
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

DelayMins

Specifies the number of minutes log apply services will delay applying the archived redo logs on the standby database.

Datatype	Integer
Valid Values	>= 0
Broker Default	`0`
Imported?	Yes, from the `DELAY_MINS` column of the `V$ARCHIVE_DEST` view
Parameter Class	Dynamic
Role	Standby
Standby Type	Physical and logical
Corresponds to	`DELAY` attribute for the `LOG_ARCHIVE_DEST_``n` initialization parameter `DELAY_MINS` column of the `V$ARCHIVE_DEST` view

Dependency

Specifies the dependency attribute for the LOG_ARCHIVE_DEST_n parameter. The site name (can be the primary or a standby site name) on which this site depends for receiving archived redo logs.

Datatype	String
Valid Values	Site name, except for the standby site itself or you can set this property to null.
Broker Default	Empty string
Imported?	No
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical or logical
Corresponds to	Dependency attribute for the `LOG_ARCHIVE_DEST_``n` initialization parameter

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

LogArchiveFormat

Specifies the format for filenames of archived redo log files.

Datatype	String
Valid Values	Same as for the `LOG_ARCHIVE_FORMAT` initialization parameter.
Broker Default	Empty string
Imported?	Yes, from the `LOG_ARCHIVE_FORMAT` initialization parameter
Parameter Class	Static
Role	Primary and standby
Standby Type	Physical and logical
Corresponds to	`LOG_ARCHIVE_FORMAT` initialization parameter

LogArchiveMaxProcesses

Specifies the number of archiver background processes (ARC0 through ARC9) the Oracle database server initially invokes. The actual number of archiver processes in use may vary subsequently based on archive workload.

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

LogArchiveMinSucceedDest

Defines the minimum number of destinations that must succeed for the online log file to be available for reuse.

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

LogArchiveTrace

Set this parameter to an integer value to see the progression of the archiving of redo logs on the primary and the standby sites. Oracle database server writes an audit trail of the archived logs received from the primary database into a trace file.

Datatype	Integer
Valid Values	The valid values have the following meanings: 0: Disable archivelog tracing 1: Track archival of redo log file 2: Track archival status of each archivelog destination 4: Track archival operational phase 8: Track archivelog destination activity 16: Track detailed archivelog destination activity 32: Track archivelog destination parameter modifications 64: Track ARCn process state activity 128: Track FAL (fetch archived log) server related activities 256: Supported in a future release 512: Tracks asynchronous LGWR activity 1024 RFS physical client tracking 2048 ARCn / RFS heartbeat tracking
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

LogFileNameConvert

Converts the filename of a new log file on the primary database to the filename of a log file on the standby database. If you add a log file to the primary database, you must add a corresponding file to the standby database.

Datatype	String
Valid Values	A list of an even number of strings, separated by commas. `LOG_FILE_NAME_CONVERT = [(]'string1', 'string2', 'string3', 'string4',...[)]` Where: `string1` is the pattern of the primary database filename `string2` is the pattern of the standby database filename `string3` is the pattern of the primary database filename `string4` is the pattern of the standby database filename
Broker Default	' ',' '
Imported?	Yes, from the `LOG_FILE_NAME_CONVERT` initialization parameter
Parameter Class	Static
Role	Standby
Standby Type	Physical standby
Corresponds to	LOG_FILE_NAME_CONVERT initialization parameter

LogShipping

Specifies whether or not log transport services can send archived redo logs to the particular standby database. The broker uses the value of the LogShipping property only when the primary database is in READ-WRITE-XPTON state:

If the primary database is in the READ-WRITE state, then log transport services are offline to all standby sites, regardless of whether or not the LogShipping property is set to on or off.
If the primary database is in READ-WRITE-XPTON state and the value of the LogShipping property is ON, then log transport services are enabled to send archived redo logs to the particular standby site. If the LogShipping property is OFF, then log transport services are disabled to send archived redo logs to the particular standby site.

Datatype	String
Valid Values	ON or OFF
Broker Default	ON
Imported?	No
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical and logical
Corresponds to	The ENABLE and DEFER values for the LOG_ARCHIVE_DEST_STATE_n initialization parameter

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

LogXptMode

Allows you to set the data protection mode for log transport services. You set the log transport services on each standby database to one of the following modes:

SYNC

Configures the log transport services to this standby using the LGWR, SYNC, AFFIRM settings. If this is a physical standby database, standby redo logs are required. If this is a logical standby database, standby redo logs are not required because logical standby databases do not use them. This mode provides the highest grade of data protection and potentially a correspondingly high impact on primary database performance.
ASYNC

Configures the log transport services to this standby using the LGWR, ASYNC, NOAFFIRM settings. Also, standby redo logs are required for physical standby databases; they are not required for logical standby databases. This mode provides the next highest grade of data protection with a correspondingly lower impact on primary database performance.

ARCH

Configures the log transport services to this standby database using the ARCH setting. Standby redo logs are not required. This is the default setting.

This mode provides the lowest grade of data protection and the least impact on primary database performance of the 3 options.

Datatype	String
Valid Values	SYNC or ASYNC or ARCH
Broker Default	ASYNC for logical standby databases ASYNC for physical standby databases with standby redo logs ARCH for physical standby databases without standby redo logs
Imported?	Yes, from the ARCHIVER, TRANSMIT_MODE, AFFIRM column of V$ARCHIVE_DEST view
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical or logical
Corresponds to	ARCH, LGWR, SYNC, ASYNC, AFFIRM, NOAFFIRM attributes for the LOG_ARCHIVE_DEST_n initialization parameter. ARCHIVER, TRANSMIT_MODE, AFFIRM column of V$ARCHIVE_DEST view

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

See Also:

Chapter 4 for more information about setting data protection modes for log transport services

LsbyASkipCfgPr

Provides a way to apply specific SQL statements and skip (ignore) SQL statements that you do not want applied to the logical standby database. The SKIP procedure:

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

This property is used only when you explicitly update its value. The property will not be reused when you enable the database for management by the broker.

Datatype	String
Valid Values	A valid set of arguments to the `DBMS_LOGSTDBY.SKIP` procedure.
Broker Default	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.SKIP procedure

Note:

Data Guard Manager uses the LsbySkipTable property to represent the LsbyASkipCfgPr, LsbyDSkipCfgPr, LsbyASkipErrorCfgPr, and LsbyDSkipErrorCfgPr properties.

LsbyASkipErrorCfgPr

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. This property is used only when you explicitly update its value. The property will not be reused when you enable the database for management by the broker.

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	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.SKIP_ERROR procedure

Note:

Data Guard Manager uses the LsbySkipTable property to represent the LsbyASkipCfgPr, LsbyDSkipCfgPr, LsbyASkipErrorCfgPr, and LsbyDSkipErrorCfgPr properties.

LsbyASkipTxnCfgPr

Skips over a transaction that caused the log apply services to stop applying transactions to the logical standby database. This property allows 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 take some corrective action, such as providing a compensating transaction. This will help avoid data divergence between the primary and logical standby databases that might result from skipping the problematic transaction. This property is used only when you explicitly update its value. The property will not be reused when you enable the database for management by the broker.

Datatype	String
Valid Values	A valid set of arguments to the `DBMS_LOGSTDBY.SKIP_TRANSACTION` procedure. Use comma separators between the arguments.
Broker Default	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.SKIP_TRANSACTION procedure

Note:

Data Guard Manager uses the LsbySkipTxnTable property to represent the LsbyASkipTxnCfgPr and LsbyDSkipTxnCfgPr properties.

LsbyDSkipCfgPr

Reverses 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 undone only by a matching number of unskip actions. You cannot undo multiple skip actions using wildcard characters. The property will not be reused when you enable the database for management by the broker.

Datatype	String
Valid Values	A valid set of arguments to the `DBMS_LOGSTDBY.UNSKIP` procedure
Broker Default	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.UNSKIP procedure

Note:

Data Guard Manager uses the LsbySkipTable property to represent the LsbyASkipCfgPr, LsbyDSkipCfgPr, LsbyASkipErrorCfgPr, and LsbyDSkipErrorCfgPr properties.

LsbyDSkipErrorCfgPr

Reverses or undoes 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 undone only by a matching number of unskip actions. You cannot undo multiple skip actions with just one unskip procedure call. The property will not be reused when you enable the database for management by the broker.

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	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.UNSKIP_ERROR procedure

Note:

Data Guard Manager uses the LsbySkipTable property to represent the LsbyASkipCfgPr, LsbyDSkipCfgPr, LsbyASkipErrorCfgPr, and LsbyDSkipErrorCfgPr properties.

LsbyDSkipTxnCfgPr

Reverses the actions of the LsbyASkipTxnCfgPr property. The transaction IDs must match exactly, and multiple skip transaction actions can be undone only by a matching number of unskip transaction actions. You cannot undo multiple skip transaction actions with just one unskip transaction procedure call. The property will not be reused when you enable the database for management by the broker.

Datatype	String
Valid Values	A valid set of arguments to the `DBMS_LOGSTDBY.UNSKIP_TRANSACTION` procedure
Broker Default	Not applicable
Imported?	No
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.UNSKIP_TRANSACTION procedure

Note:

Data Guard Manager uses the LsbySkipTxnTable property to represent the LsbyASkipTxnCfgPr and LsbyDSkipTxnCfgPr properties.

LsbyMaxEventsRecorded

Specifies the number of events that will be stored in the DBA_LOGSTDBY_EVENTS table, which stores logical standby event information.

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 standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('MAX_EVENTS_RECORDED')and the DBMS_LOGSTDBY.APPLY_UNSET('MAX_EVENTS_RECORDED')procedures

LsbyMaxSga

Specifies the number of megabytes for the system global area (SGA) allocation for log apply services cache. The default value is one quarter of the value set for the SHARED_POOL_SIZE initialization parameter.

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 standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('MAX_SGA')and the DBMS_LOGSTDBY.APPLY_UNSET('MAX_SGA')procedures

LsbyMaxServers

Specifies the number of parallel query servers specifically reserved for log apply services. By default, log apply services use all available parallel query servers to read the log files and apply changes.

Datatype	Integer
Valid Values	>=0
Broker Default	0
Imported?	Yes, from the `MAX_SERVERS` row of `system.LOGSTDBY$PARAMETERS`
Parameter Class	Not applicable
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('MAX_SERVERS')and the DBMS_LOGSTDBY.APPLY_UNSET('MAX_SERVERS')procedures

LsbyRecordAppliedDdl

Controls whether or not DDL statements that have been applied to the logical standby database are recorded in the DBA_LOGSTDBY_EVENTS table. Specify one of the following values:

TRUE: Indicates that DDL statements applied to the logical standby database are recorded in the DBA_LOGSTDBY_EVENTS table. This is the default parameter setting.

FALSE: Indicates that applied DDL statements are not recorded.

Datatype	String
Valid Values	`TRUE` or `FALSE` or `NULL`
Broker Default	NULL
Imported?	Yes, from the `RECORD_APPLIED_DDL` row of `system.LOGSTDBY$PARAMETERS`
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('RECORD_APPLIED_DDL')and the DBMS_LOGSTDBY.APPLY_UNSET('RECORD_APPLIED_DDL')procedures

LsbyRecordSkipDdl

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.

Datatype	String
Valid Values	`TRUE` or `FALSE` or `NULL`
Broker Default	NULL
Imported?	Yes, from the `RECORD_SKIP_DDL` row of `system.LOGSTDBY$PARAMETERS`
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('RECORD_SKIP_DDL')and the DBMS_LOGSTDBY.APPLY_UNSET('RECORD_SKIP_DDL')procedures

LsbyRecordSkipErrors

Controls whether 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.

Datatype	String
Valid Values	`TRUE` or `FALSE` or `NULL`
Broker Default	NULL
Imported?	Yes, from the `RECORD_SKIP_ERRORS` row of `system.LOGSTDBY$PARAMETERS`
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('RECORD_SKIP_ERRORS')and the DBMS_LOGSTDBY.APPLY_UNSET('RECORD_SKIP_ERRORS')procedures

LsbyTxnConsistency

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 results in the lowest 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 that are reading the logical standby database make no assumptions about transaction order, this option works well.

Datatype	String
Valid Values	`FULL` or `READ_ONLY` or `NONE`
Broker Default	None
Imported?	Yes, from the `TRANSACTION_CONSISTENCY` row of `system.LOGSTDBY$PARAMETERS`
Parameter Class	Not applicable
Role	Standby
Standby Type	Logical standby
Corresponds to	DBMS_LOGSTDBY.APPLY_SET('TRANSACTION_CONSISTENCY')and the DBMS_LOGSTDBY.APPLY_UNSET('TRANSACTION_CONSISTENCY')procedures

MaxFailure

Specifies the maximum number of contiguous archival failures before the log transport services stop trying to transport archived redo logs to the standby database. A value of zero indicates that an unlimited number of failures are allowed.

Datatype	Integer
Valid Values	>=0
Broker Default	0
Imported?	Yes, from the `MAX_FAILURE` column of `V$ARCHIVE_DEST` view
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical and logical
Corresponds to	`MAX_FAILURE` attribute for the `LOG_ARCHIVE_DEST_``n` initialization parameter `MAX_FAILURE` column of the `V$ARCHIVE_DEST` view

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

ReopenSecs

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.

Datatype	Integer
Valid Values	>=0 seconds
Broker Default	0
Imported?	Yes, from the `REOPEN_SECS` column of `V$ARCHIVE_DEST` view
Parameter Class	Dynamic
Role	Standby^{Foot 1}
Standby Type	Physical and logical
Corresponds to	`REOPEN` attribute for the `LOG_ARCHIVE_DEST_``n` initialization parameter `REOPEN_SECS` column of the `V$ARCHIVE_DEST` view

¹ Although this property is set for the standby database, it is indirectly related to the log transport services for the primary database. The broker reconciles the setting you specify on the standby database with the LOG_ARCHIVE_DEST_n value in the initialization parameter file for the primary database.

StandbyArchiveDest

Updates the file specification for the STANDBY_ARCHIVE_DEST initialization parameter. Specifies the location of archived redo logs arriving from a primary database. You can set this property to null.

Datatype	String
Valid Values	File specification of the location of archived redo logs on the standby site
Broker Default	0
Imported?	Yes, from the `STANDBY_ARCHIVE_DEST` initialization parameter
Parameter Class	Dynamic
Role	Standby
Standby Type	Physical or logical
Corresponds to	STANDBY_ARCHIVE_DEST initialization parameter

StandbyFileManagement

Updates the STANDBY_FILE_MANAGEMENT initialization parameter setting. Set this property on each standby site to indicate whether or not the filenames on the standby database are the same as those used on the primary database. Set this parameter to AUTO only if the COMPATIBILITY parameter is set to 9.0.n or higher.

Datatype	String
Valid Values	`AUTO` or `MANUAL`
Broker Default	MANUAL
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

8 Database Resource Properties

8.1 Monitorable (Read-Only) Properties for Database Resources

8.1.1 InconsistentLogXptProps (Inconsistent Log Transport Properties)

8.1.2 InconsistentProperties (Inconsistent Database Properties)

8.1.3 LogXptStatus (Log Transport Status)

8.1.4 LsbyFailedTxnInfo (Logical Standby Failed Transaction Information)

8.1.5 LsbyParameters (Logical Standby Parameters)

8.1.6 LsbySkipTable (Logical Standby Skip Table)

8.1.7 LsbySkipTxnTable (Logical Standby Skip Transaction Table)

8.1.8 SbyLogQueue (Standby Log Queue)

8.1.9 SendQEntries (Send Queue Entries)

8.2 Configurable Properties for Database Resources

Alternate

ApplyNext

ApplyNoDelay

ApplyParallel

ArchiveLagTarget

AsyncBlocks

Binding

DbFileNameConvert

DelayMins

Dependency

LogArchiveFormat

LogArchiveMaxProcesses

LogArchiveMinSucceedDest

LogArchiveTrace

LogFileNameConvert

LogShipping

LogXptMode

LsbyASkipCfgPr

LsbyASkipErrorCfgPr

LsbyASkipTxnCfgPr

LsbyDSkipCfgPr

LsbyDSkipErrorCfgPr

LsbyDSkipTxnCfgPr

LsbyMaxEventsRecorded

LsbyMaxSga

LsbyMaxServers

LsbyRecordAppliedDdl

LsbyRecordSkipDdl

LsbyRecordSkipErrors

LsbyTxnConsistency

MaxFailure

ReopenSecs

StandbyArchiveDest

StandbyFileManagement

8
Database Resource Properties