Teradata SQL Error and Failure Codes from Error 5266 To 5305

5266 TVS requested a reduction in the amp’s size that could not be done
Explanation: The reduction amout would impact current disk usage
Generated By: File System
For Whom: TVS
Notes: n/a

5267 TVS requested an increase in the amp’s size that could not be done
Explanation: The increase amount would exceed the allowable size for the amp
Generated By: File System
For Whom: TVS
Notes: n/a

5268 WARNING: The datablock size for table %s.%s (%04X %04X) is not appropriate based on the
system characteristics. Please examine datablock size distributions and definitions for this table
and consider executing an ALTER TABLE DATABLOCKSIZE IMMEDIATE command or an INSERTSELECT
to a new table.
Explanation: A BAR Restore operation is restoring whole blocks from a table whose archived block sizes are inappropriate for the target system configuration.
Generated By: File System
For Whom: End user of BAR Restore.
Notes: This is an informational message, not a fatal error. The associated table is restored successfully.
Remedy: After completion of the Restore, contact Field Engineer and take appropriate action if necessary.

5269 WARNING: The REBLOCK option will be ignored due to incompatible system characteristics.
Explanation: A BAR Restore operation cannot restore whole blocks from the archive due to incompatible file system
characteristics on the target system. The Restore operation will restore individual rows.
Generated By: File System
For Whom: End user of BAR Restore.
Notes: This is an informational message, not a fatal error. The Restore operation will complete successfully.
Remedy: After completion of the Restore, contact Field Engineer and take appropriate action if necessary.

5270 Headerless spool situation detected.
Explanation: A situation where spool table header on the disk is missing/absent is detected.
Generated By: File System
For Whom: Field Engineer
Notes: This indicates a Data Base System software error. Need to analyze to find the cause of spool header absence.
Remedy: Contact a field engineer.

5300 Foreign Key column ’%VSTR’ cannot reference itself.
Explanation: The Foreign Key and corresponding referenced column cannot be the same. A table can but a column cannot
reference itself.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

5301 The referential constraint has already been defined.
Explanation: The user twice tried to define the same referential constraint on a table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Do not resubmit the request. The referential constraint has already been defined.

5302 A column can appear only once in a Foreign Key/Parent Key.
Explanation: A column that is identified to appear in a Foreign or Parent Key must be unique.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

5303 Error table ’%VSTR’ already exists.
Explanation: Teradata system creates an error table to store target data rows that violate the specified referential constraint when the constraint is added to an existing table via ALTER TABLE statement or an inconsistent referential constraint is revalidated via REVALIDATE REFERENCES statement. The name of the error table is the target table name
appended by the corresponding reference index number. If a table with that name has already existed in the system, then
this error is returned.
Generated By: RES modules.
For Whom: End User.
Remedy: Drop the table in conflict, and resubmit request.

5304 Foreign Key column ’%VSTR’ cannot be dropped.
Explanation: A Foreign Key column cannot be dropped by the ALTER TABLE statement.
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the referential constraint containing that Foreign Key column with an ALTER TABLE DROP FOREIGN
KEY … statement, and resubmit the request.

5305 Foreign Key column ’%VSTR’ cannot be modified.
Explanation: A Foreign Key column cannot be modified using by the ALTER TABLE statement.
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the referential constraint containing that Foreign Key column with an ALTER TABLE DROP FOREIGN
KEY … statement, and resubmit the request.

Above are list of Teradata Errors or Failure Codes from Error 5266 To 5305 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 *