Invalid Segment name for NameSpace=<TDname>, Pathname=<image_basename>, Segment=<segment_no>, CopyId=<xx>. Skipping.
| Explanation: | When querying the vendor's storage catalog metadata, the access module picked up a storage object that qualified on the name pattern but which does not follow the proper naming convention. This is not a fatal error message but the relevant object is skipped from processing. |
| For whom: | End User/Field Engineer |
| Notes: | The convention used by the access module is to store the segment sequence number as part of the file segment name. For example, F0014 would correspond to the 15th file segment of a single ARCMAIN backup file (file segment numbering starts at zero). The precise cause of this error is that the access module is unable to parse the segment name properly. |
| Remedy: | If the segment name is getting picked up because the NameSpace and PathName you are using is too close to the name chosen for some other storage process, then just pick a different name. If the skipped object really was created by a Teradata backup operation then this error suggests a software bug. Report the situation to your local Field Engineer or Global Support. |