Teradata SQL Error and Failure Codes from Error 5943 To 5953

5943 External user has the same name as a permanent user.
Explanation: A directory-based logon must not specify a permanent user.
Generated By: SES module.
For Whom: End User.
Remedy: Resolve user name conflict.

5944 Partition Expression can’t be altered due to partition statistics.
Explanation: Partition Expression can’t be altered when the partition stats exists.
Generated By: OPD module.
For Whom: End User.
Remedy: Drop the partition statistics or multi-column stats involving partition column before attempting to alter the
partitioning expression.

5945 Partition Statistics are not allowed on Temporary Tables.
Explanation: Partition Statistics are not allowed on global or volatile temporary tables.
Generated By: OPD module.
For Whom: End User.
Remedy: Change the request to adhere to the partition statistics rules and resubmit the request.

5947 Authorization does not exist. Check output for possible warnings encountered in compiling UDF/XSP.
Explanation: There are two warning messages combined in this warning code.
1) During the creation of a UDF/XSP, a problem was found during compilation. Compilation warnings exist. The
UDF/XSP was created despite the errors.
2) The authorization being referenced in the UDF/XSP has not been created yet.
Generated By: CUFTsk
For Whom: UDF/UDT/XSP developer
Remedy: Check the compile errors returned with this error.

5948 Cannot alter the protection mode of an UDF/XSP that specifies an external security clause.
Explanation: It is not possible to convert an UDF/XSP that specifies an external security clause to run in NOT PROTECTED
mode, such that this statement will result in an error.
Generated By: Resolver
For Whom: UDF/UDT/XSP/AUTH developer
Remedy: Do not submit the statement.

5949 DROP RANGE level %VSTR exceeds the current number of partitioning levels.
Explanation: For an ALTER TABLE statement, the default or specified level of a DROP RANGE[#Ln] must not exceed
the number of partitioning expressions currently defined for the primary index of the table.
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 partitioned
primary index rules and resubmit the re-quest.

5950 ADD RANGE level %VSTR exceeds the current number of partitioning levels.
Explanation: For an ALTER TABLE statement, the default or specified level of a ADD RANGE[#Ln] must not exceed the
number of partitioning expressions currently defined for the primary index of the table.
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 partitioned
primary index rules and resubmit the re-quest.

5951 Specified ADD RANGE level %VSTR is not the same as level %FSTR for the corresponding DROP RANGE.
Explanation: For an ALTER TABLE statement, if ADD RANGE#Ln is specified with a DROP RANGE[#Ln] in an alter
partitioning expression clause, n must specify the same level as the default or specified level of that DROP RANGE[#Ln].
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 partitioned
primary index rules and resubmit the re-quest.

5952 WITH DELETE specified without a DROP RANGE.
Explanation: For an ALTER TABLE statement, if WITH DELETE is specified when altering partitioning expressions, at
least one partitioning expression must be altered with a DROP RANGE[#Ln]. That is, WITH DELETE is not allowed when
only adding ranges.
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 partitioned
primary index rules and resubmit the re-quest.

5953 WITH INSERT specified without a DROP RANGE.
Explanation: For an ALTER TABLE statement, if WITH INSERT is specified when altering partitioning expressions, at
least one partitioning expression must be altered with a DROP RANGE[#Ln]. That is, WITH INSERT is not allowed when
only adding ranges.
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 partitioned
primary index rules and resubmit the re-quest.

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