Scribd
Upload
48 views6 pages

Setting The DB2 Configuration Parameters

Uploaded by

Robson Silva Aguiar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
48 views6 pages

Setting The DB2 Configuration Parameters

Uploaded by

Robson Silva Aguiar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Expert>

Backup and Restore Agents>


Backup Agents>
DB2>
DB2 Backup Administrator Guide>
Configuration for DB2 Agent Environments>
Additional Configuration for the DB2 Agent>
Setting the DB2 Configuration Parameters

Setting the DB2 Configuration Parameters


Updated Friday, June 19, 2020

On this page 
Set the LOGARCHOPT1 Parameter
Set the VENDOROPT Parameter
Set the LOGARCHMETH1 Parameter to the VENDOR Library for Log Backups
Set the LOGARCHMETH1 Parameter to DISK for Log Backups
Before You Begin
Procedure
Set the TRACKMOD Parameter for Delta or Incremental Backups
Set the LOGARCHOPT1 and VENDOROPT Parameters for a Cluster Setup
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.

Variable Description

database_name The DB2 database name


The name of the client in the CommCell Console.
CvClientName When you have a clustered environment, you must set this parameter to the virtual client name in the CommCell
Console.

CvInstanceName The name of the Commvault installed instance

The path where the Commvault software is installed.


For the directory under the commvault_install_path, use the following:
commvault_install_path
Base - for Windows, 32-bit AIX/Solaris or HP-UX or 32bit/64bit Linux or 31bit Linux on System Z

Base64 - for 64-bit AIX/Solaris/HP PA-RISC or 64-bit Linux on System Z

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

 Note: If the parameter is set to DISK and the path is different from the archive log path the log backup jobs go to a pending state.

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.

Property Value

Name sALLOWLOGARCHMETH1TODISK

Category Db2Agent

Type String

Value Y

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'"

© 1997-2022 Commvault Systems® Inc. All Rights Reserved.

You might also like