The error messages that are displayed during ARCMAIN operations can originate from various software components.
The error conditions shown in the following table can occur while starting Teradata Extension for Tivoli Storage Manager or while backing up data. Use this information to ensure that the installation process is successfully completed and that all recovery options are considered.
| Error Condition | Possible Recovery Option |
|---|---|
| An invalid option was found during option parsing | This is a dsmSetup error. The installation process attempted to read Windows registry settings to determine the paths to TSM. However, there was an invalid option found during option parsing, probably due to an invalid option specification in the TSM Client Options file. Refer to the DSIERROR.LOG file and determine which line of the options file is invalid. The path to this file is set with the DSMI_LOG environment variable or the path defaults to the local directory. For more information about TSM Client Options, refer to IBM’s Tivoli Storage Manager for Windows: Backup-Archive Clients Installation and User’s Guide. |
| ANSnnnn or ANRnnnn TSM errors | Teradata Extension for Tivoli Storage Manager attempts to gather as much information as it can about the root cause of errors. Query the TSM server activity log for device errors or other messages that did not get conveyed to the client process. For information on the TSM server activity log, refer to TSM Server Activity Log. Alternately, check for DSIERROR.LOG file error messages on the client. |
| dsmInitEx-- Session rejected | This is an open session error from Teradata Extension for Tivoli Storage Manager, related to opening a TSM server connection. This is an authentication error, the most common source of open session errors. An invalid NODENAME or PASSWORD is defined in the TSM Client Options file. For more information about how settings need to match what is defined for the TSM server, see Configuring TSM for Teradata Backups. |
| Errors that include a traceback | Teradata Extension for Tivoli Storage Manager maintains an internal trace buffer that is dumped to stderr output when exceptional conditions occur, such as memory access or illegal instruction. This type of diagnostic output is a problem that can only be corrected by the Teradata Development organization, therefore: Capture a complete output listing. For information about generating diagnostic traces, see taratddsmc Help Command for details about the BARAMLOG and BARAMLOGLEVEL environment variables. These variables control the diagnostic tracing for Teradata Extension for Tivoli Storage Manager. After collecting the trace information, contact Teradata Customer Support. File locking contention can occur when two jobs attempt to write to the same log file at the same time. |
| Hung up on a tape mount | Device messages often show up in the TSM server activity log. For more information on the TSM server activity log, refer to TSM Server Activity Log. |
| Hung up on a Teradata Database lock | Consult the Teradata QUERYSESSION and SHOWLOCKS console utilities for help. |
| Options file ‘*’ not found | This is a dsmSetup error. The installation process attempted to read Windows registry settings to determine paths to TSM. However, the TSM Client Options file was not found. One or more of the DSMI environment variables are not properly set. Edit runarctiv.bat and:
|
| The file cannot be found or is improperly formatted | Locate the file and correct the format. The installation process should have created a TDBAR configuration file directory (which is usually C:\Program Files\Teradata\Teradata Client\TDBAR). The TIVARC.BAT file starts ARCMAIN with the sample ARCDFLT.TXT file as the ARCMAIN default command line option file. |
| tivarc (tivadm) is not recognized as an internal or external command, operable program or batch file | The %PATH% is wrong. The environment variable for %PATH% does not include the location of the TIVARC.BAT, ARCMAIN.EXE, and TIVBAR.DLL files. Usually this location is C:\Program Files\Teradata\Teradata Client\BIN. |
| Unable to see backups in storage using TDDSMC | If the ARCMAIN process seems to be error-free, but verifying that the storage object was created on the TSM server is not possible, check the following:
The QUERY TSM command from the taratddsmc utility might provide additional information. |