Teradata SQL Error and Failure Codes from Error 3527 To 3537

3527 Format string ’%VSTR’ has combination of numeric, character and GRAPHIC values.
Explanation: The specified format contains X characters, characters that imply numeric values and/or G characters, for
example, the digit 9, the dollar sign, period, dash, plus sign, comma, character G, or character X.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the format.

3528 FORMAT string ’%VSTR’ contains an unrecognizable character.
Explanation: The specified format contained an invalid character.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the format.

3529 Invalid multiplier in FORMAT string ’%VSTR’.
Explanation: The multiplier (the number in parentheses) is invalid.
Generated By: OPT modules.
For Whom: End User.
Notes: The multiplier must be from 1 to 32000.
Remedy: Correct the format.

3530 Invalid FORMAT string ’%VSTR’.
Explanation: The FORMAT string is invalid.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the format.

3531 A Non-Hashed table cannot be ALTERed.
Explanation: An attempt was made to alter a table that is not hashed.
Generated By: OPT modules.
For Whom: End User.
Remedy: This operation is illegal. The only remedy is to create a hashed version of the table and then make appropriate
modifications against it.

3532 Conversion between BYTE data and other types is illegal.
Explanation: The user tried an operation requiring either conversion from numeric, character, or GRAPHIC data to
BYTE data or BYTE data to character, numeric, or GRAPHIC data. Most operations on BYTE data are illegal. User is probably
trying to access the wrong column.
Generated By: OPT modules.
For Whom: End User.
Remedy: Most operations on BYTE data are illegal. User is probably trying to access the wrong column.

3533 A table cannot have more than 32 secondary indexes.
Explanation: The user tried to create more than 32 secondary indexes for a table.
Generated By: OPT modules.
For Whom: End User.
Remedy: Reduce the number of secondary indexes.

3534 Another index already exists, using the same columns and the same ordering.
Explanation: The user tried to create a secondary index, and an index already existed with the same columns and with
the same ordering.
Generated By: OPT modules.
For Whom: End User.
Notes: The user cannot have both a unique and a non-unique index specifying the same column or group of columns.
Remedy: None, since the index already exists.

3535 A character string failed conversion to a numeric value.
Explanation: A character string constant in a query is in a context requiring that it represent a numeric value, and it does not.
Generated By: OPT modules.
For Whom: End User.
Notes: It is preferable to use a numeric value rather than a character representation of a numeric value. This avoids the need for conversion and is more efficient.
Remedy: Change the constant to either a numeric value or a character string that represents a numeric value.

3536 UPPERCASE or CASESPECIFIC specified for non-CHAR data.
Explanation: The user tried to specify UPPERCASE or CASESPECIFIC for data with a type other than CHAR or VARCHAR.
Generated By: SYN and OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.

3537 A MultiLoad DELETE Statement is Invalid.
Explanation: In a MultiLoad Complex Import Task, the user provided a DELETE statement that does not fully specify a
primary index value or the values of all the partitioning columns. Or, in a MultiLoad Delete Task, the user provided a
DELETE statement that specified a primary index.
Generated By: OPT modules.
For Whom: End User.
Remedy: Correct the error and resubmit the request.
In a MultiLoad Complex Import Task, the WHERE condition, including any taken from a view definition, must allow for
primary index access (and, if partitioned, partition access) with possible ANDed residual conditions. It must also reference no other tables or views.
In a MultiLoad Delete Task, the WHERE condition, including any taken from a view definition, must not include a primary
index access. It must also reference no other tables or views.

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