Error messages that range from 1200 to 1299 (shown in the following table) originate in the TSM portion of Teradata Extension for Tivoli Storage Manager. Note that some of the error codes have multiple error messages.
| Error Code | Error Message Text | Description and Remedy |
|---|---|---|
| BAM1200 | Access Module needs Tivoli Version < > Release < > but client library is Version < > Release < > | Teradata Extension for Tivoli Storage Manager detects an invalid software library release level. The path to the loaded extension is set with the IOMODULE command line parameter to ARCMAIN. Remedy: Correct the configuration issue and resubmit the job. |
| BAM1201 | Tivoli dsmEndTxn error < >, (reason < >): < > | Teradata Extension for Tivoli Storage Manager detects an unexpected error when starting a TSM End Transaction function. The error code, reason code, and error message text indicate the nature of the error. Reason codes usually correspond to numbers 1 through 50 of the API return codes. For more information on the API return codes, see IBM’s TSM Messages manual. If this error occurs when writing backup files to the TSM, Teradata Extension for Tivoli Storage Manager rolls back and deletes all file segments written to TSM up to this point, except file segment 0 (F000). Remedy: For recommendations about correcting the cause of this error, refer to the TSM documentation. Do one of the following:
|
| BAM1202 | Tivoli Backup Copy Group does not exist for object FileSpace= < >, HighLevel= < >, LowLevel= < > | TSM is unable to assign a copy group for the backup object being created. This situation is the result of an API dsmBindMC call. The object name is listed as FileSpace, HighLevel name, and LowLevel name. Remedy: Consult the TSM administrator to determine the source of the problem. |
| BAM1203 | Tivoli Storage object FileSpace= < >, HighLevel= < >, LowLevel= < >, ID= < > is not recognized by Access Module. Skipping. | Teradata Extension for Tivoli Storage Manager is unable to interpret the formatted metadata, which is usually stored with the storage object. The object is skipped and processing for the object stops, although processing continues for the balance of the job. This error is usually generated because a storage object exists in TSM that has a similar name to a Teradata backup created by Teradata Extension for Tivoli Storage Manager. The specified object name in the query is picking up more than it should. This warning message does not terminate processing because Teradata Extension for Tivoli Storage Manager cannot communicate a non-fatal warning condition to ARCMAIN. As a result, the return code indicator from ARCMAIN can be zero, even though this message is displayed. Remedy: Use the indicated diagnostic information to verify the status of the storage object. If the storage object is considered for Teradata backup and restore, contact the Teradata Global Support Center. If the object is being incorrectly qualified because the wildcard specification is too general, restate the query so it is correctly limited to the storage objects created by Teradata Extension for Tivoli Storage Manager. |
| BAM1204 | TDDSMC syntax error: < > | The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error in the command. The message indicates the source of the error. Remedy: Correct the syntax and resubmit the job. For more details, issue the HELP command or refer to taratddsmc Help Command. |
| BAM1205 | TDDSMC syntax error: < > field width cannot exceed < > | The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on a FORMAT string. The field width override value for the indicated substitution variable is too long. Remedy: Correct the syntax and resubmit the job. For more details, issue the HELP FORMAT command or refer to taratddsmc Help Command. |
| BAM1206 | Tivoli server aborted transaction during < > call. Error < >, (reason < >): < > | TSMserver aborted the client transaction for the noted reason code. For more information on the API return codes, see the TSM Messages manual. Reason codes usually correspond to numbers 1 through 50 of the API return codes. If this error occurs when writing backup files to the TSM, Teradata Extension for Tivoli Storage Manager rolls back and deletes file segments written to TSM up to this point, except file segment 0 (F000). If the text of the message indicates a zero value for the reason code, issue a QUERY ACTIVITYLOG command on the TSM server to determine the root cause of the abort. Remedy: For recommendations about correcting the cause of this error, refer to the TSM documentation. Do one of the following:
|
| BAM1207 | TDDSMC syntax error: Expected quote string at >> ( ) << on command line | The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on the command line arguments used to start the utility. This error is the result of a quote string not being found at the specified position. Remedy: Correct the syntax and resubmit the job. For more details about command line syntax, issue the HELP command or refer to taratddsmc Help Command. |
| BAM1208 | TDDSMC syntax error: No matching and quote character on command line | The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on the command line arguments used to start the utility. A quote string was detected, but no matching end-quote was found. The TDDSMC utility recognizes single- and double-quote characters, but sometimes the operating system strips quotes before passing the command line to the utility. After a quote character is detected, the utility will keep scanning the command line for a matching end-quote. Remedy: Correct the syntax and resubmit the job. For more details about command line syntax, issue the HELP command or refer to taratddsmc Help Command. |
| BAM1209 | TDDSMC syntax error: Extraneous information follows < > command starting at: < > | The TDDSMC utility in Teradata Extension for Tivoli Storage Manager detects a syntax error on the command line arguments used to start the utility. A valid command was parsed, but non-blank trailing characters were detected. This error can occur when an unquoted name pattern contains embedded blanks. There are optional fields after the name pattern. Therefore, the actual source of the syntax error might be prior to the position indicated. Remedy: Correct the syntax and resubmit the job. For more details about command line syntax, issue the HELP command or refer to taratddsmc Help Command. |
| BAM1210 | Access Module cannot backup more than 4080 objects. | TSM limits the number of objects that can be retrieved at one time to DSM_MAX_GET_OBJ (4080). Therefore Teradata Extension for Tivoli Storage Manager does not back up more than 4080 object segments. The maximum size of one backup job cannot exceed approximately 8 TB. Remedy: Modify backup jobs to contain less data. |