Teradata SQL Error and Failure Codes from Error 1073 to 1084

SQLServerF1

1073 Data File Open Error on directory path:%VSTR.
Explanation: File Open Error on the given directory path.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Check to ensure that the data file exists.

1074 Data File has bad format.
Explanation: Data File DumpHeader is missing.
Generated By: BAR.
For Whom: End user.
Notes: The Data File may be bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1075 Cannot archive/restore objects more than 5200 objects.
Explanation: Maximum number of objects which can be archived/restore reached.
Generated By: BAR.
For Whom: End user.
Notes: This is a 14.10 restriction.
Remedy: Change the job plan and submit again.

1078 Unknown record type is %VSTR.
Explanation: Unknown record type found.
Generated By: BAR.
For Whom: End user.
Notes: The dump may be bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1079 Post dbc restore script not started. Please run the post_dbc_restore script manually with the following command: %VSTRdbc_password.
Explanation: Did not start post dbc restore script due to system not being quiescent.
Generated By: BAR.
For Whom: End user.
Notes: None.
Remedy: Please make sure the system is quiescent and then run the post_dbc_restore script manually.

1080 Possible data file corruption: Multiple DUMPHEADER records found.
Explanation: Multiple dump header records found.
Generated By: BAR.
For Whom: End user.
Notes: The dump is bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1081 Possible data file corruption: Amp Info Record missing.
Explanation: Amp Info record missing.
Generated By: BAR.
For Whom: End user.
Notes: The dump is bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1082 Possible data file corruption: No ENDOBJECT record found between DATASEGMENTS.
Explanation: End object record missing between datasegments.
Generated By: BAR.
For Whom: End user.
Notes: The dump is bad..
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1083 Possible data file corruption: Found ENDOBJECT record that does not match current DATASEGMENT records.
Explanation: End object record does not match current datasegment.
Generated By: BAR.
For Whom: End user.
Notes: The dump is bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

1084 Possible data file corruption: Reached EOF without finding ENDOBJECT.
Explanation: Data File Corruption as reached EOF without finding ENDOBJECT.
Generated By: BAR.
For Whom: End user.
Notes: The dump is bad.
Remedy: If possible, please take a new dump. Otherwise, contact field engineer.

Above are list of Teradata Errors or Failure Codes from Error 1073 to 1084 received while performing certain operation against Teradata Database or related products.

What are Teradata Database Errors?

In general, each Teradata error message contains the following information:
• The message number.
• The message text. This text is usually returned with the message number. Some messages employ word substitution, where the word substituted represents the system-replacement of a term more specific to the occurrence.
• An explanation of how the error may have occurred.
• Generated-by text that indicates the software module which initiated the message. This field serves a diagnostic purpose for support and development personnel.
• A remedy which suggests how to resolve the condition.

Hope this was helpful.

Thanks,
SQLServerF1 Team
Information about Teradata SQL Error and Failure Codes and Error Messages on Windows, Linux Operating Systems.

 

Leave a Reply

Your email address will not be published. Required fields are marked *