Teradata SQL Error and Failure Codes from Error 5517 To 5531

SQLServerF1_Header_Small

5517 The 2 arguments of binary aggregate function have incompatible data types.
Explanation: The data types of two-argument complex aggregate functions COVAR, CORREL, LINREGSLOPE, LINREGINTERCEPT
must have compatible data types (i.e. all numerics are compatible but other types must be identical).
Generated By: OptWExp
For Whom: End User.
Remedy: Use correct type of arguments.

5518 The RANDOM function has invalid arguments.
Explanation: Random(X,Y) function arguments must be two integers where Y >= X to define a non-empty range.
Generated By: OptWExp
For Whom: End User.
Remedy: Correct arguments to the function.

5521 The RANDOM function can not be used in Aggregates or Ordered Analytical Functions.
Explanation: SUM(Random(X,Y)) and CSUM(Random(X,Y),date) like usage is not allowed for semantic simplicity.
Generated By: ParFdRan
For Whom: End User.
Remedy: Do it as a two step process: aggregate or Ordered Analytical Function on a derived table with Random values

5522 The RANDOM function can not be used in more than one SELECT query clauses.
Explanation: If Random function is called from more than one clause in the same SELECT/UPDATE query, this error is
generated. Such usage is not allowed for semantic simplicity.
Generated By: ParFdRan
For Whom: End User.
Remedy: Call the functions in multiple steps using derived tables or views.

5523 Invalid MULTITSR parcel received.
Explanation: The MULTITSR parcel received from CLI is invalid. The reason could be that the sequence number is not
correct.
Generated By: Parser.
For Whom: System Support Representative.
Remedy: Save all the information. Contact your support representative.

5525 LOCKING modifier canot be specified with CALL SQL statement.
Explanation: Locking Modifier is not allowed with a CALL SQL statement.
Generated By: RES Modules.
For Whom: End User.
Remedy: Correct the CALL SQL statement and resubmit the request.

5526 %VSTR
Explanation: The SPL text of the stored procedure contains compilation errors (and possibly warnings also).
Generated By: Parser (SPL Compiler).
For Whom: End User
Remedy: Correct the SPL text and resubmit the request.

5527 %VSTR
Explanation: Only a warning. There are warnings generated while compiling the stored procedure code. The stored procedure
is successfully created despite warnings.
Generated By: Parser (SPL Compiler).
For Whom: End User
Remedy: Attempt to eliminate the warnings by modifying the SPL text and resubmit the request.

5528 DMLs capturing changed data, DDLs and Comment statements cannot be mixed in a replicated transaction.
Explanation: Normally a DDL is allowed to be the last request in a transaction. Since a replicated transaction uses 2PC
protocol, a DDL can not be allowed in such a transaction.
For example, BT; <dml> against a replicated table; <ddl> …. NOT ALLOWED! ET;
In addition, a COMMENT placing statement follows the same rule as for a DDL statment if the statement text is being captured
for replication because either the object is member of a replcation group or by way of a replication rule.
Generated By: RES/OPU modules.
For Whom: End User.
Remedy: None.

5530 Invalid operating environment for procedure execution.
Explanation: The Teradata RDBMS server operating environment in which the CALL SQL is submitted is different than
the one in which the stored procedure was created. A stored procedure created in say, NT server environment cannot be
executed on UNIX server. This situation can occur if a stored procedure is restored to a different server operating environment
than the archive was created on. From version TD13.1 onwards, a stored procedure created on one ’row format’environment
cannot be executed on another ’row format’ environment.
Generated By: RES modules.
For Whom: End User
Remedy: Recreate the procedure on the new server operating environment and resubmit the request.

5531 Named-list is not supported for arguments of a procedure.
Explanation: Named-list is not supported for parameters of a stored procedure. Only Postional-List is supported.
Generated By: RES modules.
For Whom: End User
Remedy: Correct the SQL and resubmit the request.

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