Teradata SQL Error and Failure Codes from Error 5735 To 5746

5735 The primary index columns may not be altered for a nonempty table.
Explanation: For an ALTER TABLE statement, the set of primary index columns must not be altered for a non-empty
table.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request.

5736 DROP RANGE for level %VSTR removes all ranges.
Explanation: An ALTER TABLE statement with DROP RANGE[#Ln] but without ADD RANGE[#Ln] is attempting to
remove all the ranges from the partitioning expression. This is not allowed.
Generated By: OPD modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the partitioned
primary index rules and resubmit the request.

5737 Triggers not disabled for %VSTR for an ALTER TABLE.
Explanation: If the %VSTR is the table being altered, any existing delete triggers must be disabled for table %VSTR
when WITH DELETE or WITH INSERT option is specified. If %VSTR is the save table, any existing insert triggers must be
disabled for table %VSTR when WITH INSERT option is specified.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Disable or drop the appropriate triggers for the table prior to an attempt to modify or revalidate the primary
index of a table.

5738 Invalid save table for an ALTER TABLE.
Explanation: The specified save table is the same as the table being altered or it does not have the same number of columns
with compatible data types as the table being altered. This is not allowed.
Generated By: RES modules.
For Whom: End User. **DR62813-bessc**
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to ALTER
TABLE rules and resubmit the request.

5739 Column %VSTR is a partitioning column and cannot be dropped.
Explanation: A partitioning column cannot be dropped by an ALTER TABLE statement.
Generated By: OPT modules. **DR62813-bessc**
For Whom: End User. **DR62813-bessc**
Remedy: If the column needs to be dropped, alter the partitioning expression such that the column is not a partitioning
column or remove partitioning from the primary index. Then resubmit the ALTER TABLE to drop the column.

5740 Column %VSTR is a partitioning column and cannot be altered.
Explanation: A partitioning column cannot be modified by an ALTER TABLE statement unless the modification does
not change the data type, nullability, or name of the column.
Generated By: OPT modules. **DR62813-bessc**
For Whom: End User. **DR62813-bessc**
Remedy: If the column needs to be altered, alter the partitioning expression such that the column is not a partitioning
column or remove partitioning from the primary index. Then resubmit the ALTER TABLE to alter the column. If desired,
the partitioning may then be altered to include the column.

5741 The partitioning column values are mismatched in the UPSERT statement.
Explanation: The user specified different partitioning column values for the UPDATE and the INSERT parts of an
UPSERT statement. The same partitioning column values must be used in both parts of an UPSERT statement.
Generated By: GNC Apply.
For Whom: End User. **DR62813-bessc**
Remedy: Correct the UPSERT statement and resubmit.

5742 The UPDATE part of the UPSERT does not fully specify values for the partitioning columns.
Explanation: The UPDATE part of the UPSERT statement must fully specify values for all the partitioning columns by
specifying an equality constraint on each of the partitioning columns to an expression having the same data type and not
containing column references.
Generated By: Parser.
For Whom: End User. **DR62813-bessc**
Remedy: Correct the UPSERT statement and resubmit.

5744 System-derived column “%VSTR” not allowed to be updated.
Explanation: The user attempted to update a system-derived column.
Generated By: RES modules.
For Whom: End User.
Remedy: Don’t update system-derived columns.

5745 PARTITION cannot be determined due to internal error. Please do not resubmit request.
Explanation: A primary (or fallback if an AMP is down) data row has an invalid internal partition number. Therefore, a
valid external partition number cannot be returned for the system-derived column PARTITION[#Ln]. Because of this internal
error, a snapshot dump is taken and the request is aborted.
Generated By: EVL
For Whom: End user and site support representative.
Remedy: Save a test case and contact your support representative for an analysis of the snapshot dump. Additionally,
run CHECKTABLE at level 3 to look for other anomalies in the table and, if any, report them to your support representative.
DR67353-NDFSDBSE-01 : Removed compilation warnings. * <- DR53763-al151002-01 * * <<<–DR53763-bessc-01 V2R5 PPI

5746 The partitioning expression for level %VSTR is not valid; partitioning expressions for multilevel partitioning must be RANGE_N or CASE_N functions.
Explanation: For a CREATE TABLE or ALTER TABLE statement, if more than one parti-tioning expression is specified in
the PARTITION BY clause, each such partitioning expression must consist solely of either a RANGE_N or CASE_N function. The partitioning expression at the specified level is neither solely a RANGE_N nor CASE_N function. Note that it is
not required that the parti-tioning expressions be all of one form or the other (some could be RANGE_N functions and others
CASE_N functions).
Generated By: RES modules.
For Whom: End User.
Remedy: Examine the SQL statement and verify that the request is correct. Change the statement to adhere to the multilevel
partitioned primary index rules and re-submit the request.

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