You can use this parameter to
specify the media type of the primary destination for logs that are
archived from the current 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 [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, which is the default, the database uses
circular logging and is not rollforward recoverable.
- LOGRETAIN
- Specifies that active log files are retained and become online
archive log files for use in rollforward recovery.
- USEREXIT
- Specifies that log retention logging is performed and that a user
exit program should be used to archive and retrieve the log files.
Log files are archived when they are full. They are retrieved when
the ROLLFORWARD utility must use them to restore
a database.
- DISK
- You must follow this value with a colon (:) and then a fully qualified
existing path name where the log files are 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/logstream/chainid/ directory.
- 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,
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. Examples
of TSM entries are:
- With a management class specified: db2 update db cfg for
mydb using logarchmeth1 TSM:DB2_LOGS
- With no management class specified: db2 update db cfg
for mydb using logarchmeth1 TSM
- 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. An example of a vendor entry is: db2
update db cfg for mydb using logarchmeth1 VENDOR:/home/dbuser/vendorLib/<library
name>
Note: - 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.
- To assign an archive path with a space in it,
use the db2CfgSet API.
- 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 10.1 for Linux, UNIX, and Windows