ANR2969E

Explanation
 DB2® detected
a problem during the restore operation. Sources of the problem might
include:  Tivoli® Storage Manager
API configuration errors for the DB2 instance
in which the Tivoli  Storage
Manager server database resides.
Errors related to the DB2 restore
operation.
Errors related to the target backup device.
The Tivoli Storage Manager
API client configuration used by the current instance is not able
to access the backup image.

System action
 The database restore operation is terminated.

User response
 If the message indicates DB2 sqlcode 2033, then the problem is most likely
the Tivoli Storage Manager
API configuration. The DB2 instance
uses the Tivoli Storage Manger
API to copy the Tivoli Storage
Manager database restore image from the Tivoli Storage Manager server-attached storage
devices to DB2. Common sqlerrmc
codes include:
  50 - To determine whether an error created the API timeout condition,
look for any Tivoli Storage
Manager server messages that occurred during the backup DB process
and that were issued before ANR2969E. Ensure that the Tivoli Storage Manager API options file has
the correct TCPSERVERADDR and TCPPORT options specified for the Tivoli Storage Manager server
being backed up. If the option settings are wrong, correct them for
the DB2 instance.
 53 - Ensure that the NODENAME option in the Tivoli Storage Manager API options files is
set to $$_TSMDBMGR_$$.
 106 - Ensure that the DB2-instance DSMI_DIR environment variable
is pointing to the location of the Tivoli Storage
Manager API executables and the dsm.sys configuration file. Ensure
that you have the correct permissions to access these locations. If
the DSMI_DIR setting is wrong, correct it for the DB2 instance, and then restart the DB2 instance.
 137 - Ensure that the DB2-instance DSMAPIPW command was run and
that it specified the nodename $$_TSMDBMGR_$$ and the password TSMDBMGR.
 400 - Ensure that the options specified in the Tivoli Storage Manager API options file are
valid.
 406 - Ensure that the DB2 instance
owner has at least read access to the Tivoli Storage
Manager API options file. Ensure that the DB2 Instance DSMI_CONFIG environment variable
is pointing to a valid options file for the Tivoli Storage Manager API. If the DSMI_CONFIG
setting is wrong, correct it for the DB2 instance,
and then restart the DB2 instance.
 450,451 - Ensure that the server options file and the Tivoli Storage Manager API options
file both contain the COMMMETHOD SHAREDMEM option. Ensure that the
values for the SHMPORT option in each options file correspond. Restart
the server if you change any values in the server options file.
 For descriptions of other sqlerrmc values, look in the dsmrc.h
file that is installed with the Tivoli Storage
Manager   API.

 If the message indicates DB2 sqlcode
2542, then the problem is probably because Tivoli Storage Manager API version for database
restore is not the same API version for database backup. Check Tivoli Storage Manager API version:
  AIX® - /bin/sh -c "lslpp
-lcq tivoli.tsm.client.api.64bit"
 Solaris -  /bin/sh -c "cat /var/sadm/pkg/TIVsmCapi/pkginfo |
grep VERSION
 HP- /bin/sh -c "cat /var/adm/sw/products/TIVsm64/CLIENT_API64/INDEX|
grep ^revision
 Linux - rpm -q TIVsm-API64-*
--qf %{VERSION}.%{RELEASE}\\n
 Windows - reg query
"HKEY_LOCAL_MACHINE\SOFTWARE\IBM\ADSM\CurrentVersion\Api"

 If this message is issued with a DB2 sqlcode that is not 2033 or 2542, then look
for more information about the error by opening a DB2 command-line processor window and typing:
? SQLsqlcode. For example, db2 => ? sql2428