Stefan, From the "TSM V6.1 Problem Determination Guide" - GC23-9789
Note - Adjust the following for your Windows environment ====================================== DB2 SQLCODE -2033 SQLERRMC 406 SQL error message code 406 requires that the following issues are resolved: - The DSMI_CONFIG environment variable points to a valid Tivoli Storage Manager options file. - The instance owner has read access to the dsm.opt file. - The DSMI_CONFIG environment variable is set in the db2profile. The following procedure is an example process for debugging DSMI environment variable errors on a UNIX platform where the SQL error code (SQLERRMC) of 409 was displayed when using the dsmapipw command: 1. Open the /home/tsminst1/sqllib/userprofile file and examine the statements. If you make any changes to this file, stop and restart the DB2 instance so that the changes are recognized. The userprofile file might have statements similar to the following example text: export DSMI_CONFIG=/home/tsminst1/tsminst1/tsmdbmgr.opt export DSMI_DIR=/usr/tivoli/tsm/client/api/bin64/dsm.sys export DSMI_LOG=/home/tsminst1/tsminst1 The file in the first line of the example (/home/tsminst1/tsminst1/ tsmdbmgr.opt) might have something similar to the following text: SERVERNAME TSMDBMGR_TSMINST1 The file in the second line of the example (/usr/tivoli/tsm/client/api/bin64/ dsm.sys) might have something similar to the following text: SERVERNAME TSMDBMGR_TSMINST1 commmethod tcpip tcpserveraddr localhost errorlogname /home/tsminst1/tsminst1/tsmdbmgr.log 2. Verify that the SERVERNAME entry in the tsmdbmgr.opt file matches the SERVERNAME entry in the dsm.sys file. 3. Run the DSMAPIPW command. You must be logged on using the root user ID. 4. If you can run the DSMAPIPW command, remove the /home/tsminst1/ tsminst1/tsmdbmgr.log file while still using the root user ID to eliminate permission problems between the root user and tsminst1. ============================================ Also make sure that the user running TSM has write permissions to all log files The API Options file in UNIX is /usr/tivoli/tsm/client/api/bin64/dsm.sys - look for or create a similar file on your server Another reference you may want to consult is the IBM Redbook: "Backing up DB2 with IBM Tivoli Storage Manager" - sg24-6247 Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. ============================================================ =========================================================== -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Stefan Folkerts Sent: Wednesday, August 26, 2009 6:25 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Windows TSM server 6.1.2.0 after clean install : ANR2968E Database backup terminated. DB2 sqlcode: -2033. I have done a clean install of the 64bit windows version of 64bit TSM 6.1.2.0 on Windows 2008 DC +sp1 + windows patches After I do a minimal setup of the server instance I am able to connect to the instance using TSMmanager. When I set the dbrecovery option to the default file device class I should be able to backup the TSM database with the 'ba db type=full devcass=FILEDEV1' command (FILEDEV1 is the name of the default file device class with TSM 6.1.2.0) ANR2968E: Database backup terminated. DB2 sqlcode: sqlcode. DB2 sqlerrmc: sqlerrmc. =============================== I have the 406 error but I cannot figure out what exactly IBM wants me to do to fix this problem. I don't have ANY DB2 knowledge. My questions ; >> Ensure that the DB2 instance owner has at least read access to the Tivoli Storage Manger API options file. What is the name and location of this file? >> Ensure that the DB2-instance DSMI_CONFIG environment variable is pointing to a valid options file for the Tivoli Storage Manager API. Where and how do I set this environment variable? >> If the DSMI_CONFIG setting is wrong, correct it for the DB2 instance, and then restart the DB2 instance. Where do I check what the current setting is? Regards, Stefan IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
