Teradata SQL Error and Failure Codes from Error 9112 To 9125

SQLServerF1_Header_Small

9112 No more FastExport blocks on the session.
Explanation: This error is returned when there are no more data blocks to be exported for the FastExport session.
Generated By: LCT Modules.
For Whom: FastExport Utility and interfaces using the FastExport Protocol
Remedy: Check all sessions with outstanding requests and begin completion processing.

9113 Insufficient security credentials for operation on one or more rows, or constraint input value
of zero is detected.
Explanation: The INSERT or UPDATE operation on an RLS-protected table failed security policy checks defined in the
constraint function for the statement kind. If the user has override constraint privilege for the operation, the warning is also
returned if an input value specified for the constant column is zero.
Generated By: SUT module.
For Whom: End User.
Remedy: This message is for information only.

9114 Invalid input value of %VSTR for constraint column ’%DBID’.
Explanation: An input value for the named security constraint column is invalid. If it is a non-set constraint column, the
invalid constraint value will be displayed. If it is a set constraint column, the byte string input value will be displayed.
Generated By: SUT module.
For Whom: End User.
Remedy: Correct the input value and re-submit the request.

9120 Corruption detected in NUSI or CDT index, index %VSTR invalidated on %DBID.%TVMID. Drop
and re-create the index.
Explanation: Corruption was detected in the NUSI or CDT index during index maintenance. The index has been invalidated
to avoid further problems and a DBS restart.
Generated By: AMP Steps.
For Whom: End User and Site support representative.
Remedy: Drop the invalidated secondary or CDT index on the table and re-create it. Using the table with an invalid secondary
or CDT index is not recommended.
To determine which index has been invalidated on the table, please refer to the error code 9120 in the event log. Alternatively,
run CheckTable on the affected table to determine the invalid secondary or CDT indexes.

9121 Invalid jar name(s) found.
Explanation: This error is returned if while performing a database/table restore a jar name is found violating the following naming convention:
1. Cannot be ’RETURNS’, ’JAVFNC’, ’TERAJDBC4’, ’TDGSSJAVA’, ’TDGSSCONFIG’. 2. Contains only alphanumeric characters
with the exception of the symbols ’#’, ’$’, ’.’, ’-’, ’_’.
Generated By: hutinr.
For Whom: End User.
Remedy: Run the migration script, verify_jar_name_migration.pl, to get a list of the jars with invalid names. Correct the
names, then try again.

9122 Left-over index work block detected.
Explanation: This error occurs when a left-over index work datablock is detected. Note that index work blocks are created
after a sormerge operation. These blocks are temporary in nature and are deleted once the purpose is served.
Generated By: Sutsi module
For Whom: End User and Site support representative.
Remedy: Contact your Support Representative.

9123 The row length changed during in-place row generation.
Explanation: When the in-place row modification instructions are used and the row length changes, the row must be rebuilt
This is because the fields after the variable length field that is modified have to be moved. The row cannot be built inplace
for such case. Note that if the row has only fixed length fields, then this does not occur.
Generated By: EVL
For Whom: sutexpand
Remedy: NA.

9124 Segmentation Violation in AMP: Please do not resubmit the last request.
Explanation: This error occurs when a program attempts to access a memory location that it is not allowed to access.
Accessing a nil ptr is one of the cases that leads to segv. The segmentation violation can also be caused by a task stack overflow.
This error could result in transaction abort.
Generated By: AMP Software.
For Whom: Site support representative.
Remedy: Save the snapshot dump. Have all the traceback information ready. Then contact your support representative.

9125 First fault isolation call and recursion not handled, crash now.
Explanation: This error indicates the runaway nested calls to suterrcx, since first fault isolation calls and recursions not
handled, the maximum depth (SUTERRCXDEPTH) is two, if greater than that system will crash.
Generated By: AMP Software.
For Whom: Site support representative.
Remedy: Save the crashdump for offloading. Have all traceback information ready. Then contact your Support Representative.

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