LOG_ARCHIVE_TRACE

Property	Description
Parameter type	Integer
Default value	0
Modifiable	ALTER SYSTEM
Range of values	0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192
Basic	No
Real Application Clusters	Multiple instances can have different values.

LOG_ARCHIVE_TRACE controls output generated by the archivelog process.

This process can be initiated by any of the following:

· An ARCn background process (designated as ARCn in the output logs)

· An explicit session-invoked foreground process (designated as ARCH in the output logs)

The valid values have the following meanings:

· 0: Disable archivelog tracing (this is the default)

· 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: Track RFS Logical Client

· 512: Track LGWR redo shipping network activity

· 1024: Track RFS Physical Client

· 2048: Track RFS/ARCn Ping Heartbeat

· 4096: Track Real Time Apply

· 8192: Track Redo Apply (Media Recovery or Physical Standby)

You can combine tracing levels by adding together the values of the desired tracing levels. For example, a setting of 3 will generate level 1 and level 2 trace output. You can set different values for the primary and standby database.

When this parameter is set to the default value of 0, Oracle will still generate appropriate alert and trace entries in response to error conditions. If you change the value of this parameter dynamically in an ALTER SYSTEM statement, the changes will take effect at the start of the next archivelog operation.

Note:

1. This parameter was introduced in 8.1.6.

2. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘LOG_ARCHIVE_TRACE’;

NAME	VALUE	IS DEFAULT	ISSES_ MODIFIABLE	ISSYS_ MODIFIABLE	ISINSTANCE_ MODIFIABLE	IS DEPRECATED	DESCRIPTION
log_archive_trace	0	TRUE	FALSE	IMMEDIATE	TRUE	FALSE	Establish archivelog operation tracing level

Oracle initializatoin parameters

LOG_ARCHIVE_MIN_SUCCEED_DEST

Property	Description
Parameter type	Integer
Default value	1
Modifiable	ALTER SESSION, ALTER SYSTEM
Range of values	1 to 10 if you are using LOG_ARCHIVE_DEST_n 1 or 2 if you are using LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST
Basic	No

LOG_ARCHIVE_MIN_SUCCEED_DEST defines the minimum number of destinations that must succeed in order for the online logfile to be available for reuse.

· If you are using the LOG_ARCHIVE_DEST_n parameters and automatic archiving is enabled, then the value of this parameter cannot exceed either of the following:

- The total number of destinations

- The number of enabled, valid destinations specified as MANDATORY plus the number of enabled, valid non-standby destinations specified as OPTIONAL

· If you are using LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST and automatic archiving is enabled, a value of 1 specifies that the destination specified in LOG_ARCHIVE_DEST must succeed. A value of 2 specifies that the destinations specified in both parameters must succeed.

If the value of this parameter is less than the number of enabled, valid MANDATORY destinations, this parameter is ignored in favor of the MANDATORY destination count. If the value is more than the number of enabled, valid MANDATORY destinations, some of the enabled, valid OPTIONAL non-standby destinations are treated as MANDATORY.

You can switch dynamically from using the older parameters to the LOG_ARCHIVE_DEST_n parameter using ALTER SYSTEM, as follows:

1. Set LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.

2. Set the value of LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST to the null string.

3. Set the desired number of destinations for the LOG_ARCHIVE_DEST_n parameters.

4. Reset LOG_ARCHIVE_MIN_SUCCEED_DEST to the desired value.

Note:

1. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘LOG_ARCHIVE_MIN_SUCCEED_DEST’;

NAME	VALUE	IS DEFAULT	ISSES_ MODIFIABLE	ISSYS_ MODIFIABLE	ISINSTANCE_ MODIFIABLE	IS DEPRECATED	DESCRIPTION
log_archive_min_succeed_dest	1	TRUE	TRUE	IMMEDIATE	TRUE	FALSE	minimum number of archive destinations that must succeed

Oracle initializatoin parameters

LOG_ARCHIVE_MAX_PROCESSES

Thank you for visiting Spatial DBA - Oracle and ArcSDE.

I have stopped updating the blog.

