Teradata SQL Error and Failure Codes from Error 9500 To 9542

SQLServerF1_Header_Small

9500 A CDT Index error occured. %VSTR
Explanation: This error is reported if an error occured with a CDT index. See the individual error message for details.
Generated By: PAR module.
For Whom: End User.
Remedy: See individual text.

9514 Cannot Proceed with DBC Restore, DBC Logons are not enabled.
Explanation: During a Full DBC Restore operation, DBC Logons should be enabled as enabling all logons causes restart
when other users try to logon. So report an error if DBC Logons are not enabled before starting the DBC Restore and abort
the restore operation. DBC user has to enable the DBC logons and logoff the users other than DBC and should start the
DBC Restore again.
Generated By: OPT modules.
For Whom: End User.
Remedy: DBC user has to Disable the logons except DBC and logoff all the users other then DBC and start the Restore
process again. Also, DBC Logons should be kept enabled until DBC Restore is complted.

9531 Override Select Constraint privileges are required for this operation.
Explanation: Override Select Constraint privileges on both the target and save tables are required for altering the partitioned
primary index of a protected table.
Generated By: RES module.
For Whom: User.
Remedy: Obtain the required privileges before re-submitting the

9532 Target and save tables do not have identical security constraints.
Explanation: The table being altered is a protected table And the save table is not created with the same constraints
defined in the target table.
Generated By: RES module.
For Whom: End User.
Remedy: Re-create the save table with the constraints

9533 The revoke statement is illegal.
Explanation: The user is trying to revoke either a) an Override Constraint privilege on a table that is not protected, or b)
a RLS privilege from PUBLIC. RLS privileges cannot be granted to PUBLIC.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9534 The NO RLS option is applicable to creating an error table for a protected table only.
Explanation: When the NO RLS clause is specified, an unprotected error table will be created for a protected data table.
It is illegal to specify the clause if the data table is not protected.
Generated By: RES module.
For Whom: End User.
Remedy: Do not re-submit the request.

9536 RANGE_N defines more than %VSTR result values.
Explanation: A RANGE_N function with INTEGER data type must not define more than 2147483647 result values
(including all the ranges, and the NO RANGE, UNKNOWN, and NO RANGE OR UNKNOWN options if specified). In
this case, the value for VSTR is “2147483647”.
A RANGE_N function with BIGINT data type must not define more than 9223372036854775807 result values (including all
the ranges, and the NO RANGE, UNKNOWN, and NO RANGE OR UNKNOWN options if specified). In this case, the
value for VSTR is “9223372036854775807”.
Generated By: OPT modules.
For Whom: End User.
Remedy: Examine the RANGE_N function invocation and verify that it is correct. Modify the arguments to the
RANGE_N such that maximum result value does not exceed the limit.

9540 The ExportDefinitionName ’%VSTR’ does not exist.
Explanation: The user referred to an ExportDefinitionName as %VSTR that does not exist in DBC.ExportWidth table.
Generated By: OPD modules.
For Whom: User.
Remedy: Correct the Teradata SQL statemenet by using a valid ExportDefinitionName and resubmit the request.

9541 Diagnostic REWRITEQRY that returns rewritten text is applied on this query.
Explanation: This is a warning message and not an error. This warning code means that the the query is rewritten and
the rewritten text is sent back.
Generated By: PAR modules.
For Whom: End user.
Remedy: Not an error. This message is for information only.

9542 A security constraint with the name “%VSTR” already exists.
Explanation: This error is displayed when the user tried to create an UDT which has the same name as an existing security
constraint.
Generated By: Resolver
For Whom: End User
Remedy: Examine the Teradata SQL statement and verify that the request is correct. Change the statement to specify a
different name and resubmit the request.

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