Teradata SQL Error and Failure Codes from Error 5961 To 5970

SQLServerF1_Header_Small

5961 Error during unsupported request: %VSTR
Explanation: An error occurred during the parsing of an unsupported SQL statement which exists for support and diagnostic purposes only. Additional information regarding the nature of the failure is provided in the text of the error message
for support personnel.
Generated By: SYN and PAR modules.
For Whom: End User, and System Support Representative.
Remedy: The SQL request encountering this error is unsupported. Please do not re-issue the request.

5962 %VSTR
Explanation: This is a warning only, not an error. This warning can occur during the processing of an unsupported SQL
statement which exists for support and diagnostic purposes only. Additional information regarding the nature of the warning is provided in the text of the warning message for support personnel.
Generated By: SYN and PAR modules.
For Whom: End User, and System Support Representative.
Remedy: None, this is an informational message.

5963 EACH clause not supported for character or graphic test value.
Explanation: A RANGE_N function was specified where the data type of the test value was CHAR, VARCHAR,
GRAPHIC or VARGRAPHIC, and an EACH clause was specified. This combination is not supported.
Generated By: OPT modules.
For Whom: End User.
Remedy: Rewrite the RANGE_N expression to specify each range individually, or use a test value of integer or DATE
data type.

5964 Session collation does not match PPI collation.
Explanation: An operation on a character partitioned primary index was attempted that is only allowed when the session
collation matches the collation of the PPI.
Generated By: OPT modules.
For Whom: End User.
Remedy: Retry the operation using the same session collation as the PPI collation. The PPI collation of a permanent table or join index with a partitioned primary index can be looked up in columns ConstraintCollation and CollationName of DBC.IndexConstraints. When ConstraintCollation is ’C’, the collation is CHARSET_COLL with CollationName and Char-
SetID indicating the character set used for the collation. Set the session collation the same as the PPI collation and retry the operation.

5965 PPI collation character set is not installed.
Explanation: An operation on a character partitioned primary index was attempted that is not allowed because the PPI
is collated by a client character set that is no longer installed.
Generated By: OPT modules.
For Whom: End User.
Notes: Only the first sixteen character sets (in ascending order by TranslateName in DBC.Translation) marked with a
value of DBC.Translation.Install as ’Y’ will be installed.
Remedy: Make sure the PPI collation character set is installed in DBC.Translation. The PPI collation character set of a
permanent table or join index can be looked up in columns CollationName and CharSetID of DBC.IndexConstraints.

5966 Too many data records packed in one USING row.
Explanation: User has defined too many data records in one USING row. The limit is 16383.
Generated By: PAR modules.
For Whom: End User.
Remedy: Correct the request and resubmit it.

5967 The table being dropped has an error table.
Explanation: The user tried to drop a table that has an associated error table.
Generated By: OPD module.
For Whom: End User.
Remedy: Drop the error table, and re-submit the query.

5968 Atomic UPSERTS are not allowed in Multiload.
Explanation: Atomic UPSERTS are not allowed in Multiload.
Generated By: Syntaxer
For Whom: End User.
Remedy: Rewrite UPSERT with Update and Insert separately with the following syntax.
DO INSERT FOR MISSING UPDATE ROWS; UPDATE … WHERE PK=…; INSERT …;

5969 The database ’%VSTR’ has tables with error tables defined in another database.
Explanation: The above error is generated when a user submits a DELETE DATABASE command on a database that
contains tables with error tables defined in some other database. The DELETE is disallowed in order to avoid orphaned
error tables.
Generated By: OPD module(opddeldb)
For Whom: End User or Field Engineer or the concerned site support Representative.
Notes: Find all the error tables that are defined on the tables in the database being deleted by using the following command:
SELECT BaseTblDbName, BaseTblName, ErrTblDbName, ErrTblName FROM DBC.ErrorTblsV WHERE BaseTblDbName
<> ErrTblDbName AND BaseTblDbName = CurrentDBName;
where <CurrentDBName> is the database name of the database being deleted.
Remedy: Drop all error tables from the above list and re-submit the DELETE DATABASE command.

5970 Table function has too few/many output arguments.
Explanation: The number of output arguments for a table function must be between 1 and 2,048, inclusively.
Generated By: Resolver
For Whom: End User.
Remedy: Resubmit request with the number of table function ouput arguments in the valid range.

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