Teradata SQL Error and Failure Codes from Error 9142 To 9149

SQLServerF1_Header_Small

9142 %NSTR was aborted while decompressing ALC field id %VSTR due to error %d.
Explanation: This message indicates that while decompressing an ALC column in a table, the filer utility had problems
due to which the table reading is aborted.
Generated By: AMP
For Whom: End user or Field Engineer or the concerned site support representative.
Remedy: Check the aborted table(s) and if the problem persists contact support personnel.

9143 Auto CHECKTABLE mode found errors.Debugger is running.
Explanation: This error indicates that CHECKTABLE encountered at least one error while validating the ALL TABLES.
Since debugger is running, a GO AFTERTRAP will continue from this point without any harm.
Generated By: DBS Auto CHECKTABLE mode.
For Whom: SE/FE.
Notes: Auto CHECKTABLE mode is enable/disabled by the RcvACUTL console startable utility.
When enabled, CHECKTABLE is automatically run on all tables immediately after startup has set up for transaction recovery
(ie. voted and placed all required locks).
To find out exactly which tables had errors, the auto CHECKTABLE mode should be disabled, the system should be
restarted and CHECKTABLE should be run manually. Alternatively, if the debugger is running, a GO AFTERTRAP will
allow the system to continue and then a manual CHECKTABLE can be run.
Remedy: See notes

9144 Serious SAS EP error occurred, see system log for details.)
Explanation: An error was generated during processing of SAS VM UDF. Exact UDT error code and corresponding message
are given within VSTR. This error is used by SAS VM users to debug SAS VM.
Generated By: FPF subsystem.
For Whom: SAS VM Users.
Remedy: Take appropriate action based on the value of VSTR.

9145 %VSTR for %DBID.%TVMID. Please do not submit any request using this table.
Explanation: This error occurs when mini check detects that the index for the specific table is corrupt, which may lead to
wrong result or DBS crash. Don’t perform any operation on this table.
Generated By: EIX module.
For Whom: End User and Site support representative.
Remedy: Contact your Support Representative immediately. A mini check note is available for further investigation.

9146 Block pointer in GeoSpatial Index is corrupted.
Explanation: This error occurs when a bad pointer in a directory or leaf block is detected. A Geospatial Index is physically
stored in Hilbert RTREE organized as a multilevel hierachy consisting of N-1 directory levels and 1 leaf level. The
hierarchy is constructed using directory blocks containing directory rows and leaf blocks containing leaf rows. The directory
rows contain pointers that point toward the child blocks in the level below them. The header in each child and directory block contains a pointer that points backward to its parent row. When such a pointer become invalid, the index is
unusable.
Generated By: CheckTable.
For Whom: Site support representative.
Notes: This error can occur in the following situations: 1. The backpointer in the header of leaf block is corrupted. 2. The
backpointer in the header of directory block is corrupted. 3. The pointer in a directory row pointing toward to a child block
is corrupted.
Remedy: Contact your Support Representative immediately.

9147 MBR in GeoSpatial Index is inconsistent.
Explanation: This error occurs when MBR in a child header block is inconsistent with that in its managed directory row
or with the recalculated MBR from each row in the block. All geometric shapes can be approximated by a rectangle in
which the edges of the rectangle enclose the object. The enclosing rectangle, also known as the Minimum Bounding Rectangle
(MBR), serves the role of being an index key in the RTREE implementation.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative immediately.

9148 Largest Hilbert Value (LHV) in GeoSpatial Index is incorrect.
Explanation: This error occurs when a Largest Hilbert Value (LHV) in a directory row is different from a recalculated
LHV from its child block that is pointed by the row.
Generated By: CheckTable.
For Whom: Site support representative.
Notes: A Hilbert Value is a linear value that is associated with a coordinate composed of 2-dimensions. A Hilbert routine
generates the Hilbert value by mapping the (x,y) coordinates of the center point of the MBR to a linear value on a Hilbert
curve.
Remedy: Contact your Support Representative immediately.

9149 Row Count in GeoSpatial Index is incorrect.
Explanation: This error occurs when a row count recorded in a block header is different from the recount from each row
in the block. They should be the same.
Generated By: CheckTable.
For Whom: Site support representative.
Notes: This error can occur in the following situations: 1. The directory row count recorded in a directory block header is
different from the number of directory row in a directory block. 2. The leaf row count recorded in a leaf block header is different
from the number of leaf row in a leaf block. 3. The leaf entries (the number of rowid) recorded in a leaf block header
is different from the number of leaf entries in a leaf block. 4. The directory block count recorded in header block header row
is different from the number of directory block in an entire RTREE. 5. The leaf block count recorded in header block header
row is different from the number of leaf block in an entire RTREE. 6. The leaf row count recorded in header block header
row is different from the number of leaf row in an entire RTREE. 7. The number of leaf entries recorded in header block
header row is different from the number of leaf entries in an entire RTREE.
Remedy: Contact your Support Representative immediately.

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