Please visit Oracle DBA Tips (http://www.oracledbatips.com) for more Oracle DBA Tips.

========================================================================

Property	Description
Parameter type	Integer
Default value	4
Modifiable	ALTER SYSTEM
Range of values	1 to 30
Basic	No

LOG_ARCHIVE_MAX_PROCESSES specifies the number of archiver background processes (ARC0 through ARCn) Oracle initially invokes.

· If the LOG_ARCHIVE_START initialization parameter has the value true, then this value is evaluated at instance startup. Note that the LOG_ARCHIVE_START initialization parameter was deprecated as of Oracle Database 10g Release 1 (10.1).

· Otherwise, this parameter is evaluated when the archiver process is first invoked by SQL*Plus or SQL syntax.

The actual number of archiver processes in use may vary subsequently based on archive workload.
Note:
1. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘LOG_ARCHIVE_MAX_PROCESSES’;

NAME	VALUE	IS DEFAULT	ISSES_ MODIFIABLE	ISSYS_ MODIFIABLE	ISINSTANCE_ MODIFIABLE	IS DEPRECATED	DESCRIPTION
log_archive_max_processes	10	FALSE	FALSE	IMMEDIATE	TRUE	FALSE	maximum number of active ARCH processes

Oracle initializatoin parameters

LOG_ARCHIVE_LOCAL_FIRST

Property	Description
Parameter type	Boolean
Default value	true
Modifiable	ALTER SYSTEM
Range of values	true | false
Basic	No

Note:

The LOG_ARCHIVE_LOCAL_FIRST parameter is deprecated. It is retained for backward compatibility only.

LOG_ARCHIVE_LOCAL_FIRST specifies when the archiver processes (ARCn) transmit redo data to remote standby database destinations.

Values:

· true

Directs the ARCn process to transmit redo data after the online redo log file has been completely and successfully archived to at least one local destination. This is the default value.

Because the online redo log files are archived locally first, the LGWR process reuses the online redo log files much earlier than would be possible if the ARCn processes archived to the standby database concurrently with the local destination. This behavior is useful when archiving to remote destinations that use a slow network connection, such as a long-distance wide area network (WAN).

· false

Directs the ARCn process to transmit redo data at the same time the online redo log file is archived to the local destinations. This results in redo data being promptly dispatched to the remote standby database destination.

Setting LOG_ARCHIVE_LOCAL_FIRST to false is most useful for faster network connections, such as high-speed local area networks (LAN).

If LOG_ARCHIVE_LOCAL_FIRST is set to true, then it is not used on a physical standby database and any database for which the following attributes have been specified in the LOG_ARCHIVE_DEST_n initialization parameter:

· MANDATORY

· LOCAL

· DEPENDENCY (or any database destination that is the target of a DEPENDENCY attribute)

If LOG_ARCHIVE_LOCAL_FIRST is set to true, then it is ignored during certain operations, such as during a switchover, which requires synchronized archival operations. If the destination was explicitly configured to use the log writer process (by specifying the LGWR attribute in the LOG_ARCHIVE_DEST_n initialization parameter), but for some reason the log writer process becomes unable to archive to the destination, then Data Guard will revert to using the ARCn process to complete archival operations using the default behavior, even if LOG_ARCHIVE_LOCAL_FIRST is set to false.

For example, if a standby database problem or a network problem causes the LGWR process to fail, then the ARCn process will complete the archival. Data Guard minimizes the effect on the primary database as much as possible by archiving to the local destination first to ensure the online redo log files are available to the LGWR process as quickly as possible.

2. This parameter was introduced in 10g.

3. Query for the current value of the parameter

select name, value, isdefault, isses_modifiable, issys_modifiable,

isinstance_modifiable, isdeprecated, description

from v$parameter

where upper(name) = ‘LOG_ARCHIVE_LOCAL_FIRST’;

NAME	VALUE	IS DEFAULT	ISSES_ MODIFIABLE	ISSYS_ MODIFIABLE	ISINSTANCE_ MODIFIABLE	IS DEPRECATED	DESCRIPTION
log_archive_local_first	TRUE	TRUE	FALSE	IMMEDIATE	TRUE	FALSE	Establish EXPEDITE attribute default value

Oracle initializatoin parameters