1. Driveworks Configuration Specific Properties In Java

Oracle Data Guard broker provides various configuration and database properties that help you view and control the behavior of entire broker configurations, individual configuration members, redo transport services, and log apply services.Properties have either configuration-wide scope, database-wide scope, far sync instance-wide scope, or instance-specific scope. Configuration-wide properties control the behavior of the broker on all members of the configuration.

The values of such properties apply uniformly across all members of the configuration.Database-wide properties allow you to view or control the behavior of a specific database. If the database (primary or standby) is an Oracle RAC database consisting of multiple instances, the value of such a property applies uniformly across all instances of that database.Far sync instance-wide properties allow you to view or control the behavior of a far sync instance.Instance-specific properties allow you to view or control the behavior of an individual database instance. Such a property exists for all instances of an Oracle RAC database, but its value may differ from one specific instance to another.

Configuration properties control the behavior of the broker configuration. You can view and dynamically update the values of these properties using either DGMGRL or Cloud Control. However, some properties can only be updated through DGMGRL.A configuration property has configuration-wide scope; meaning that the value you set for the property applies uniformly to each member in the configuration.Configuration properties are set using the EDIT CONFIGURATION SET PROPERTY command, as shown in the following examples. The BystandersFollowRoleChange configuration property establishes whether bystander standby databases are evaluated during failover (value = ALL) or after failover (value = NONE).ALL - During the failover process, the broker determines whether the bystander standby databases are ahead of or behind the failover target standby (that is, the standby that will be the new primary).If the bystander standbys are ahead, they will be disabled with a status of ORA-16661 as part of the failover operation. The bystander standbys must be reinstated after failover completes. The broker reinstates a standby through a flashback to the SCN at which the target standby became a primary database, and sets up the redo transport configuration from the new primary to the standby.If the bystander standbys are behind, then the broker simply sets up the redo transport configuration from the soon-to-be-new-primary to these standbys and completes the failover process.NONE - During the failover process, the broker does NOT evaluate the status of the bystander standbys as part of the failover operation.

1. The configuration properties validator is created very early in the application’s lifecycle, and declaring the @Bean method as static lets the bean be created without having to instantiate the @Configuration class. Doing so avoids any problems that may be caused by early instantiation.
2. One of more common and straightforward solutions is a flexible use of properties files and the first class property support provided by Spring. As a proof of concept, for the purposes of this article, we’ll take a look at one specific type of property – the database configuration.

They are marked as disabled with a status of ORA-16661 so that they can be evaluated later. The broker simply completes the failover to produce a new primary database as soon as possible.After the failover is completed, you can reinstate the bystander standbys. During reinstatement of a bystander, the broker determines whether the bystander is ahead of, or behind, the new primary. If the bystander is ahead of the new primary, then the broker automatically flashes back the standby to the SCN at which the target standby became a primary database and sets up redo transport from the new primary to the standby. (Even if a flashback is not required, the broker sets up the redo transport configuration from the new primary to these standbys.)The NONE option decreases the processing time for failover, but disables broker management of all bystander databases in the configuration.

Application-dev.properties; application-qa.properties; application-production.properties, etc; To notify Spring which files to use, we have to set an environment variable - spring.profiles.active. So if the value of spring.profiles.active is dev, for an example, Spring boot will load the application-dev.properties file and likewise.

If fast-start failover is enabled, then the observer automatically reinstates the standby databases after failover has completed. Otherwise, you will have to manually reinstate the standby databases after failover has completed. Note:.The Externaldestination1 configuration property is available only in Oracle Database 11 g Release 2 (11.2.0.4) and in Oracle Database 12c Release 1 (12.1.0.2) and later.As of Oracle Database 12 c release 1 (12.1.0.2), the ExternalDestination1 configuration property supports Zero Data Loss Recovery Appliance (Recovery Appliance) as a redo transport destination.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 LOGARCHIVEDEST 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 LOGARCHIVEDEST n initialization parameter on the new primary database to ship redo data to the specified destination. Note:.The Externaldestination2 configuration property is available only in Oracle Database 11 g Release 2 (11.2.0.4) and in Oracle Database 12c Release 1 (12.1.0.2) and later.As of Oracle Database 12 c release 1 (12.1.0.2), the ExternalDestination2 configuration property supports Zero Data Loss Recovery Appliance (Recovery Appliance) as a redo transport destination.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 LOGARCHIVEDEST 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 LOGARCHIVEDEST n initialization parameter on the new primary database to ship redo data to the specified destination. 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 DBMSDG.INITIATEFSFAILOVER function. The FastStartFailoverPmyShutdown configuration property causes the primary database to shut down if fast-start failover is enabled and V$DATABASE.FSFAILOVERSTATUS 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 DBMSDG.INITIATEFSFAILOVER function.

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 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$FSOBSERVERHISTOGRAM view. This view displays statistics that are based on the frequency of successful pings between the observer and primary database for different time intervals.

