Teradata SQL Error and Failure Codes from Error 9134 To 9141

9134 %VSTR
Explanation: An error was generated during processing of a fastpath function. Exact UDT error code and corresponding
message are given within VSTR.
Generated By: FPF subsystem.
For Whom: Fastpath function Developer, End User.
Remedy: Take appropriate action based on the value of VSTR.

9135 Maximum number of UDT handles exceeded in UDM/UDF %DBID.%TVMID.
Explanation: The UDM/UDF has exceeded the maximum number of UDT handles that may be allocated by the
FNC_GetStructuredAttribute function. This may be caused by a logic error in the UDF resulting in the execution of an
unbounded loop.
Generated By: FNC_GetStructuredAttribute
For Whom: UDM/UDF developer
Notes: The maximum number of UDT handles that may be allocated in one UDM/UDF execution is 2000.
Remedy: Modify the UDM/UDF.

9136 Online archive logging cannot be enabled on one or more tables.
Explanation: This warning will be reported at one or more of the following condition :
– This is an aborted multiload target table in apply phase. – This is an aborted multiload work table. – This is an aborted fastloading
table. – This is a global temporary table. – This is a LDI table that is in pending load state.
Generated By: AMP Software(STPLOGARCON).
For Whom: End User.
Remedy: Completed the aborted load table then resumbiting the “online archive logging on” statement.

9137 Expand complete and exit.
Explanation: This error is returned to sutexpand.c for graceful exit from the expansion loop. This error is not intended
for end user.
Generated By: EVL (evlexpand)
For Whom: sutexpand.c (To gracefully exit from the expansion loop).
Remedy: NA.

9138 Invalid ANCHOR expression in the BY clause.
Explanation: This error may be reported if an invalid ANCHOR expression is is used in the BY clause.
Generated By: EVL (evlexpand)
For Whom: End User.
Remedy: Re-submit the request with the correct ANCHOR expression.

9139 Invalid unique primary index.
Explanation: When an ExpReq from mgc was attempted using a key, no row was found that contained the key value
and the dictionary table was read with access lock.
Generated By: ExpRer, ExpRar, and ExpRst.
For Whom: GSC
Notes: This is an internal error that should be handled by other procedures. It should not handled by other procedures. It
should not cause a crash or be reported to users.
Remedy: Redo the ExpReq with read lock only.

9140 No current row defined.
Explanation: In an express request from mgc was attempted using a USI, no row was found and the dictionary table was
read with access lock.
Generated By: ExpRsi.
For Whom: GSC
Notes: This is an internal error that should be handled by other procedures. It should not cause a crash or be reported to
users.
Remedy: Redo the ExpReq with read lock only.

9141 Sample Spool Row Count Exceeded.
Explanation: This error message occurs when the number of rows in the sample spool exceeds the supported limit of
4294967295 rows for the sample rows.
Generated By: AMP.
For Whom: End User.
Remedy: Correct and re-submit the query to ensure that fewer than 4294967295 rows are requested as a sample.

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