Teradata SQL Error and Failure Codes from Error 5679 To 5690

SQLServerF1_Header_Small

5679 Exceeded the limit of 64 stratum.
Explanation: Atmost 64 stratum are allowed in stratified sampling
Generated By: OPT modules
For Whom: End-User
Remedy: Reduce the number of stratum defined to less than 64

5680 Stratified sampling not allowed with triggers.
Explanation: Stratified Sampling is not allowed with triggers
Generated By: OPT modules
For Whom: End-User
Remedy: Remove the reference to stratified sampling in triggers.

5681 Stratified sampling not allowed in Fast exports/Multiload.
Explanation: Stratified Sampling is not allowed with fast export,multiload etc
Generated By: OPT modules
For Whom: End-User
Remedy: Remove the reference to stratified sampling with fast export/multiload

5682 User has insufficient SPOOL space.
Explanation: The user tried to give more SPOOL space to a profile than what the user has available.
Generated By: OPD modules.
For Whom: The DBA and the End User.
Remedy: Either decrease the SPOOL space specified for the profile or increase the SPOOL space of the user if possible.

5683 User has insufficient TEMPORARY space.
Explanation: The user tried to give more TEMPORARY space to a profile than what the user has available.
Generated By: OPD modules.
For Whom: The DBA and the End User.
Remedy: Either decrease the TEMPORARY space specified for the profile or increase the TEMPORARY space of the user
if possible.

5684 A profile may not be assigned to user DBC.
Explanation: User DBC cannot be assigned any profiles.
Generated By: RES modules.
For Whom: Site Administrator.
Remedy: Check the name of the user to be assigned the profile.

5685 %VSTR is not supported on LOB columns.
Explanation: A LOB column is not allowed in FastExport, FastLoad, MultiLoad.
Generated By: OPH modules (ophexpda, ophlin, ohpedins, ophedupd, opheddel).
For Whom: End User.
Remedy: Remove LOB column in the query.

5686 %VSTR cannot be used on a LOB column.
Explanation: A LOB column can not have these attributes: compress, default, constraint,…
Generated By: OPU modules (opubflds, opdmodta, opuconeq, opuhsheq).
For Whom: End User.
Remedy: Remove LOB column in the query.

5687 REFERENTIAL INTEGRITY is not allowed on LOB columns.
Explanation: A LOB column is not allowed in Referential Integrity.
Generated By: OPU modules (opucldrf).
For Whom: End User.
Remedy: Remove LOB column in the query.

5688 Unwind the stack to the most outer logmark.
Explanation: Unwind the stack for the task to the most outer logmark.
Generated By: mgcexprq
For Whom: Internal only.
Remedy: This operation is only internal to the DBS. When the SqlDrivr (combo) task picks up an abort message while
waiting for an express request response, we simply unwind the stack to the most outer logmark which is placed in DisDrivr
so that the abort message could be processed right away.

5689 LOBs are not allowed to be compared.
Explanation: LOBs are not allowed to be compared with equals, less than, greater than, etc.
Generated By: OPT modules.
For Whom: End User.
Remedy: Remove the comparison and resubmit.

5690 LOBs are not allowed to be hashed.
Explanation: LOBs are not allowed to be hashed. Hashing is required for UNION, INTERSECT, MINUS, and DISTINCT
queries containing LOB columns or for ORDER BY’s on LOB columns or for select query with SAMPLE clause specified on
LOB columns.
Generated By: OPT modules.
For Whom: End User.
Remedy: Remove the LOB column and resubmit.

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