Teradata SQL Error and Failure Codes from Error 9624 To 9650

SQLServerF1_Header_Small

9624 Logical row for a specified RowID does not exist or is marked as deleted.
Explanation: A logical row was located but a column-partition value was not found for it or the logical row is marked as
deleted. This can occur if an access lock is being used and the logical row was deleted by another session or an insert or
update attempted by another session was rolled back.
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.

9626 Null column-partition value encountered in the row-column subsystem.
Explanation: This error indicates all column values in the column-partition value are null.
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.

9628 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.

9629 Insufficient buffer space for appending a column-partition value to a container row.
Explanation: This error occurs when there is insufficient buffer space available (that is, buffer is full) for appending a new column-partition value to a container row.
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 Support Representative.

9630 Unable to compress null value for a container row.
Explanation: This error occurs when attempting to append a null column-partition value to a container row and autocompression
is not being used for this container row or, if auto-compression is being used for this container row, that the
auto-compression types for this container row do not allow for nulls.
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.

9632 Container row cannot be compressed.
Explanation: This error occurs when no compression techniques are applicable to a container row.
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.

9634 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.

9650 End of partition encountered in row-column subsystem.
Explanation: A read past the end of a column-partitioned table row partition during search mode was encountered.
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.

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