logarchmeth2 - Secondary log archive method configuration parameter

• Database server with local and remote clients
• Client
• Database server with local clients
• Partitioned database server with local and remote clients

OFF

Specifies that the log archiving method should not be used. If both logarchmeth1 and logarchmeth2 are set to OFF, the database is considered to be using circular logging and is not rollforward recoverable. This is the default.

DISK

This value must be followed by a colon(:) and a fully qualified existing path name where you want the log files 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>/.

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 should be 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.

VENDOR

Specifies that a vendor library should be 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.

If you specify this path, log files are archived to both this destination and the destination specified by the logarchmeth1 database configuration parameter.