Teradata SQL Error and Failure Codes from Error 9268 To 9293

SQLServerF1_Header_Small

9268 An SQL UDF cannot be used inside a table/join index/index type.
Explanation: An SQL UDF cannot be used inside a table, join index, or index type definition.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the request based on the above explanation and resubmit it.

9270 SQL UDF cannot be used as an ordering, cast, or transform function.
Explanation: An SQL UDF cannot be used as an ordering, cast, or transform function.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the request based on the above explanation and resubmit it.

9271 The creator does not have %VSTR privilege.
Explanation: The creator of the function does not have the proper access privileges to underlying objects to execute the
function.
Generated By: RES modules.
For Whom: End User.
Remedy: Obtain the necessary access privileges.

9285 System-defined join index row has same row as previous row.
Explanation: Duplicated system defined join index rows are detected as the system defined join index subtables are traversed.
The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9286 System-defined join index row out of order.
Explanation: Out of order system defined join index rows are detected as the system defined join index subtables are
traversed. The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9287 Primary system-defined join index row is on wrong AMP
Explanation: Incorrectly distributed system defined join index rows are detected as the system defined join index subtables are traversed. The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9288 Fallback system-defined join index row is on wrong AMP.
Explanation: Incorrectly distributed system defined join index rows are detected as the system defined join index subtables are traversed. The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9289 Fallback system-defined join index row is in wrong subtable.
Explanation: Incorrectly distributed system defined join index rows are detected as the system defined join index subtables are traversed. The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9290 Closed row found in system-defined join index.
Explanation: Incorrect system defined join index maintance cause this error. Closed system defined join index rows are
detected as the system defined join index subtables are traversed. The row is discarded from the remainder of the checking process.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9291 Data row not indexed by system-defined join index.
Explanation: Unindexed data rows are detected during the check for system-defined join indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9292 Data row indexed multiple times by system-defined join index.
Explanation: Multiply indexed data rows are detected during the check for system-defined join indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9293 System-defined join index row indexes non existent data row.
Explanation: Non existent indexed data rows are detected during the check for system-defined join indexes.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

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