Tips to fix the TSM server startup problems seen during installation in AIX

Today I will share some of the issues I faced during Installation/Reinstallation of Tivoli Storage Manager V6.3 in our training lab. 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......

SQL1032N No start database manager command was issued. SQLSTATE=57019

I got this error when I am installing for the first time on AIX 7, the error was that the DB2 license was not activated or db2iupdt failed. I have got this following error when I ran ./dsmicfgx command to configure TSM instance.

The "db2start" command fails with the following errors :

SQL8000N DB2START processing failed; a valid product license was not found. If you have licensed this product, ensure the license key is properly registered. You can register the license via the License Center or db2licm command line utility. The license key can be obtained from your licensed product CD.

SQL1032N No start database manager command was issued. SQLSTATE=57019

Solution:

The following steps can be used to resolve the issue:Login or su to the TSM DB2 instance owner and run the "db2licm -l" command. If the command returns license as "Expired", for example:

Then you should see a message like thisLIC1402I License added successfully.LIC1426I This product is now licensed for use as outlined in your License Agreement. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT, LOCATED IN THE FOLLOWING DIRECTORY: "/opt/tivoli/tsm/db2/license/en_US.iso88591"$ db2licm -lProduct name: "DB2 Enterprise Server Edition"License type: "Restricted"Expiry date: "Permanent"Product identifier: "db2ese"Version information: "9.7"So, now License has been renewed and you can try the ./dsmicfgx command again. It should work properly now and you should be able to configure TSM Instance.Also Read: Take TSM DB backup immediately if you notice these messages

libdb2.so.1: cannot open shared object file: No such file or directory

I have got this error when I am trying to run the command ./dsmserv to start the TSM server. The reason for this error is the TSM server database environment variables is not set correctly. The below message was displayed.

The TSM server fails to start as follows :

cd /instance_dir/opt/tivoli/tsm/server/bin/dsmserv -u tsminst1 -i /home/tsminst1.../opt/tivoli/tsm/server/bin/dsmserv: error while loading shared libraries: libdb2.so.1: cannot open shared object file: No such file or directoryorcd /opt/tivoli/tsm/server/bin /opt/tivoli/tsm/server/bin# ./dsmserv exec(): 0509-036 Cannot load program ./dsmserv because of the following errors: 0509-150 Dependent module libdb2.a(shr_64.o) could not be loaded. 0509-022 Cannot load module libdb2.a(shr_64.o). 0509-026 System error: A file or directory in the path name does not exist.SolutionThe below steps may be used to correct the situation. The below example uses /home/tsminst1 for the instance directory.As root user, Run the following command to source db2profile and reset the environment variables:

/home/tsminst1/sqllib/db2profile

cd /home/tsminst1

and run below command

/opt/tivoli/tsm/server/bin/dsmserv -u tsminst1 -i /home/tsminst1

As instance user, run the following commandssu - tsminst1cd /home/tsminst1/opt/tivoli/tsm/server/bin/dsmservAfter running this, the TSM Server should start automatically, to check if it is running, run this command# lslpp -l|grep -i dsmservAlso Read: Why is it important to use DIRMC option during backups ?

ANR0226S: The database ID file could not be found for server startup

I have got this error when I tried to start the TSM server after 2-3 days of AIX machine shutdown. I have to make the machine down for 2 days to use the memory for other AIX server. I assume the reason for this error is because of this reason.

The TSM server did not start when I gave ./dsmserv command because the server's database ID file (dsmserv.dbid) could not be found. This file is created when the database is formatted, is stored in the directory from which the format is performed, and is required for normal server operation.

Solution

Ensure that you are starting the server from the correct instance directory, and that the dsmserv.dbid file exists and can be read. If no dsmserv.dbid file exists, restart the server with the -S option to create a new database ID file.

For example: ./dsmserv -S

Run the above command even if there is dsmserv.dbid file to create and replace the old file.