(This view is available in Oracle Database 12 c Release 1 (12.1.0.2) and later. It is also available in Oracle Database 11 g Release 2 (11.2.0.4), but not in Oracle Database 12 c Release 1 (12.1.0.1).) See for a description of the V$FSOBSERVERHISTOGRAM view. CategoryDescriptionDatatypeIntegerValid valueIntegral number of seconds. Must be greater than, or equal to, 6.Broker default30 secondsImported?NoParameter classNot applicableRoleTarget standby database that is about to fail over to the primary roleStandby typeNot applicableCorresponds toNot applicableScopeBroker configuration. This property will be consumed by the observer after fast-start failover has been enabled.Cloud Control nameCloud Control presents this as 'Failover Threshold' on the Oracle Data Guard Overview page. 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. Note:The PrimaryLostWriteAction configuration property is available only in Oracle Database 11 g Release 2 (11.2.0.4) and in Oracle Database 12c Release 1 (12.1.0.2) and later.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 even if a standby database detects that a lost write has occurred at the primary database. This is the default action.SHUTDOWN - If a standby database detects that a lost write has occurred at the primary database, then fast start failover is disabled and the primary database performs a shutdown abort. Automatic failover will not occur.FAILOVER - If fast-start failover is enabled in maximum performance mode, and the configuration is within the acceptable limit specified for the FastStartFailoverLagLimit property, then the observer initiates a failover.

(The FAILOVER option is available only in Oracle Database 12 c Release 1 (12.1.0.2) and later.).FORCEFAILOVER - If fast-start failover is enabled (in either maximum performance or maximum availability mode), then the observer initiates a failover. This option results in a data loss failover. (The FORCEFAILOVER option is available only in Oracle Database 12 c Release 1 (12.1.0.2) and later.)For both the FAILOVER and FORCEFAILOVER options, if fast-start failover is disabled then no failover occurs, but the primary is shut down.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. Note:Information for monitorable properties can be seen only when broker management of the entity is enabled. Cloud Control displays the information obtained from these properties on the Property page.If the database is an Oracle RAC database, the output values of some properties may also show instance-specific information. For example if the primary database is an Oracle 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 monitorable properties:. The InconsistentLogXptProps monitorable 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.Although the properties reported in this table are database-specific or far sync instance-specific properties, the inconsistency is reported on an instance-specific basis. A database or far sync instance-specific property only ensures that there is one value in the broker's configuration file for all instances of the database or far sync instance, but the runtime values can be different. This means that a database or far sync instance-specific property may be inconsistent only on some instances.This property pertains to the primary database, a physical standby database that ships redo data, or a far sync instance.

The table contains the following columns:.INSTANCENAMEThe value identifying the SID for the instance.STANDBYNAMEThe database unique name ( DBUNIQUENAME) of the standby database or far sync instance to which this redo transport services property pertains.PROPERTYNAMEThe name of the redo transport services property with an inconsistent value.MEMORYVALUEThe runtime value being used in the database or far sync instance.BROKERVALUEThe value of the redo transport services property saved in the broker configuration file. The InconsistentProperties monitorable property returns a table that shows all properties whose values contained in the broker configuration file are inconsistent with the values in the corresponding server parameter file or the runtime values.Although the properties reported in this table are database-specific or far sync instance-specific properties, the inconsistency is reported on an instance-specific basis.

A database or far sync instance-specific property only ensures that there is one value in the broker's configuration file for all instances of the database or far sync instance, but the runtime values can be different. This means that a database or far sync instance-specific property may be inconsistent only on some instancesEach individual configuration member has this property. The table contains the following columns:.INSTANCENAMEThe value identifying the SID for the instance.PROPERTYNAMEThe name of the property with the inconsistent value.MEMORYVALUEThe corresponding runtime value being used.SPFILEVALUEThe corresponding value saved in the server parameter file (SPFILE).BROKERVALUEThe value of the property saved in the broker configuration file. The LogXptStatus monitorable property returns a table that contains the error status of redo transport services for each of the enabled configuration members.

