Verifying the Current Archive Setting of the Transaction Log

Set the primary DB2 UDB database transaction logging to archive logging, instead of circular logging for Replication Agent.

1. Determine the LOGARCHMETH1 setting.

   1. Connect to the database by entering this command at the CLP prompt.

      CONNECT TO dbalias USER db2_user USING db2_user_ps

      where dbalias is the cataloged alias of the primary database, db2_user is the primary database user, and db2_user_ps is the password.

   2. Determine the LOGARCHMETH1 setting:

      GET DB CFG FOR dbalias

2. If the results do not show that LOGARCHMETH1 is set to LOGRETAIN or to the path name of the directory to which logs are archived, set it:
   • To use the default archive location:

     UPDATE DATABASE CONFIGURATION USING logarchmeth1 LOGRETAIN

   • To use a specific archive location:

     UPDATE DATABASE CONFIGURATION USING logarchmeth1 DISK:path

     where path is the full path name of the directory where the archive logs are to be stored.

   If you change the setting of the DB2 UDB logarchmeth1 parameter, DB2 UDB requires you to back up the database:

   BACKUP DATABASE dbname TO "backup_dir"

   where dbname is your database name, and backup_dir is the target directory for the backup.