Teradata SQL Error and Failure Codes from Error 5306 To 5315

5306 Parent Key (Referenced) column ’%VSTR’ cannot be modified.
Explanation: A referenced (Parent Key) column cannot be modified by the ALTER TABLE statement.
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the referential constraint containing the referenced (Parent Key) column, and resubmit request.

5307 Inconsistent referential constraint(s) do not exist.
Explanation: The specified table does not have any inconsistent referential constraints.
Generated By: OPT modules.
For Whom: End User.
Remedy: Do not resubmit the request. No inconsistent referential constraints exist for the specified table.

5308 No such referential constraint.
Explanation: The user tried to drop a non-existent referential constraint.
Generated By: RES, OPT modules.
For Whom: End User.
Remedy: Do not resubmit the request. No such referential constraint exists.

5309 Invalid reference index number.
Explanation: The reference index number specified in the host REVALIDATE REFERENCES statement is not a valid
number. This error message indicates a software bug in the host utility.
Generated By: OPT modules.
For Whom: Host Utility.
Remedy: None.

5310 Cannot validate referential constraint containing inconsistent information.
Explanation: The referential constraint specified in the host REVALIDATE REFERENCES statement cannot be validated.
This can occur if a restored table references a table which has already been dropped. The error message is returned to the host utility such that it can display a message to inform the user to take appropriate actions.
Generated By: OPT modules.
For Whom: Host Utility.
Remedy: The user must submit statement
ALTER TABLE <tablename> DROP INCONSISTENT REFERENCES
to remove inconsistent referential constraints.

5311 The specified constraint is inconsistent. Submit ALTER TABLE DROP INCONSISTENT REFERENCES statement instead.
Explanation: The specified referential constraint is inconsistent and cannot be dropped using the ALTER TABLE DROP
FOREIGN KEY statement. This can occur after the table is restored. The user must submit an ALTER TABLE DROP
INCONSISTENT REFERENCES statement to drop all inconsistent references from the target table.
Generated By: OPT modules.
For Whom: Host Utility.
Remedy: The user must submit statement ALTER TABLE <tablename> DROP INCONSISTENT REFERENCES to
remove inconsistent referential constraints.

5312 Aborted due to a non-valid reference index on %DBID.%TVMID.
Explanation: The table being accessed has a reference index that is not valid. This could have resulted from one of the
following two cases: (1) The target table or other table which references or is being referenced by the target table was rollforward/
back or restored. (2) The target table has some unresolved references because it is referencing some non-existent
tables. For either case, no inserts, updates, or deletes are allowed.
Generated By: OPT modules.
For Whom: End User.
Remedy: For the Roll and Restore case, drop the corresponding referential constraint and resubmit the request. For the
unresolved references case, create all the missing referenced tables and resubmit the request.

5313 Referential integrity violation: cannot drop a referenced (Parent) table.
Explanation: The user tried to drop a table which is referenced by some other table(s).
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the referential constraint which references the target table, and resubmit the request.

5314 Referential integrity violation: cannot delete database ’%VSTR’.
Explanation: The user tried to delete a database which contains a table or tables that reference or are referenced by some other table(s) in a different database.
Generated By: OPT modules.
For Whom: End User.
Remedy: Drop the referential constraint(s) which established the inter-database reference(s), and resubmit request.

5315 %FSTR does not have %VSTR access to %DBID.%TVMID.%FLDID.
Explanation: The user does not have the proper access rights to execute this request, or the owner of the requested view or macro does not have the proper access rights to underlying columns of a table.
Generated By: SQL modules.
For Whom: End User.
Remedy: Obtain the necessary access rights.

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