The error messages shown in the following table originate in the vendor-independent portions of Teradata Extension for Tivoli Storage Manager. These error codes range from 1000 to 1199.
| Error Code | Error Message Text | Description and Remedy |
|---|---|---|
| BAM1000 | NULL file pointer passed to < > function of Access Module Unrecognized file pointer 0x< > passed to < > function of Access Module Write called with buffer length < > when max size is < > Access Module passed OBJNAME attribute < >. It is < > characters long when only < > characters supported Invalid object type < > passed on OBJNAME attribute Invalid CopyNum < > passed to BARFile Constructor Invalid File Open Mode < > when closing Write called when file not opened for writing NULL position pointer passed to SetPos Invalid position (< > < >) passed to SetPos SetPos position (< > < >) caused us to read past end of segment SetPos position (< > < >) reads past end of segment Reposition offset= < > when only < > bytes returned by read Unable to interpret Object Info. Format= < >, InfoLen= < > CloseWrite should have updated < > segments but only did < > CloseWrite File segment FS= < >, HL= < >, LL= < > does not match list
|
An internal software error is detected. These messages correspond to BAR internal error codes. They indicate a severe, unexpected, or exceptional condition that can only be corrected by the Teradata Development organization, therefore:
Remedy: Contact a field engineer or Teradata Customer Support. |
| BAM1001 |
|
The core error reporting routines cannot do their work. An internal software error/corruption is detected. Other error conditions might be hidden behind this error. Remedy: Contact a field engineer or Teradata Customer Support. |
| BAM1002 | The access module expects the Tivoli password access mode to be PASSWORD PROMPT | Teradata Extension for Tivoli Storage Manager only functions in PASSWORD PROMPT mode. Remedy: Specify the PASSWORD mode as PROMPT in dsm.opt. |
| BAM1003 | Access Module currently does not support restarts in the WRITE mode | Teradata Extension for Tivoli Storage Manager does not support restart processing when a backup file is opened in WRITE mode, which means that the extension rolls back and deletes all data written to TSM up to this point.
Remedy: Do one of the following:
|
| BAM1005 | Access Module cannot open more than < > files at same time | More FILE= clauses are specified on the ARCMAIN backup statement than are supported by Teradata Extension for Tivoli Storage Manager. Remedy: Correct the ARCMAIN statement and resubmit the job. |
| BAM1006 | Access Module detected multiple backups for NameSpace= < >, Path= < >, Segment= < > | TSM qualified multiple backups for the indicated Namespace, Pathname, and Segmentname pattern. This is an error because a backup and restore needs to work with only one high-level name per ARCMAIN statement. The most likely reason for this error is that the Namespace or Pathname fields contain a wildcard character that qualifies multiple backup files from the TSM catalog. Test this by using the native API query tool to see what backup file names come back, making sure that you are logged on as the same user ID to the TSM server. Wildcard characters are acceptable for a low-level segment name because Teradata Extension for Tivoli Storage Manager reserves those names for its own purposes. Remedy: Correct the indicated name by removing the wildcard characters, and resubmit the job. |
| BAM1007 | No backup file (s) found with NameSpace= < >, Path= < >, Segment= < >, Generation= < > | No backup file matched the indicated Namespace, Pathname, Segmentnamepattern, and Backup File Generation number. The Namespace field defaults to Teradata. The Pathname is set by one of the following:
Segmentname is controlled only by Teradata Extension for Tivoli Storage Manager, but is shown in case you want to include it in an administrative query. The generation number is entered as an IOPARM field or defaults to zero. Relative numbers, such as -1 and -2, count backwards from the current active backup (gen=0). Remedy: Correct the indicated name and resubmit the restore job. |
| BAM1008 | Duplicate storage objects found with NameSpace= < >, Path= < >, Segment= < >, Generation= < > | Teradata Extension for Tivoli Storage Manager creates storage object names with a particular format. Also, a non-negative generation number is stored in the Object Info portion of the storage catalog metadata. If duplicate storage objects were found with the same name/generation one of the following has happened:
The extension relies on the generation number to distinguish between separate runs of the same backup job, so all file segments that correspond to a single backup job execution need to have the same generation number. Remedy: Verify the heritage of the pertinent storage objects and, if necessary, delete the corrupt objects or update the Object Info metadata with distinct generation numbers. Ensure that the backups are not creating new objects when the metadata is updated. If the remedy does not work, contact a field engineer or Teradata Customer Support. |
| BAM1009 | Access Module currently does not support repositioning when writing to backup files | Teradata Extension for Tivoli Storage Manager does not support restart processing when a backup file is opened in WRITE mode because it is not possible to reposition to the exact point of failure inside TSM. This means that Teradata Extension for Tivoli Storage Manager rolls back and deletes all data written to TSM up to this point.
Remedy: Do one of the following:
|
| BAM1010 | SetPos generation < > does not match current file generation of < > | When Teradata Extension for Tivoli Storage Manager creates a new backup file, it stores a unique generation number in the Object Info field of the storage object. This error occurs when a reposition operation detects that the position being requested is for a backup file with a different generation number from the one that is currently open. Normally, this condition indicates a corrupted position field managed by ARCMAIN. However, when using the CATALOG feature of ARCMAIN to get fast repositioning on a restore, ARCMAIN can pick up a position that is inconsistent with the backup files in storage. This condition can happen under the following circumstances: Regularly running the same backup job, saving position information to the CATALOG database. Creating additional backups without using the CATALOG option, so there is no position information saved. Running a restore using the most recent backup image from storage. In this case, the most recent image in storage might correspond to generation 103, when the most recent backup image in the CATALOG database corresponds to generation 102. Remedy: Examine ARCMAIN listings and the storage catalog, and do one of the following:
|
| BAM1011 | SetPos file segment number < > not found in retrieved list of backup segments | Teradata Extension for Tivoli Storage Manager cannot find the requested file segment number when a request was made to reposition the file within the backup set. Either the position information is corrupted, or a mismatch occurred between the backup set being requested and the position information. Remedy: Contact a field engineer or Teradata Customer Support. |
| BAM1012 | < > < > error < > < > | Teradata Extension for Tivoli Storage Manager detects an unexpected error when starting a function of TSM. The nature of the error is indicated in the message by naming the TSM product, the API function being called, the error code, and the error message text. This type of error can be difficult to fix. Teradata Extension for Tivoli Storage Manager is customized to work with site-specific APIs, but configuration to work with TSM and ARCMAIN can be complex. Remedy: Correct the job or configuration settings. To run Teradata Extension for Tivoli Storage Manager with an option that is not recognized on the IOPARM of an ARCMAIN job, configure the TSM runtime environment to set the option as a default configuration option. To avoid resubmitting a job, issue a RELEASE LOCK statement on the Teradata Database to remove any database locks set and clean up the server. |
| BAM1013 | Storage object created on platform < > | The backup file being restored was generated on a different operating system. The platform number identifies the operating system that created the backup. Remedy: Resubmit the job on the same platform that created backup. |
| BAM1014 | Invalid Segment name for NameSpace= < >, Pathname= < >, Segment= < >, CopyId= < >. Skipping. | When querying the TSM storage catalog metadata, Teradata Extension for Tivoli Storage Manager found a storage object that qualified on the name pattern, but does not follow the proper naming convention. This is not a fatal error message, but the relevant object is omitted from processing because Teradata Extension for Tivoli Storage Manager cannot properly parse the segment name. Teradata Extension for Tivoli Storage Manager stores segment sequence numbers as part of the file segment name. For example, F0014 corresponds to the 15th file segment of a single ARCMAIN backup file. (File segment numbering starts at zero.) Remedy: Rename the segment name if NameSpace and PathName are too close to the name chosen for another storage process. If the skipped object was created by a Teradata backup operation, report the issue to a field engineer or Teradata Customer Support. |
| BAM1015 | Unable to open diagnostic file < > because < >. Logging disabled. | Diagnostic logging is requested, but Teradata Extension for Tivoli Storage Manager is unable to open the file. This is a non-fatal error, but no diagnostic logging is captured. The cause of the file open error is indicated. Teradata Extension for Tivoli Storage Manager opens the log file in write-append mode. Periodic purging of this file is necessary. Remedy: Correct the problem, and resubmit the job. |
| BAM1017 | Unable to open DEFAULT file < > because < > | Teradata Extension for Tivoli Storage Manager is unable to open the command line DEFAULT file. The cause of the file open error is indicated. The DEFAULT file is specified with the BARAM_DEFAULT environment variable. Remedy: Specify a valid path to a DEFAULT file that is accessible to your user ID, then resubmit the job. |
| BAM1018 | Access Module is aborting the backup transaction | Teradata Extension for Tivoli Storage Manager was called to close the backup file in an error condition. The write transaction is aborted and all storage objects created by this job are rolled back. This is an informational message rather than a report of the root cause of an error condition. ARCMAIN indicates the cause of the error or reports that the backup process is interrupted. Remedy: Correct the root cause of the error and resubmit the job. For further information, refer the output listing to Teradata Customer Support. |
| BAM1019 | Access Module is aborting due to Insufficient Memory | This error occurs when Teradata Extension for Tivoli Storage Manager runs out of memory while attempting to allocate resources. A number of conditions can cause insufficient memory, including a lack of memory or swap space. Remedy: Correct the root cause of the error, then resubmit the job. |