Setting the DB2 Configuration Parameters

Each DB2 database has its own configuration. To back up DB2 data successfully, you must enable the appropriate database configuration parameters. You must set these parameters based on the state of the database, the backup type, and/or the data type.

Before you change any configuration parameter, ensure that no applications are currently using the database. Also, consult your database administrator about the business requirements for the database.

Update the database configuration parameters when the DB2 agent is installed.

If you want to automatically update the DB2 parameters, see Automatically Updating DB2 Parameters.

The following variables are used in describing the syntax for the DB2 parameters.

Set the LOGARCHOPT1 Parameter

From the DB2 console, type the following command to set the LOGARCHOPT1 parameter:

 
db2 update db cfg for database_name using LOGARCHOPT1 "'CvClientName=CvClientName,CvInstanceName=CvInstanceName'"

Example:

db2 update db cfg for test_db using LOGARCHOPT1 "'CvClientName=testhost,CvInstanceName=Instance001'"

Set the VENDOROPT Parameter

From the DB2 console, type the following command to set the VENDOROPT parameter:

 
db2 update db cfg for database_name using VENDOROPT "'CvClientName=CvClientName,CvInstanceName=CvInstanceName'"

Example:

db2 update db cfg for test_db using VENDOROPT "'CvClientName=testhost,CvInstanceName=Instance001'"

Set the LOGARCHMETH1 Parameter to the VENDOR Library for Log Backups

By default, Commvault software sets the DB2 configuration parameter LOGARCHEMETH1 to the VENDOR library. For information about the default values for the vendor library, see Vendor Library.

The SBT interface transfers the log files from the DB2 directory to the threshold directory that you defined when you installed the DB2 Agent. If you use the delete option, then the log files are deleted from the threshold directory. If you do not use the delete option, then the log files are kept in this directory. By default, the threshold directory can hold 1000 log files. If more than 1000 log files are put in the threshold directory a command line backup for the log files starts automatically, and the log files are transferred to tape.

You can change the log threshold. For more information, see Modifying the Threshold for Log Backups.

From the DB2 console, type the following command to set the LOGARCHMETH1 parameter to the VENDOR library:

Unix:

 
db2 update db cfg for database_name using LOGARCHMETH1 "'VENDOR:commvault_install_path/Base/libDb2Sbt.so'"

Windows:

 
db2 update db cfg for database_name using LOGARCHMETH1 "'VENDOR:commvault_install_path\Base\Db2Sbt.dll'"

Unix example:

db2 update db cfg for test_db using LOGARCHMETH1 "''VENDOR:/opt/commvault/Base/libDb2Sbt.so''"

Set the LOGARCHMETH1 Parameter to DISK for Log Backups

Before You Begin

You can configure the DB2 configuration parameter LOGARCHEMETH1 to DISK when the DISK directory path is the same as the DB2 Archive Log path. To the CommServe host, add the sALLOWLOGARCHMETH1TODISK additional setting as shown in the following table. Note that you cannot use the sALLOWLOGARCHMETH1TODISK additional setting when you run DB2 Version 10 or higher.

For instructions on how to add additional settings from the CommCell Console, see Adding or Modifying Additional Settings from the CommCell Console.

Procedure

Set the LOGARCHMETH1 parameter. On the command line, type the following, substituting archive_log_path with your value:

 
db2 update db cfg using LOGARCHMETH1 "'DISK:archive_log_path'"

Example:

db2 update db cfg for new_db using LOGARCHMETH1 "'DISK:/db2archive'"

Set the TRACKMOD Parameter for Delta or Incremental Backups

From the DB2 console, type the following command to set the TRACKMOD parameter.

 
db2 update db cfg for database_name using TRACKMOD on

Example:

db2 update db cfg for new_db using TRACKMOD on

After you change the TRACKMOD database configuration parameter to ON, you must run an offline full backup before an incremental backup can be taken on the tablespace.

Set the LOGARCHOPT1 and VENDOROPT Parameters for a Cluster Setup

Set the DB2 database configuration parameters on both of the physical nodes, for a cluster configuration. Use the virtual machine name instead of a physical client name.

To back up any type of DB2 data, update the LOGARCHOPT1 and VENDOROPT database configuration parameters on both of the physical nodes by entering the following commands:

1. From the DB2 Console, type the command to set the LOGARCHOPT1 parameter:

    
   db2 update db cfg for database_name using LOGARCHOPT1 "'CvClientName=Virtual_Machine_CvClientName,CvInstanceName=CvInstanceName'"

2. Type the following command to set the VENDOROPT parameter:

    
   db2 update db cfg for database_name using VENDOROPT "'CvClientName=Virtual_Machine_CvClientName,CvInstanceName=CvInstanceName'"