This property pertains to the primary database, a physical standby database that ships redo data, or a far sync instance.The table contains the following columns:.PRIMARYINSTANCENAMEThe value identifying the SID for the instance on the primary database.STANDBYDATABASENAMEThe database unique name ( DBUNIQUENAME) of the standby database or far sync instance.ERRORThe 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 redo source to one redo destination.The error status can be an empty string, which indicates there is no error.In the following example, the STATUS from SouthSales is empty because there is no error for the SouthSales destination. The SouthReport destination returned the ORA-01034 message.DGMGRL SHOW DATABASE 'NorthSales' 'LogXptStatus';LOG TRANSPORT STATUSPRIMARYINSTANCENAME STANDBYDATABASENAME STATUSnorthsales1 SouthSalesnorthsales1 SouthReport ORA-01034: ORACLE not available. The LsbyFailedTxnInfo monitorable property identifies a failed transaction that caused log apply services to stop. This property contains a string with the following values from the DBALOGSTDBYEVENTS view:.XIDUSN: Transaction ID undo segment number.XIDSLT: Transaction ID slot number.XIDSQN: Transaction ID sequence number.STATUSCODE: 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 stoppedThe transaction IDs and status information are separated by a string of number signs (###).This property pertains to a logical standby database. The RecvQEntries monitorable 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:.STATUSThe STATUS column is set to one of the following values for a log file on a logical standby database:.NOTAPPLIED: No redo records in this log file have been applied.PARTIALLYAPPLIED: Some of the redo records in this log file have been applied while others have not.COMMITTEDTRANSACTIONSAPPLIED: 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. The SendQEntries monitorable 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:.STANDBYNAMEThe value can be empty or it can contain the database unique name ( DBUNIQUENAME) of a standby database. If empty, the STATUS column will contain a value of CURRENT or NOTARCHIVED.STATUSThe STATUS column is set to one of the following values:.CURRENT: A log file to which online redo is currently being written.NOTARCHIVED: 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 STANDBYNAME 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=NOTARCHIVED.RESETLOGSIDResetlogs identifier associated with the archived redo log file.THREADThe redo thread number.LOGSEQThe log sequence number. The TopWaitEvents monitorable property specifies the 5 events with the longest waiting time in the specified instance.

The events and their waiting time are retrieved from V$SYSTEMEVENT. 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:.EventThe system wait event.Wait TimeThe 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 northsales1 'TopWaitEvents';TOP SYSTEM WAIT EVENTSEvent Wait Timerdbms ipc message 671350SQL.Net message from client 62390pmon timer 47897Queue Monitor Wait 43016wakeup time manager 38508. Configurable properties control the behavior of broker configuration members. You can view and dynamically update the values of these properties using either DGMGRL or Cloud Control.

However, some properties can only be updated through DGMGRL.These properties control certain database initialization parameters and SQL statements that the broker uses to manage an Oracle Data Guard broker configuration. Therefore, you should not manually set those initialization parameters or issue those SQL statements on a broker configuration. See '.In most cases, the configurable property is said to apply to the entire member, meaning the value you set for the property applies to each instance of the member (that is, database or far sync instance).

However, in a few cases, the configurable property is said to have instance-specific scope which means that for a multiple-instance database or far sync instance, it is possible that the values of some particular properties may differ between instances. Lists each configurable property and indicates whether the scope of the property is member-wide or instance-specific. If the Scope column contains:.Member—The value of the property is database or far sync instance-wide, not instance or configuration specific.Instance—The value of the property is instance specific.If there is an asterisk (.) present, it indicates that the property value can be set for all instances of an Oracle RAC database using the EDIT INSTANCE. ON DATABASE command.Configuration—The value of the property is configuration wide, not instance or member specific.

The following database initialization parameters are controlled by broker configurable properties. Therefore, you should not set these parameters manually:.LOGARCHIVEDEST n.LOGARCHIVEDESTSTATE n.ARCHIVELAGTARGET.DBFILENAMECONVERT.LOGARCHIVEFORMAT.LOGARCHIVEMAXPROCESSES.LOGARCHIVEMINSUCCEEDDEST.LOGARCHIVETRACE.LOGFILENAMECONVERT.STANDBYFILEMANAGEMENTThe broker also uses configurable property settings to manage how apply is to be started. Therefore, the following SQL statements are managed automatically by the broker:.ALTER DATABASE RECOVER MANAGED STANDBY DATABASE.ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEThe broker sets the following apply parameters on a logical standby automatically; you should not manually set them:.MAXEVENTSRECORDED.MAXSERVERS.MAXSGA.PRESERVECOMMITORDER.RECORDAPPLIESDDL.RECORDSKIPDDL.RECORDSKIPERRORS.

CategoryDescriptionDatatypeStringValid values.AUTO—the number of parallel processes used for Redo Apply is automatically determined by Oracle based on the number of CPUs that the system has.NO—no parallel apply.2, 3, and so on—manually specify the number of parallel processes used for Redo Apply. (Specifying 0 is the same as specifying NO; specifying 1 is the same as specifying AUTO.)Broker defaultAUTOImported?NoParameter classNot applicableRoleStandbyStandby typePhysicalCorresponds to.AUTO corresponds to the PARALLEL clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement.NO corresponds to the NOPARALLEL clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement.2, 3, and so on corresponds to the PARALLEL n clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statementScopeDatabaseCloud Control nameNot applicable. CategoryDescriptionDatatypeStringValid values.MANDATORYYou can specify a policy for reuse of online redo log files using the MANDATORY value. If the archiving operation of a mandatory destination fails, online redo log files cannot be overwritten.OPTIONALYou can specify a policy for reuse of online redo log files using the OPTIONAL value. The DbFileNameConvert configurable property distinguishes physical standby datafile filenames from primary datafile filenames.

Note:When a database is added to the configuration, the broker sets the initial value of this property to the in-memory value of the DBFILENAMECONVERT initialization parameter. It is possible that the in-memory value and server parameter file (SPFILE) value of this parameter will differ. If you want to use the parameter's in-memory value, then enable the database and the broker will ensure that the SPFILE value of the parameter is set to the in-memory value. If you want to use the SPFILE value, then set the property value to be the parameter's value stored in the SPFILE.

Then enable the database. The DelayMins configurable 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;.Start SQL Apply on logical standby databases using the following SQL statement:ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE. The DGConnectIdentifier configurable property specifies the connection identifier the broker uses when making connections to a configuration member.

If using DGMGRL, you supply the value when you enter the CREATE CONFIGURATION, ADD DATABASE, or ADD FARSYNC command. If you are using Cloud Control, the value is supplied automatically. The connect identifier for a configuration member must:.Allow all other members in the configuration to reach it.Allow the member 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. CategoryDescriptionDatatypeStringValid valuesA connect identifier that can be used to connect to this databaseBroker defaultNot applicableImported?NoParameter classNot applicableRolePrimary, standby, far sync instanceStandby typePhysical, logical, or snapshot standby, or a far sync instanceCorresponds toSERVICENAME attribute of the LOGARCHIVEDEST n initialization parameter of the configuration member that is sending redo dataScopeDatabase, far sync instanceCloud Control nameNot applicable. CategoryDescriptionDatatypeStringValid valueDBUNIQUENAME of the database that is the target of the fast-start failover.Broker defaultIf only one physical or logical standby database exists, then the broker selects that as the default value for this property on the primary database when fast-start failover is enabled.If more than one physical or logical standby database exists, you must specify the FastStartFailoverTarget value explicitly, prior to enabling fast-start failover.

The indicated target is verified when fast-start failover is enabled.For the target standby database, the broker automatically selects the current primary database as the value for this property when fast-start failover is enabled.Imported?NoParameter classNot applicableRolePrimary or standbyStandby typePhysical or logicalCorresponds toNot applicableScopeDatabaseCloud Control nameCloud Control displays the value for the current primary database on the Oracle Data Guard Overview page, along with whether or not fast-start failover has been enabled. Note:When a member is added to the configuration, the broker sets the initial value of this property to the in-memory value of the LOGARCHIVEFORMAT initialization parameter. It is possible that the in-memory value and server parameter file (SPFILE) value of this parameter will differ.

If you want to use the parameter's in-memory value, then enable the member and the broker will ensure that the SPFILE value of the parameter is set to the in-memory value. If you want to use the SPFILE value, then set the property value to be the parameter's value stored in the SPFILE. Then enable the member.

CategoryDescriptionDatatypeStringValid values%d%t%s%rBroker defaultEmpty stringImported?Yes, from the LOGARCHIVEFORMAT initialization parameter on the primary databaseParameter classStaticRolePrimary, standby, far sync instanceStandby typePhysical, logical, or snapshot standby, or a far sync instanceCorresponds toLOGARCHIVEFORMAT initialization parameterScopeInstance (On an Oracle RAC database, you can use the EDIT INSTANCE. ON DATABASE command to have all instances use the same value for this property.)Cloud Control nameNot applicable.

Driveworks Configuration Specific Properties In Java

Note:When a database is added to the configuration, the broker sets the initial value of this property to the in-memory value of the LOGFILENAMECONVERT initialization parameter. It is possible that the in-memory value and server parameter file (SPFILE) value of this parameter will differ. If you want to use the parameter's in-memory value, then enable the database and the broker will ensure that the SPFILE value of the parameter is set to the in-memory value. If you want to use the SPFILE value, then set the property value to be the parameter's value stored in the SPFILE. Then enable the database. The broker uses the value of the LogShipping property when the primary database is in the TRANSPORT-ON state or when the physical standby or far sync instance forwards redo data to another member (physical, logical, or snapshot standby, or a far sync instance).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 configuration member. The LogXptMode configurable property enables you to set the redo transport service.

You set the redo transport services on each configuration member to one of the following modes:.SYNCConfigures redo transport services for this configuration member using the SYNC and AFFIRM attributes of the LOGARCHIVEDEST 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.ASYNCConfigures redo transport services for this configuration member using the ASYNC and NOAFFIRM attributes of the LOGARCHIVEDEST 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.FASTSYNCConfigures redo transport services for this configuration member using the SYNC and NOAFFIRM attributes of the LOGARCHIVEDEST n initialization parameter. This mode is only available in maximum availability protection mode.

Because FASTSYNC transport mode uses the NOAFFIRM attribute of the LOGARCHIVEDESTn parameter, data loss is possible. CategoryDescriptionDatatypeIntegerValid values=0Broker default0Imported?Yes, from the MAXSERVERS row of SYSTEM.LOGSTDBY$PARAMETERSParameter classDynamic; SQL Apply does not require restartRoleStandbyStandby typeLogicalCorresponds toDBMSLOGSTDBY.APPLYSET('MAXSERVERS') and the DBMSLOGSTDBY.APPLYUNSET('MAXSERVERS') proceduresScopeInstance (On an Oracle RAC database, you can use the EDIT INSTANCE. ON DATABASE command to have all instances use the same value for this property.)Cloud Control nameMax Servers.

CategoryDescriptionDatatypeIntegerValid values=0Broker default0Imported?Yes, from the MAXSGA row of SYSTEM.LOGSTDBY$PARAMETERSParameter classDynamic; SQL Apply does not require restartRoleStandbyStandby typeLogicalCorresponds toDBMSLOGSTDBY.APPLYSET('MAXSGA') and the DBMSLOGSTDBY.APPLYUNSET('MAXSGA') proceduresScopeInstance (On an Oracle RAC database, you can use the EDIT INSTANCE. ON DATABASE command to have all instances use the same value for this property.)Cloud Control nameMax SGA (MB). The LsbyPreserveCommitOrder configurable 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. CategoryDescriptionDatatypeIntegerValid values0, 15 to 1200Broker default30Imported?NoParameter classDynamicRolePrimary, standby, far sync instanceStandby typePhysical, logical, or snapshot standby, or a far sync instanceCorresponds to.NETTIMEOUT attribute of the LOGARCHIVEDEST n initialization parameter of the database or far sync instance that is sending redo data.NETTIMEOUT column of V$ARCHIVEDEST view of the database or far sync instance that is sending redo dataScopeDatabase, far sync instanceCloud Control nameNot applicable. CategoryDescriptionDatatypeStringValid ValuesA connect identifier that observer can use to connect to this databaseBroker DefaultEmpty StringImported?NoParameter ClassNot applicableRolePrimary and StandbyStandby TypePhysical or logicalCorresponds toNot applicableScopeDatabaseCloud Control nameObserver Connect IdentifierFootnote 8When 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. By default, a primary database sends the redo that it generates to every other redo transport destination in the configuration. You can use the RedoRoutes property to create a more complex redo transport topology, such as one in which a physical standby database or a far sync instance forwards redo received from the primary database to one or more destinations, or one in which the redo transport mode used for a given destination is dependent on which database is in the primary role.The RedoRoutes property is set to a character string that contains one or more redo routing rules. Each rule contains one or more redo sources and one or more redo destinations.

A redo routing rule becomes active when one of the redo sources in the rule is in the primary role. This results in redo from the primary database being sent to every redo destination in that rule. CategoryDescriptionDatatypeStringValid valuesA character string that contains one or more redo routing rules, each contained within a pair of parentheses:(redoroutingrule 1) (redoroutingrule n)See ' for more information about redo routing rules.Broker defaultNullImported?NoParameter classNot applicableRolePrimary, standby, far sync instanceStandby typePhysical standby and far sync instanceCorresponds toLOGARCHIVEDEST nScopeDatabase, far sync instanceCloud Control NameRedoRoutes. CategoryDescriptionDatatypeStringValid valuesNonempty file specification of the location of archived redo log files on the database or far sync instance. Specify USEDBRECOVERYFILEDEST if a database recovery area is desired.Broker defaultdgsby dbuniquenameImported?Yes, from the DESTINATION column of the V$ARCHIVEDEST fixed view of the standby database or far sync instance where the destination is a local destination and where the VALIDFOR attribute is compatible with the string (STANDBYROLE, STANDBYLOGFILE); if no such destination exists, import is from the STANDBYARCHIVEDEST initialization parameter. Note that the STANDBYARCHIVEDEST parameter has been deprecated and is supported for backward compatibility only.Parameter classDynamicRoleStandby database or far sync instanceStandby typePhysical, logical, or snapshot standby, or a far sync instanceCorresponds to.LOCATION attribute of the LOGARCHIVEDEST n initialization parameter of the standby database or far sync instance with VALIDFOR compatible with (STANDBYROLE, STANDBYLOGFILE).DESTINATION column of the V$ARCHIVEDEST view of the standby databaseScopeInstanceCloud Control nameStandby Archive Location.

The StandbyFileManagement configurable 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 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 Data Guard Broker PropertiesThis chapter describes the various configuration and database properties that help you view and control the behavior of entire broker configurations, individual databases, redo transport services, and log apply services.This chapter discusses the following topics:.Properties have either configuration-wide scope, database-wide scope, or instance-specific scope. Configuration-wide properties control the behavior of the broker on all databases in the configuration. The values of such properties apply uniformly across all databases in the configuration.Database-wide properties allow you to view or control the behavior of a specific database. If the database (primary or standby) is an Oracle RAC database consisting of multiple instances, the value of such a property applies uniformly across all instances of that database.Instance-specific properties allow you to view or control the behavior of an individual database instance. Such a property exists for all instances of an Oracle 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 Data Guard command-line interface (DGMGRL). Using DGMGRL, the properties described in this chapter may be viewed or modified using discrete DGMGRL commands.Enterprise Manager explicitly presents some of these properties on the Edit Properties page. Information from other properties may be implicitly incorporated into other Web pages displayed by Enterprise Manager. Each property's description in this chapter indicates how Enterprise Manager presents that property.

8.1 Configuration PropertiesConfiguration properties control the behavior of the broker configuration. You can view and dynamically update the values of these properties using either DGMGRL or Enterprise Manager. However, some properties can only be updated through DGMGRL.A configuration property has configuration-wide scope; meaning that the value you set for the property applies uniformly to each database in the configuration.The following sections describe the configuration properties:. 8.1.1 BystandersFollowRoleChangeThe 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.5 FastStartFailoverAutoReinstateThe 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 DBMSDG.INITIATEFSFAILOVER function. 8.1.7 FastStartFailoverPmyShutdownThe FastStartFailoverPmyShutdown configuration property causes the primary database to shut down if fast-start failover is enabled and V$DATABASE.FSFAILOVERSTATUS 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 DBMSDG.INITIATEFSFAILOVER function. 8.1.8 FastStartFailoverThresholdThe 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 in 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$FSOBSERVERHISTOGRAM 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 for a description of the V$FSOBSERVERHISTOGRAM view.). CategoryDescriptionDatatypeIntegerValid valueIntegral number of seconds. Must be greater than, or equal to, 6.Broker default30 secondsImported?NoParameter classNot applicableRoleTarget standby database that is about to fail over to the primary roleStandby typeNot applicableCorresponds toNot applicableScopeBroker configuration.

