Teradata SQL Error and Failure Codes from Error 5317 To 5331

SQLServerF1_Header_Small

5317 Check constraint violation: Check error in field %TVMID.%FLDID.
Explanation: The user tried to place data in a table/view whose CHECK definition does not allow the user- supplied
value.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the values of the columns referenced in the check constraint and resubmit the request.

5319 The specified DATABLOCKSIZE value %VSTR
Explanation: The specified DATABLOCKSIZE value is invalid. Please reference the Teradata Database Design Manual
for the permissible range for the current release.
Generated By: GNS modules.
For Whom: End user.
Remedy: Correct DATABLOCKSIZE value and resubmit request.

5320 The specified FREESPACE value is not between 0 and 75 percent.
Explanation: The allowable range for the FREESPACE value is 0 to 75 percent.
Generated By: GNS modules.
For Whom: End user.
Remedy: Correct FREESPACE value and resubmit the request.

5321 Constraint, primary index, or secondary index with the same name “%VSTR” already exists in table.
Explanation: The constraint, primary index, or secondary index name must be unique in a table regardless of constraint
type.
Generated By: RES and OPT modules.
For Whom: End User.
Notes: Names of join indexes and hash indexes must be unique within a database. For example, a join index must not
have the same name as a table in the same database but it may have the same name as a constraint, primary index, or secondary
index as in a table on which the join index is defined.
Remedy: Give the constraint or index a different name and resubmit the request.

5322 The specified constraint name ’%VSTR’ does not exist.
Explanation: The user tries to drop/display a non-existent constraint.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not resubmit request. No such constraint name exist.

5323 The %FSTR column ’%VSTR’ must be NOT NULL.
Explanation: The PRIMARY KEY or UNIQUE column(s) must be NOT NULL.
Generated By: RES modules.
For Whom: End User.
Remedy: Change the attribute of the Primary Key/Unique column(s) to NOT NULL then resubmit the request.

5324 The referenced table %DBID.%VSTR does not have a Primary Key defined.
Explanation: If referenced (Parent Key) columns are not specified in a referential constraint, it defaults to the unique constraint that specifies PRIMARY KEY in the referenced (Parent) table. This error will be returned if the referenced table does not have such unique constraint (PRIMARY KEY) defined.
Generated By: RES/OPT modules.
For Whom: End User.
Remedy: Specify referenced columns of the unique constraint and resubmit the request.

5325 Length 0 is not allowed for a CHAR, VARCHAR, BYTE, VARBYTE column.
Explanation: A column of type CHAR, VARCHAR, BYTE, VARBYTE of a table can not defined of length 0.
Generated By: SYN
For Whom: End User.
Remedy: Change the length of columns to values different than 0.

5326 Operand of EXTRACT function is not a valid data type or value.
Explanation: The argument of EXTRACT must be an appropriate DateTime type or for a Time field, may be a REAL
value, but the value must be in the appropriate range for TIME stored in a REAL value.
Generated By: Optimizer or Evl procedures.
For Whom: End User.
Remedy: Check the data type of the operand. If the data type is REAL and a time field is being extracted, check that the
column or source involved contains Time values.

5327 ADD_MONTHS has been called with wrong data types or values.
Explanation: The first argument of ADD_MONTHS must be of the TDBS DATE Type, and the second argument must be
a BYTEINT,SMALLINT or INTEGER. The values of the first argument, DATE, and the second, MONTHS, must be in
ranges such that the resulting date has a Year value between 0000 and 3500.
Generated By: Optimizer or Evl procedures.
For Whom: End User.
Remedy: Use values of proper types and ranges.

5331 More than 2,000 temporary tables materialized in the current session.
Explanation: The number of materialized temporary tables produced by the requests in current session has exceeded the
maximum allowed, which is currently set to 2,000 (SysMaxTmpTblPSn).
Generated By: RES modules
For Whom: End User.
Remedy: Reduce usage of temporary tables.

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