ANR2968E
Database backup terminated. DB2 sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc.

Explanation

DB2® detected a problem during the backup operation. Sources of the problem might include:
  1. Tivoli® Storage Manager API configuration errors for the DB2 instance in which the Tivoli Storage Manager server database resides.
  2. An error related to the DB2 backup operation.
  3. Errors related to the target backup device.

System action

The database backup is terminated.

User response

If the message indicates DB2 sqlcode 2033, then the problem is probably the Tivoli Storage Manager API configuration. The DB2 instance uses the Tivoli Storage Manager API to copy the Tivoli Storage Manager database-backup image to the Tivoli Storage Manager server-attached storage devices. Common sqlerrmc codes include:

  1. 50 - To determine whether an error created the API timeout condition, look for any Tivoli Storage Manager server messages that occurred during the database-backup process and that were issued before ANR2968E. 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.
  2. 53 - Ensure that the NODENAME option in the Tivoli Storage Manager API options files is set to $$_TSMDBMGR_$$. Also verify the TCPSERVERADDRESS setting. If the keyword "localhost" is being used verify that this is being resolved correctly by issuing the command "ping localhost" from a system command window. If the ping of localhost fails, consider changing the TCPSERVERADDRESS to the explicit loopback address of 127.0.0.1. As an alternative to setting the explicit loopback address of 127.0.0.1, verify the TCP/IP configuration and whether or not "localhost" is configured correctly. For example, for Unix or Linux systems, verify that /etc/hosts has an appropriate entry for "localhost".
  3. 106 - Ensure that the DB2 Instance DSMI_DIR environment variable is pointing to the location of the Tivoli Storage Manger API executables and the dsm.sys configuration file. If the DSMI_DIR setting is wrong, correct it for the DB2 instance, and then restart the DB2 instance.
  4. 137 - Ensure that the DB2-instance DSMAPIPW command was run and that it specified nodename $$_TSMDBMGR_$$ and the password TSMDBMGR.
  5. 400 - Ensure that the options specified in the Tivoli Storage Manager API options file are valid.
  6. 406 - Ensure that the DB2 instance owner has at least read access to the Tivoli Storage Manger 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.
  7. 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.
  8. For descriptions of other sqlerrmc values, look in the dsmrc.h file that is installed with the Tivoli Storage Manager API.

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