You can use this parameter to specify the media type of
the primary destination for archived logs.
- Configuration type
- Database
- Applies to
-
- Database server with local and remote clients
- Client
- Database server with local clients
- Partitioned database server with local and remote clients
- Parameter type
- Configurable Online
- Default [range]
- OFF [LOGRETAIN, USEREXIT, DISK, TSM, VENDOR]
The value that you set for the logarchmeth1 configuration
parameter is dependant on your database environment and your database
logging requirements.
- OFF
- Specifies that the log archiving method is not used. If both logarchmeth1 and logarchmeth2 are
set to OFF, the database uses circular logging and
is not rollforward recoverable.
- LOGRETAIN
- If this value is set for logarchmeth1, it
determines whether active log files are retained and available for
rollforward recovery. If logretain is set to RECOVERY or userexit is
set to ON, the active log files are retained and
become online archive log files for use in rollforward recovery. This
is called log retention logging.
- USEREXIT
- If this value is set for logarchmeth1, log
retention logging is performed. This parameter also indicates that
a user exit program should be used to archive and retrieve the log
files. Log files are archived when the log file is full. They are
retrieved when the ROLLFORWARD utility needs to use them to restore
a database.
- DISK
- This value must be followed by a colon(:) and then a fully qualified
existing path name where the log files are archived. For example,
if you set logarchmeth1 to DISK:/u/dbuser/archived_logs the
archive log files are placed in a directory called /u/dbuser/archived_logs/<instance>/<dbname>/<nodename>/<chainid>/.
- On
Windows operating systems, you must format the path name using UNC
disk addressing, such as \\u\dbuser\archived_logs\,
or drive letters, such as C:\u\dbuser\archived_logs.
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,
this value indicates that log files are archived on the local TSM
server using the default management class. If followed by 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 specified by the database configuration parameter,
TSM first attempts to bind the object to the management class specified
in the INCLUDE-EXCLUDE list found in the TSM client
options file. If a match is not found, the default TSM management
class specified on the TSM server is used. TSM then rebinds the object
to the management class specified by the database configuration parameter.
- Thus, the default management class, as well
as the management class specified by 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.
This value must be followed by a colon(:) and the name of the library.
The APIs provided in the library must use the backup and restore APIs
for vendor products.
Note: - If either logarchmeth1 or logarchmeth2 is
set to a value other than OFF, the database is configured
for rollforward recovery.
- If you update the userexit or logretain configuration
parameters logarchmeth1 is automatically updated
and vice versa. However, if you are using either userexit or logretain,
logarchmeth2 must be set 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.
DB2 Version 9.7 for Linux, UNIX, and Windows