Teradata SQL Error and Failure Codes from Error 5954 To 5960

SQLServerF1_Header_Small

5954 Internal error: Inconsistency in the PPI descriptor of the table header.
Explanation: While checking a table header for the specified table, inconsistencies were found in the PPI descriptor.
Generated By: DBS, CheckTable, Ferret.
For Whom: System Support Representative.
Remedy: Save all information and contact your support representative. ALTER TABLE with the REVALIDATE PRIMARY
INDEX option may correct the problem.

5955 Warning: Table headers have been revalidated but correct partitioning of the rows needs to be verified.
Explanation: While revalidating a table header for the specified table during an ALTER TABLE that defines new partitioning
expression using DROP/ADD RANGE or during an ALTER TABLE with REVALIDATE PRIMARY option but no
WITH option, the table headers for the table were corrected but the rows may be inconsistently partitioned per the updated
table headers. If so, queries that are executed with partition elimination may get wrong results. This warning indicates the
table header for the table was created in an earlier release with a partitioned primary index where one or more of the partitioning
expressions were nondeterministic (contained time or timestamp constants without time zone, or AT LOCAL
clause) or that some internal error occurred to cause an inconsistency in the table headers.
Generated By: Opt.
For Whom: End User and System Support Representative.
Notes: This is a warning but it is important to follow the instructions in the following remedy to make sure the rows are
correctly partitioned.
Remedy: It is recommended that you contact your System Support Representative to assist in applying this remedy. Run
the following query to verify if rows are correctly partitioned: SELECT COUNT(*) AS “TOTAL ROWS”, SUM( CASE
WHEN PARTITION#L1<>partitioning_expression_1 OR PARTITION#L2<>partitioning_expression_2 OR … OR PARTITION#
Ln<>partitioning_expression_n THEN 1 ELSE 0 END) AS “ROWS INCORRECTLY PARTITIONED” FROM
table_name;
If the number of rows incorrectly partitioned is zero, no further action is necessary. If the number of rows incorrectly partitioned
is significantly less than the total number of rows (less than 1%) or the table is small, submit an ALTER TABLE
table_name REVALIDATE PRIMARY INDEX WITH DELETE/INSERT statement to correctly partition the rows (use the
WITH INSERT option if it is desired to capture any rows that may be deleted if they do not belong to any partition). If there
are too many rows incorrectly partitioned, recreating the table and re-populating will probably be more efficient. The rows
for the original table can be insert-selected from the original table into the new table or if there is not enough space on the
system, the new table may be re-populated from a backup.

5956 A range start or end must not specify leap seconds.
Explanation: In RANGE_N function, a range start or end(a constant expression) must not result in a time or timestamp
value that specifies leap seconds (that is, seconds is greater than 59.999999). Note that a range ending with seconds of
59.999999 includes test values with leap seconds.
Generated By: OPT module.
For Whom: End User.
Remedy: Change the range start or end to not specify leap seconds and resubmit the re- quest.

5957 Warning: An existing partitioning expression is nondeterministic.
Explanation: During an ALTER TABLE that defines new partitioning expressions using DROP/ADD ranges or an
ALTER TABLE with REVALIDATE PRIMARY option, an existing partition expression was found to be nondeterministic. If
so, queries that are executed with partition elimination may get wrong results and rows may be improperly partitioned.
This warning indicates the table was created in an earlier release with a partitioned primary index where one or more ofthe partitioning expressions were nondeter- ministic. Note that nondeterministic partitioning expressions are not supported
(a partitioning expression must be deterministic) but an error was not reported in all cases in earlier releases.
Generated By: Opt.
For Whom: End User and System Support Representative.
Notes: This is a warning but it is important to follow the instructions in the following remedy to make sure the rows are
correctly partitioned.
Remedy: It is recommended that you contact your System Support Representative to assist in applying this remedy. Recreate
the table with deterministic partitioning and repopulate. The rows for the original table can be insert-selected from
the original table into the new table or if there is not enough space on the system, the new table may be repopulated from a
backup. If you run all maintenance, queries, and ALTER TABLE statements for this table in the same session time zone, session
collation and session mode (ANSI or BT/ET), rows may be okay in the table and you may decide to delay applying
this remedy; however, it is highly recommended to apply the remedy at the soonest opportunity.

5958 Warning: A partitioning expression or join index search condition is nondeterministic.
Explanation: A partitioning expression in a CREATE TABLE, ALTER TABLE, or CREATE JOIN INDEX or search condition
in a CREATE JOIN INDEX was found to be nondeterministic. Queries that are executed with partition elimination
may get wrong results and rows may be improperly partitioned. This warning indicates the table was created in an earlier release with a partitioned primary index where one or more of the partitioning expressions were nondeterministic. Note
that nondeterministic partitioning expressions are not supported (a partitioning expression must be deterministic) but an error was not reported in all cases in earlier releases.
Generated By: Opt.
For Whom: End User and System Support Representative.
Notes: This is a warning but it is important to follow the instructions in the following remedy to make sure the rows are correctly partitioned.
Remedy: It is recommended that you contact your System Support Representative to assist in applying this remedy. Recreate the table with deterministic partitioning and repopulate. The rows for the original table can be insert-selected from
the original table into the new table or if there is not enough space on the system, the new table may be repopulated from a backup. If you run all maintenance, queries, and ALTER TABLE statements for this table in the same session time zone, session collation and session mode (ANSI or BT/ET), rows may be okay in the table and you may decide to delay applying this remedy; however, it is highly recommended to apply the remedy at the soonest opportunity.

5959 Statistics on system-derived column “%VSTR” is not allowed.
Explanation: COLLECT/DROP/HELP STATISTICS on a system-derived column PARTITION#Ln (where n is between 1
and 15, inclusively) is not allowed.
Generated By: RES modules.
For Whom: End User.
Remedy: Do not resubmit this statement or collect statistics on the system-derived col-umn PARTITION and/or the partitioning
columns instead.

5960 Internal error: Invalid level number for an internal to PARTITION#Ln conversion.
Explanation: An attempt was made to convert an internal partition number to a PARTITION#Ln value using an invalid
level number. This is an internal error.
Generated By: OPT and EVL modules.
For Whom: System Support Representative.
Remedy: Save all relevant information and notify your support representative.

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