Teradata SQL Error and Failure Codes from Error 9651 To 9664

SQLServerF1_Header_Small

9651 End of partition encountered in row-column subsystem.
Explanation: Compressed value encountered for a container row but it’s AC bitis off.
Generated By: Row Column Subsystem
For Whom: Site support representative.
Notes: This error is returned by the row-column subsystem. It is only returned to the client when the error is not one of
the possible expected error codes in the calling routine.
Remedy: Contact your System Representative.

9652 End of partition encountered in row-column subsystem.
Explanation: Container row context is not initialized for sticking a value in it.
Generated By: Row Column Subsystem
For Whom: Site support representative.
Notes: This error is returned by the row-column subsystem. It is only returned to the client when the error is not one of
the possible expected error codes in the calling routine.
Remedy: Contact your System Representative.

9653 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9654 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9655 Insufficient free space in a container row for appending a column-partition value.
Explanation: This error indicates that there is insufficient free space available in a container row for sticking a columnpartition
value.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9656 Insufficient space available for the compression dictionary of a container row.
Explanation: This error occurs when there is insufficient buffer space for the compression dictionary of a container row
of a column-partitioned table.
Generated By: Row-Column Subsystem
For Whom: Site support representative.
Notes: This error is returned as an internal error to the client when the error is not one of the expected error codes in the
calling routine.
Remedy: Contact your Support Representative.

9661 Column partition row counts do not match with other column partition row counts.
Explanation: Column partition row counts do not match with other column partition row counts.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

9662 Transaction was recovered.
Explanation: An a redrive-enabled transaction with at least one completed request was recovered by system recovery.
Any uncompleted requests were rolled back, and the transaction remains open. This is an informational code that is handled
internally by the Dispatcher and should not be visible to the end user.
Generated By: AMP
For Whom: Internal only.
Remedy: No remedy is necessary. The transaction may proceed as normal.

9663 Hash ownership check failed on AMP %d for %DBID.%TVMID.
Explanation: This message indicates that the database attempted to insert a row on the wrong AMP.
Generated By: AMP
For Whom: Field Engineer or the concerned site support representative.
Notes: This is an internal error.
Remedy: Contact your Support Representative.

9664 An incorrectly formatted container is detected.
Explanation: An incorrectly formatted container is detected during a level 3 CheckTable of a column-partitioned table or
join index. The following are examples of incorrect settings in a container: 1. The container has autocompression enabled and the offset to the last set of autocompression bits is out-of-bounds of the length of the container. 2. The first presence byte of the container indicates autocompression is to be determined and also indicates the container is using autocompression
types of local value dictionary compression, run length compression, or both. 3. The offset to free space is out-ofbounds
of the length of the container.
Generated By: CheckTable
For Whom: Site support representative
Remedy: Contact your Support Representative.

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