Monday, December 27, 2010

THE TSM SERVER 6.2.2 UPGRADE CAN DELETE DB2 INSTANCES - Manually upgrading server instances from Tivoli Storage Manager Version 6.1 to Version 6.2

During the upgrade to TSM 6.2.2, the installer attempts to determine the currently installed version of DB2 using the command 'db2level'. If the db2level command fails, the TSM server (including DB2) is then uninstalled and reinstalled rather than being upgraded. Uninstalling DB2 results in all DB2 instances being deleted. The deleted instances are not rebuilt post the upgrade.
The db2level command has been seen to fail with
        # LANG=C /opt/tivoli/tsm/db2/bin/db2level
        SQL10007N Message "-1390" could not be retrieved.  Reason
        code: "3".

Local fix:
Use the steps outlined in the technote:
        Manually upgrading server instances from Tivoli Storage
        Manager Version 6.1 to Version 6.2
        http://www-01.ibm.com/support/docview.wss?uid=swg27018195
        to recreate the instances that were deleted.


Manually upgrading server instances from Tivoli Storage Manager Version 6.1 to Version 6.2

Abstract
If a connection cannot be established using SSH, RSH, REXEC, or SMB, manually upgrade the IBM® Tivoli® Storage Manager server instance from Version 6.1 to 6.2.

Content
To use a wizard, the upgrade from IBM® Tivoli® Storage Manager Version 6.1 to Version 6.2 requires 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)
If a connection cannot be established using SSH, RSH, REXEC, or SMB, manually upgrade the Tivoli Storage Manager server instance from Version 6.1 to 6.2.

AIX®, Linux®, and UNIX®:
Close the installation wizard if you receive an error message indicating that the
wizard could not connect to your system using SSH, RSH, or REXEC:
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.
Then, use the following procedure to manually upgrade the server instance from Version 6.1.

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.


tsminst1
tsminst1
/home/tsminst1/tsminst1

TSMDB1
/home/tsminst1/tsminst1


DB2_SKIPINSERTED=ON>
DB2_KEEPTABLELOCK=ON
DB2_EVALUNCOMMITTED=ON
DB2_SKIPDELETED=ON
DB2CODEPAGE=819
DB2_PARALLEL_IO=*



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

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/db2iset –i InstanceName "Variable"

For example, to recreate the first variable in the example instance file, issue the
following 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:

a. Start DB2®:
db2start

b. Catalog and upgrade each database:
“db2 catalog db DatabaseName on DatabasePath"
“db2 upgrade db DatabaseName"

c. Stop DB2:
db2stop

6. Start and run the Tivoli Storage Manager server.

Windows®:
Close the installation wizard if you receive an error message indicating that the
wizard could not connect to your system using SSH, RSH, REXEC, or SMB:
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.

Then, complete the following procedures to manually upgrade the server instance from Version
6.1.

Before starting the upgrade, rename the instance file. The instance file (Instance.dat) is in the Tivoli Storage Manager server installation directory

The instance file looks similar to this example and contains DB2 environment
variables as configured for your server instance. Use the
values in the instance file for the commands necessary to manually upgrade the server
instance.


server1
server1
d:\tsm\server1

TSMDB1
d:\tsm\server1


DB2_SKIPINSERTED=ON>
DB2_KEEPTABLELOCK=ON
DB2_EVALUNCOMMITTED=ON
DB2_SKIPDELETED=ON
DB2CODEPAGE=819
DB2_PARALLEL_IO=*



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

1. Issue the following command:
installation_directory\db2\bin\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:
installation_directorydb2\bin\db2icrt InstanceName –u InstanceUser, password

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:
installation_directory\db2\bin\db2iset –i InstanceName "Variable"

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

5. Stop and start the database instance:

a. Open a DB2 command window. One method of doing this is by going to the C:\Program Files\Tivoli\TSM\db2\bin directory, or if you installed Tivoli Storage Manager in a different location, go to the db2\bin
subdirectory in your main installation directory. Then, issue this command:
db2cmd

b. Set the database instance:
set db2instance=InstanceName

c. Start DB2:
db2start

d. Catalog and upgrade each database name:
“db2 catalog db DatabaseName on DatabasePath"
“db2 upgrade db DatabaseName"

e. Stop DB2:
db2stop

6. Start and run the Tivoli Storage Manager server.
 IBM
Source:
APAR:
http://www-01.ibm.com/support/docview.wss?uid=swg1IC73253&myns=swgtiv&mynp=OCSSGSG7&mync=E
Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg27018195

1 comment: