Multiple SAP® Instances on the same host with multiple DB2 SID’s.

Answer

Because each SID has it's own environment, owner, directories and configuration files, the setup needs to be modified to accommodate any additional DB2 SAP® instances that are on the same machine and will be utilizing the Data Protection for SAP®.

The Data Protection for SAP®’s first instance will be configured during the installation process.
The steps below can be followed to modify the configuration so that a second (additional) SAP® DB2 instance can utilize the Data Protection for SAP® on this same machine.

The following general steps will be performed:

• add a new NodeName on the Tivoli Storage Manager server for each new SID.
• add a new server stanza in the dsm.sys for the each new NodeName .
• passwordaccess generate is recommended.

• Configure the config files vendor.env and *.utl specific to the new SID.
• Update the environment variable XINT_PROFILE for the new SID
• Set the password for the new SID.

In this example:

• the DP1 instance was specified during the installation process.
• the DP2 instance needs to be configured manually.
• this is a 64-bit DP for SAP® (must be same bit version as the db2 instance).
• the DB2_HOME directory is: /db2/DP1 and /db2/DP2.

The installation specified the DP1 instance and thus the DP1 SID has the complete setup:
In /db2/DP1 the vendor.env and initDP1.utl file and initDP1.bki files exist (they were put in place during the installation process).

To setup the Data Protection for SAP® for the additional SAP® instance, copy/configure the files needed for the second (DP2) instance as follows:

Copy the .utl and vendor.env files to the /db2/DP2 directory, renaming them with the correct DP2 SID. Copy the agent.lic file. The files can be copied from the DP1 setup.

cp /db2/DP1/tdp_r3/initDP1.utl /db2/DP2/tdp_r3/initDP2.utl
cp /db2/DP1/tdp_r3/vendor.env /db2/DP2/tdp_r3/vendor.env
cp /db2/DP1/tdp_r3/agent.lic /db2/DP2/tdp_r3/agent.lic

Configure the initDP2.utl file to have the correct DP2 information for the CONFIG_FILE, BACKUPIDPREFIX and the SERVER parameter. Make sure the SERVER entry has a different value for each SID if you are using different Tivoli Storage Manager NodeNames for each SID.
Make any necessary changes to the vendor.env file to specify the DP2 value instead of DP1.

Run the backom command to set the password. This will create the file /db2/DP2/tdp_r3/initDP2.bki file based on the setting for the CONFIG_FILE parameter from the initDP2.utl.

backom -e <full path>/initDP2.utl -c password

Enter the password for the DP2 node that was set on the Tivoli Storage Manager server.

This will complete the configuration of the second Data Protection client for the additional SAP® instance.

Following are steps to configure the VENDOROPT, LOGARCHMETH, LOGARCHOPT variables for the second DB2 instance.

db2 update db cfg for DP2 “VENDOROPT=/db2/DP2/tdp_r3/vendor.env”

db2 update db cfg for DP2 “LOGARCHMETH1=VENDOR:/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a”

db2 update db cfg for DP2 “LOGARCHOPT1=/db2/DP2/tdp_r3/vendor.env”

To check if the above variables are set correctly for the DB2 instance use the following command.

db2 get db cfg | grep VENDOR

and

db2 get db cfg | grep LOGARCH

NOTE: It is not required or recommended to install multiple copies of the Data Protection for SAP®.