Tips to fix the problems faced during TSM Server Instance configuration

This is continuation of the previous post TSM 6.3 Installation and Server Startup Troubleshooting Tips on AIX 7. I have to install and uninstall TSM V6.3 on AIX 7 many times (atlesast 10 times) on the same machine to demonstrate in our training lab, I have seen many issues with TSM DB2 even after I followed all TSM 6.3 requirements on AIX machine and I am going to share some of the issues in this post. Hope it helps some one......

The Home Directory of the user ID is inconsistent while running dsmicfgx Configuration Wizard

I got this error when I was running the configuration wizard (dsmicfgx) to configure the Tivoli Storage Manager V6 instance on AIX 7. The error says that home directory of the user ID is inconsistent when running the configuration wizard after a successful installation/upgrade/reinstall of Tivoli Storage Manager Server V6 as shown below.

The dsmicfgx.trc error log file located in /var/tivoli/tsm shows the following message

Fri Sept 6 10:24:25 CST 2013 com.tivoli.dsm.ServerConfig.ServerDB.validateHomeDirectory(): Checking if directory /home/tsminst1/sqllib exists
Fri Sept 6 10:24:25 CST 2013 com.tivoli.dsm.ServerConfig.ServerDB.validateHomeDirectory(): sqllib dir exists: false
Fri Sept 6 10:24:25 CST 2013 com.tivoli.dsm.ServerConfig.ServerDB.validateHomeDirectory(): Running db2ilist cmd: LANG=C /opt/tivoli/tsm/db2/instance/db2ilist

----------

----------

Also Read: Use these 4 TSM Server options to efficiently manage the client backup schedules

Solution:

The error states that the sqllib directory does not exist in the instance users home directory, but db2ilist has the instance listed. If this is a new instance configuration, you can use the following DB2 command to drop the instance. As the root user:
/opt/tivoli/tsm/db2/instance/db2idrop <instance name that db2ilist reports>

In this example, the instance name is tsminst1:
/opt/tivoli/tsm/db2/instance/db2idrop tsminst1

Then use 'db2ilist' to list the instances. If the instance is no longer reported by db2ilist, try dsmicfgx again. If tsminst1 still shows up in the list, try running the following as root:
/opt/tivoli/tsm/db2/instance/db2iset -d tsminst1

Then check again via 'db2ilist' to make sure the instance has been removed. If the instance is no longer reported by db2ilist, try dsmicfgx again. This time it should work fine without any errors. Basically we deleting the old DB2 instance from the DB2 list to create a new DB2 instance.

TSM Instance Communication Problem (SSH, RSH, REXEC, or SMB) while running TSM Configuration wizard (dsmicfgx)

To use the dsmicfgx wizard, we require one of the following protocols on the default port, and that port cannot be blocked by a firewall:

• Secure shell (SSH)

• Remote shell (RSH)

• Remote Execution Protocol (REXEC)

• Windows server message block (SMB)

You will get this kind of error when configuring TSM instance multiple times on the same machine. The error should say something like this

All attempts to establish a connection as the instance user ID have failed. This might be due to an inability to connect to the local machine through the SSH, RSH, REXEC, or Windows SMB protocols

Solution:

Then, use the following procedure to manually delete the old the server instance. First, rename the instance file. You can find this file in the following location:

/etc/tivoli/tsm/instance.info

The instance file looks similar to this example and contains DB2 environment variables as configured for your server instance . Use the values in this file for the commands necessary to manually upgrade the server
instance.
<Instance>
<InstanceName>tsminst1</InstanceName>
<InstanceUser>tsminst1</InstanceUser>
<DefaultDatabasePath>/home/tsminst1/tsminst1</DefaultDatabasePath>
<Database>
<DatabaseName>TSMDB1</DatabaseName>
<DatabasePath>/home/tsminst1/tsminst1</DatabasePath>
</Database>
<Variables>
<Variable>DB2_SKIPINSERTED=ON></Variable>
<Variable>DB2_KEEPTABLELOCK=ON</Variable>
<Variable>DB2_EVALUNCOMMITTED=ON</Variable>
<Variable>DB2_SKIPDELETED=ON</Variable>
<Variable>DB2CODEPAGE=819</Variable>
<Variable>DB2_PARALLEL_IO=*</Variable>
</Variables>
</Instance>

After renaming the instance file, complete the following steps. Complete steps 1-6 for each one of your Tivoli Storage Manager server instances.

Also Read: Take TSM DB backup immediately if you notice these messages

1. Issue the following command:
/opt/tivoli/tsm/db2/instance/db2idrop InstanceName

2. Start the installation wizard again and step through it to upgrade the Tivoli Storage Manager server.

3. After the upgrade, recreate each of the instances using the following command:
/opt/tivoli/tsm/db2/instance/db2icrt –u InstanceUser InstanceName

4. Recreate the variables in the instance file using the db2set -i command. Issue this command for each variable in your instance file. Ensure that the variable is in quotation marks:
/opt/tivoli/tsm/db2/instance/db2set –i InstanceName "Variable"

For example, to recreate the first variable in the example instance file, issue thefollowing command:
db2set -i tsminst1 "DB2_SKIPINSERTED=ON"

5. Stop and start the database instance. Connect as the user ID that owns the server instance, then issue the following commands:

• Start DB2:

                   db2start

• Catalog and upgrade each database:

                 “db2 catalog db DatabaseName on DatabasePath"
                 “db2 upgrade db DatabaseName"

• Stop DB2:

                   db2stop

6. Start and run the Tivoli Storage Manager server.