Teradata SQL Error and Failure Codes from Error 5785 To 5794

5785 Invalid value for Identity Column parameter %VSTR.
Explanation: User specified an invalid value for one of the following identity column parameters: a) If INCREMENT is
positive START WITH value is >= MAXVALUE, b) If INCREMENT is negative START WITH value is <= MINVALUE, c)
MINVALUE value >= MAXVALUE value d) The absolute value of INCREMENT value > IdColBatchSize value in the DBS
Control Record e) INCREMENT BY 0 f) START WITH, MINVALUE, MAXVALUE is not within minimum and maximum
values of the data type of the identity column.
Generated By: RES module.
For Whom: End User.
Remedy: Modify the DDL statement accordingly and re-submit the request.

5786 Error analyzing the query %VSTR in the query capture database, %DBID.
Explanation: An unexpected internal error occured during an Index Wizard Analysis.VSTR is reported in the form ’m:n’
where ’m’ is the identifier of the query that was being analyzed and ’n’ is the specific error code reported by the Optimizer.
* <- DR113879-sb230098-01 *
Generated By: OPT routines.
For Whom: End-User * DR113879-sb230098-01-> *
Remedy: Report this error to your Teradata support representative. As a workaround, try removing the failing query
from the workload and then resubmit the Analysis. * <- DR113879-sb230098-01 *

5787 READ OVERRIDE can only be specified for single table operation.
Explanation: This error message is reported when the user attempts to specify the READ OVERRIDE locking modifier
for an SQL statement that is not for a single table operation.
Generated By: RES modules.
For Whom: End User.
Remedy: Correct the SQL statement so that it contains only a single table operation.

5788 %VSTR currently does not support Identity Columns.
Explanation: The user tried to: – Fastload or Multiload into a table with an identity column. – Create As with an identity column.
Generated By: RES module.
For Whom: End User.
Remedy: Change the target table into a table without an identity column and re-submit the request.

5789 Value for Identity Column is replaced by a system-generated number.
Explanation: This is only a warning to let the user know that a value specified for a GENERATED ALWAYS identity column
was replaced by a system-generated number.
Generated By: Resolver.
For Whom: End User.
Remedy: The message is for information only.

5790 UPSERT on a table with an Identity Column primary index is illegal.
Explanation: If the UPSERT table has an identity column as its primary index, then the UPSERT would be disallowed as
it may no longer be a single-AMP operation.
Generated By: OPT module.
For Whom: End User.
Remedy: Do not re-submit the request on the same table.

5792 Invalid operation on table ’%VSTR’.
Explanation: This error message is reported when the user attempts to perform an update operation on a table which
has been invalidated. This error can also be reported if a single table retrieve is being executed without specifying the READ OVERRIDE locking modifier.
Generated By: RES modules.
For Whom: End User.
Remedy: Validate the table on which update operation has to be performed by executing a DELETE ALL operation on it
or by dropping and creating it again. In case a single table retrieve operation is being performed, then specify the READ OVERRIDE locking modifier. The table can also be used after restoring it from backup.

5793 Limit on the number of host variables in USING modifier exceeded of %VSTR
Explanation: User has defined too many host variable in the USING clause. The number of parameters in a USING
clause is limited to 2541.
Generated By: GNCSETUP.
For Whom: End User.
Remedy: Modify the parameter list in the USING clause to specify not more than 2541 parameters and resubmit the
request.

5794 UDF used in a context not currently supported.
Explanation: A UDF cannot be executed on a PE. There are certain cases where this might happend:
1. used to calculate a unique index hash
2. As an argument to a stored procedure call
Generated By: GNC modules.
For Whom: End User.
Remedy: Correct the SQL statement. Don’t use a UDF in a where clause of the type:
WHERE UDF(x) = A;
Where A is the prime key/index or a unique index column.
INSERT INTO T1 (UDF(5), 1);
Where UDF(5) represents the calculated value for the PI column.
Don’t use a UDF as an argument to a stored procedure call:
CALL UDFPROC(UDF(1), NUM);

INSERT INTO T1 (UDF(5), 1);
Where UDF(5) represents the calculated value for the PI column.
Don’t use a UDF as an argument to a stored procedure call:
CALL UDFPROC(UDF(1), NUM);

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