This parameter specifies the
media type of the secondary destination for logs that are archived
from either the current log path or the mirror log path.
- Configuration type
- Database
- Applies to
- Database servers with local and remote clients
- Clients
- Database servers with local clients
- Partitioned database servers with local and remote clients
- Parameter type
- Configurable online
- Default [range]
- OFF [DISK, TSM, VENDOR]
- OFF
- Specifies that the log archiving method is not used. If you set
both logarchmeth1 and logarchmeth2 configuration
parameters to OFF, the database is considered to
be using circular logging and is not rollforward recoverable. This
is the default.
- DISK
- You must follow this value with a colon (:) and then a fully qualified
existing path name where the log files will be archived. For example,
if you set the logarchmeth1 configuration parameter
to DISK:/u/dbuser/archived_logs the archive log
files are placed in the /u/dbuser/archived_logs/instance/dbname/nodename/chainid/ directory.
Note: If
you are archiving to tape, you can use the db2tapemgr utility
to store and retrieve log files.
- TSM
- If specified without any additional configuration parameters,
indicates that log files are archived on the local TSM server by using
the default management class. If you follow this option with a colon
(:) and a TSM management class, the log files are archived using the
specified management class.
- When archiving logs using TSM, before using the management
class that is specified by the database configuration parameter,
TSM attempts to bind the object to the management class that you specified
in the INCLUDE-EXCLUDE list in the TSM client options file. If a match
is not found, the default TSM management class that you specified
on the TSM server is used. TSM then rebinds the object to the management
class that you specified for the database configuration parameter.
Thus, the default management class and the management class that you
specify for the database configuration parameter must contain an
archive copy group, or the archive operation fails.
- VENDOR
- Specifies that a vendor library is used to archive the log files.
You must follow this value with a colon (:) and the name of the library.
The APIs in the library must use the backup and restore APIs for vendor
products.
- Notes:
- If you set either the logarchmeth1 or logarchmeth2 configuration
parameter to a value other than OFF, the database
is configured for rollforward recovery.
- If you use the userexit or logretain option
for the logarchmeth1 configuration parameter,
you must set the logarchmeth2 configuration parameter
to OFF.
- The
archive log path must not contain log files that do not belong to
the current database. If the archive log path was previously used
for a database of the same name, these log files must be removed before
using the current archive log path.
If you use the
logarchmeth2 configuration
parameter to specify a path, log files will be archived to both this
destination and the destination that is specified by the
logarchmeth1 database
configuration parameter. Which log files the
logarchmeth2 configuration
parameter archives depends on whether you also set the value of the
mirrorlogpath database
configuration parameter:
- If you do not set the value of the mirrorlogpath configuration
parameter, the logarchmeth2 configuration parameter
archives log files from the current log path, as specified by the logpath configuration
parameter.
- If you set the value of the mirrorlogpath configuration
parameter, the logarchmeth2 configuration parameter
archives log files from the mirror log path.