This property will be consumed by the observer after fast-start failover has been enabled.Enterprise Manager nameOracle Enterprise Manager presents this as 'Failover Threshold' on the Data Guard Overview page. 8.1.10 ObserverReconnectThe 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 11 g Release 2 (11.2.0.4) and higher. 8.1.12 PrimaryLostWriteActionThe 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. 8.1.13 TraceLevelThe 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 11 g Release 2 (11.2.0.3) and higher.

Note:Information for monitorable properties can be seen only when broker management of the database is enabled. Enterprise Manager displays the information obtained from these properties on the Property page.If the database is an Oracle RAC database, the output values of some properties may also show instance-specific information. For example if the primary database is an Oracle 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 monitorable database properties:. 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:.INSTANCENAMEThe value identifying the SID for the instance.STANDBYNAMEThe database unique name ( DBUNIQUENAME) of the standby database to which this redo transport services property pertains.PROPERTYNAMEThe name of the redo transport services property with an inconsistent value.MEMORYVALUEThe runtime value being used in the database.BROKERVALUEThe 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:.INSTANCENAMEThe value identifying the SID for the instance.PROPERTYNAMEThe name of the database property with the inconsistent value.MEMORYVALUEThe corresponding runtime value being used in the database.SPFILEVALUEThe corresponding value saved in the server parameter file (SPFILE).BROKERVALUEThe 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:.PRIMARYINSTANCENAMEThe value identifying the SID for the instance on the primary database.STANDBYDATABASENAMEThe database unique name ( DBUNIQUENAME) of the standby database.ERRORThe 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 SouthSales is empty because there is no error for the SouthSales destination. The SouthReport destination returned the ORA-01034 message.DGMGRL SHOW DATABASE 'NorthSales' 'LogXptStatus';LOG TRANSPORT STATUSPRIMARYINSTANCENAME STANDBYDATABASENAME STATUSnorthsales1 SouthSalesnorthsales1 SouthReport 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 DBALOGSTDBYEVENTS view:.XIDUSN: Transaction ID undo segment number.XIDSLT: Transaction ID slot number.XIDSQN: Transaction ID sequence number.STATUSCODE: 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 stoppedThe transaction IDs and status information are separated by a string of number signs (###).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 DBALOGSTDBYSKIP view:.ERRORIndicates if the statement should be skipped ( Y) or if errors should be returned for the statement ( N).STATEMENTOPTIndicates the type of statement that should be skipped.SCHEMAThe schema name for which this skip option should be used.NAMEName of the object for which this skip option should be used.PROCEDUREName of the stored procedure to execute when processing the skip optionThis property pertains to a logical standby database.

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:.STATUSThe STATUS column is set to one of the following values for a log file on a logical standby database:.NOTAPPLIED: No redo records in this log file have been applied.PARTIALLYAPPLIED: Some of the redo records in this log file have been applied while others have not.COMMITTEDTRANSACTIONSAPPLIED: 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. 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:.STANDBYNAMEThe value can be empty or it can contain the database unique name ( DBUNIQUENAME) of a standby database. If empty, the STATUS column will contain a value of CURRENT or NOTARCHIVED.STATUSThe STATUS column is set to one of the following values:.CURRENT: A log file to which online redo is currently being written.NOTARCHIVED: 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 STANDBYNAME 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=NOTARCHIVED.RESETLOGSIDResetlogs identifier associated with the archived redo log file.THREADThe redo thread number.LOGSEQThe log sequence number. 8.2.10 TopWaitEventsThe 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$SYSTEMEVENT. 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:.EventThe system wait event.Wait TimeThe 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 northsales1 'TopWaitEvents';TOP SYSTEM WAIT EVENTSEvent Wait Timerdbms ipc message 671350SQL.Net message from client 62390pmon timer 47897Queue Monitor Wait 43016wakeup time manager 38508. 8.3 Configurable Database PropertiesConfigurable database properties control the behavior of databases in a broker configuration. You can view and dynamically update the values of these properties using either DGMGRL or Enterprise Manager.

However, some properties can only be updated through DGMGRL.In most cases, the configurable database property is said to have database-wide 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-specific 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. 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 or configuration specific.Instance—The value of the property is instance specific, not database or configuration specific.If there is an asterisk (.) present, it indicates that the property value can be set for all instances of an Oracle RAC database using the EDIT INSTANCE. ON DATABASE command.Configuration—The value of the property is configuration wide, not instance or database specific. CategoryDescriptionDatatypeStringValid values.

Jun 29, 2016  Download Critical Ops: Multiplayer FPS and enjoy it on your iPhone, iPad and iPod touch. ‎Critical Ops is a 3D MULTIPLAYER FPS build for mobile. Experience action, where fast reflexes and TACTICAL skills are essential to success. Are you ready for the most skill-based mobile FPS? Requires iOS 10.0 or later. Compatible with iPhone, iPad. Oct 19, 2016  Download Critical Ops: Multiplayer FPS and enjoy it on your iPhone, iPad, and iPod touch. ‎Critical Ops is a 3D MULTIPLAYER FPS build for mobile. Experience action, where fast reflexes and TACTICAL skills are essential to success. Are you ready for the most skill-based mobile FPS? Best game on iOS but(edited). IOS for C-ops Hack. Whether you are looking to avoid cheaters or cheat yourself, knowing where most the hackers are is always useful to know. Without a doubt most of the Critical Ops hackers will be found on the Android version of the game, since Android has all the interesting cheating tools readily available and a huge modding. May 03, 2016  Critical Ops is a 3D MULTIPLAYER FPS build for mobile. Experience action, where fast reflexes and TACTICAL skills are essential to success. Are you ready for the most skill-based mobile FPS? Critical Ops is a first-person shooter that features competitive combat through beautifully crafted maps and challenging game modes. Download and install latest version of Critical Ops app for free at Freepps.top. Ratings, user reviews, direct apk files get links, update history.

AUTO—the number of parallel processes used for Redo Apply is automatically determined by Oracle based on the number of CPUs that the system has.NO—no parallel apply.2, 3, and so on—manually specify the number of parallel processes used for Redo Apply. (Specifying 0 is the same as specifying NO; specifying 1 is the same as specifying AUTO.)Broker defaultAUTOImported?NoParameter classNot applicableRoleStandbyStandby typePhysicalCorresponds to. AUTO corresponds to the PARALLEL clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement.NO corresponds to the NOPARALLEL clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement.2, 3, and so on corresponds to the PARALLEL n clause of the ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statementScopeDatabaseEnterprise Manager nameNot applicable. CategoryDescriptionDatatypeStringValid values.

MANDATORYYou can specify a policy for reuse of online redo log files using the MANDATORY value. If the archiving operation of a mandatory destination fails, online redo log files cannot be overwritten.OPTIONALYou can specify a policy for reuse of online redo log files using the OPTIONAL value. 8.3.7 DbFileNameConvertThe DbFileNameConvert configurable database property d istinguishes physical standby datafile filenames from primary datafile filenames.

Note:When a database is added to the configuration, the broker sets the initial value of this property to the in-memory value of the DBFILENAMECONVERT initialization parameter. It is possible that the in-memory value and server parameter file (SPFILE) value of this parameter will differ. If you want to use the parameter's in-memory value, then enable the database and the broker will ensure that the SPFILE value of the parameter is set to the in-memory value. If you want to use the SPFILE value, then set the property value to be the parameter's value stored in the SPFILE. Then enable the database.

8.3.8 DelayMinsThe DelayMins configurable database property s pecifies 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.

8.3.9 DGConnectIdentifierThe 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. CategoryDescriptionDatatypeStringValid valueDBUNIQUENAME of the database that is the target of the fast-start failover.Broker defaultIf only one physical or logical standby database exists, then the broker selects that as the default value for this property on the primary database when fast-start failover is enabled.If more than one physical or logical standby database exists, you must specify the FastStartFailoverTarget value explicitly, prior to enabling fast-start failover.

The indicated target is verified when fast-start failover is enabled.For the target standby database, the broker automatically selects the current primary database as the value for this property when fast-start failover is enabled.Imported?NoParameter classNot applicableRolePrimary or standbyStandby typePhysical or logicalCorresponds toNot applicableScopeDatabaseEnterprise Manager nameEnterprise Manager displays the value for the current primary database on the Data Guard Overview page, along with whether or not fast-start failover has been enabled. Note:When a database is added to the configuration, the broker sets the initial value of this property to the in-memory value of the LOGARCHIVEFORMAT initialization parameter. It is possible that the in-memory value and server parameter file (SPFILE) value of this parameter will differ. If you want to use the parameter's in-memory value, then enable the database and the broker will ensure that the SPFILE value of the parameter is set to the in-memory value.

If you want to use the SPFILE value, then set the property value to be the parameter's value stored in the SPFILE. Then enable the database. CategoryDescriptionDatatypeStringValid values%d%t%s%rBroker defaultEmpty stringImported?Yes, from the LOGARCHIVEFORMAT initialization parameter on the primary databaseParameter classStaticRolePrimary and standbyStandby typePhysical, logical, or snapshotCorresponds toLOGARCHIVEFORMAT initialization parameterScopeInstance (On an Oracle RAC database, you can use the EDIT INSTANCE. ON DATABASE command to have all instances use the same value for this property.)Enterprise Manager nameNot applicable. Note:When a database is added to the configuration, the broker sets the initial value of this property to the in-memory value of the LOGFILENAMECONVERT initialization parameter. It is possible that the in-memory value and server parameter file (SPFILE) value of this parameter will differ. If you want to use the parameter's in-memory value, then enable the database and the broker will ensure that the SPFILE value of the parameter is set to the in-memory value.

If you want to use the SPFILE value, then set the property value to be the parameter's value stored in the SPFILE. Then enable the database. 8.3.16 LogShippingThe 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.

CategoryDescriptionDatatypeStringValid valuesON or OFFBroker defaultONImported?NoParameter classDynamicRoleStandbyStandby typePhysical, logical, or snapshotCorresponds toENABLE and DEFER values for the LOGARCHIVEDESTSTATE n initialization parameter of the primary databaseScopeDatabaseEnterprise Manager nameLog ShippingFootnote 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 LOGARCHIVEDESTn value of the primary database. 8.3.17 LogXptModeThe 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:.SYNCConfigures redo transport services for this standby database using the SYNC and AFFIRM attributes of the LOGARCHIVEDEST 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.ASYNCConfigures redo transport services for this standby database using the ASYNC and NOAFFIRM attributes of the LOGARCHIVEDEST 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. 8.3.18 LsbyASkipCfgPrThe 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 necessarySpecifying a value for this property has no effect and will be ignored if management of the standby database is disabled. 8.3.20 LsbyASkipTxnCfgPrThe 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 LsbyDSkipCfgPrThe LsbyDSkipCfgPr configurable database property deletes an existing skip specification from SQL Apply. It reverses or removes the actions of the 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 LsbyDSkipErrorCfgPrThe LsbyDSkipErrorCfgPr configurable database property deletes an existing skip error specification from SQL Apply. It reverses or removes the actions of the 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 LsbyDSkipTxnCfgPrThe LsbyDSkipTxnCfgPr configurable database property reverses or removes the actions of the 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. CategoryDescriptionDatatypeIntegerValid values=0Broker default0Imported?Yes, from the MAXSGA row of SYSTEM.LOGSTDBY$PARAMETERSParameter classDynamic; SQL Apply does not require restartRoleStandbyStandby typeLogicalCorresponds toDBMSLOGSTDBY.APPLYSET('MAXSGA') and the DBMSLOGSTDBY.APPLYUNSET('MAXSGA') proceduresScopeInstance (On an Oracle RAC database, you can use the EDIT INSTANCE. ON DATABASE command to have all instances use the same value for this property.)Enterprise Manager nameMax SGA (MB). CategoryDescriptionDatatypeIntegerValid values=0Broker default0Imported?Yes, from the MAXSERVERS row of SYSTEM.LOGSTDBY$PARAMETERSParameter classDynamic; SQL Apply does not require restartRoleStandbyStandby typeLogicalCorresponds toDBMSLOGSTDBY.APPLYSET('MAXSERVERS') and the DBMSLOGSTDBY.APPLYUNSET('MAXSERVERS') proceduresScopeInstance (On an Oracle RAC database, you can use the EDIT INSTANCE.

ON DATABASE command to have all instances use the same value for this property.)Enterprise Manager nameMax Servers. 8.3.27 LsbyPreserveCommitOrderThe 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. CategoryDescriptionDatatypeIntegerValid values0, 15 to 1200Broker default30Imported?Yes, from the NETTIMEOUT column of V$ARCHIVEDEST view of the primary databaseParameter classDynamicRolePrimary and StandbyStandby typePhysical, logical, or snapshotCorresponds to. NETTIMEOUT attribute of the LOGARCHIVEDEST n initialization parameter of the primary database.NETTIMEOUT column of V$ARCHIVEDEST view of the primary databaseScopeDatabaseEnterprise Manager nameNot applicable.

CategoryDescriptionDatatypeStringValid ValuesA connect identifier that observer can use to connect to this databaseBroker DefaultEmpty StringImported?NoParameter ClassNot applicableRolePrimary and StandbyStandby TypePhysical or logicalCorresponds toNot applicableScopeDatabaseEnterprise Manager nameObserver Connect IdentifierFootnote 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. CategoryDescriptionDatatypeStringValid valuesNonempty file specification of the location of archived redo log files on the standby database. Use DBRECOVERYFILEDEST if a database recovery area is desired.Broker defaultdgsby dbuniquenameImported?Yes, from the DESTINATION column of the V$ARCHIVEDEST fixed view of the standby database where the destination is a local destination and where the VALIDFOR attribute is compatible with the string (STANDBYROLE, STANDBYLOGFILE); if no such destination exists, import is from the STANDBYARCHIVEDEST initialization parameter. Note that the STANDBYARCHIVEDEST parameter has been deprecated and is supported for backward compatibility only.Parameter classDynamicRoleStandbyStandby typePhysical, logical, or snapshotCorresponds to. LOCATION attribute of the LOGARCHIVEDEST n initialization parameter of the standby database with VALIDFOR compatible with (STANDBYROLE, STANDBYLOGFILE).DESTINATION column of the V$ARCHIVEDEST view of the standby databaseScopeInstanceEnterprise Manager nameStandby Archive Location.

8.3.40 StandbyFileManagementThe 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.42 TransportDisconnectedThresholdThe 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 11 g Release 2 (11.2.0.4) and higher. 8.3.43 TransportLagThresholdThe 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 11 g Release 2 (11.2.0.4) and higher.