Teradata SQL Error and Failure Codes from Error 9257 To 9267

9257 AT clause may only occur after DATE, TIME, or TIMESTAMP and must not occur before WITH TIME ZONE.
Explanation: An AT clause may only occur after the target data type in a CAST or Teradata conversion (other data attributes may occur between the target data type and the AT clause). In addition, WITH TIME ZONE must not be specified
after an AT clause (it may be specified after the target data type but before the AT clause). The target date type must be DATE, TIME, or TIMESTAMP.
Generated By: SYN modules.
For Whom: End user.
Remedy: Correct the request and resubmit it.

9258 AT clause is incompatible with specified data type.
Explanation: A target data time is specified before the AT clause that is not a DATE, TIME, or TIMESTAMP data type.
Generated By: SYN modules.
For Whom: End user.
Remedy: Correct the request and resubmit it.

9259 Statement Error occurred in the iterated or multistatement request.
Explanation: Since DBQL Log Table only records one response for each request, either success or error, a new error code
has been allocated to notify the user that one or more statements had errored in the iterated request or a multistatement
request.
Generated By: disdbqlupd.c
For Whom: End User.
Remedy: Check the client application for any information about the statements/data records that generated errors.

9260 The specified MERGEBLOCKRATIO value is invalid.
Explanation: Invalid MERGEBLOCKRATIO value. The allowable range is between SYSMINMERGEBLOCKRATIO and
SYSMAXMERGEBLOCKRATIO, inclusive.
Generated By: GNS modules.
For Whom: End user.
Remedy: Correct MERGEBLOCKRATIO value and resubmit the request.

9261 Stored procedure compiled with empty SPL file.
Explanation: The stored procedure text submitted for compilation is empty.
Generated By: Parser/TSP Modules
For Whom: END USER
Remedy: Retry the test case with correct SPL file and contact the support representative, if the problem persists

9262 Cannot END QUERY LOGGING as no rule exists on %VSTR.
Explanation: The END QUERY LOGGING statement cannot be completed because there is no rule in the DBQLRuleTbl
for the user/account/ application. If the END contained a list of users, accounts or applications, this message only indicates that one of the list has no rule. Use SELECT * FROM DBQLRULES to determine if others on the list have a rule in
place.
Generated By: OPD
For Whom: END USER
Remedy: Display current rules to determine which rules exist for the user/account/application.

9263 Cannot Proceed with DBC Restore, Users other than DBC are logged on.
Explanation: During a Full DBC Restore operation, no users other than DBC should be allowed to logon as it would
cause some wierd problems. So report an error if any user other than DBC is logged on before starting the DBC Restore and
abort the restore operation. DBC user has to logoff these users and disable the logons except DBC and should start the
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.

9264 SET QUERY_BAND not permitted.
Explanation: The SET QUERY_BAND statement must be issued in a trusted request.
Generated By: OPD modules.
For Whom: End User.
Remedy: Use the appropriate client interface to set the statement as trusted and resubmit.

9266 Operation is not allowed on an SQL UDF ’%VSTR’.
Explanation: The operation performed on the specified SQL UDF is not supported. Currently, ALTER FUNCTION is not
allowed on an SQL UDF.
Generated By: Parser.
For Whom: End User.
Remedy: Do not submit the request.

9267 A nondeterministic SQL expression passed as an argument to an SQL UDF cannot correspond to a parameter that appears more than once in the return statement.
Explanation: A nondeterministic SQL expression containing a RANDOM function or any form of nondeterministic
functions when passed as an argument to the corresponding parameter which is used more than once in the return statement
is not allowed.
Generated By: Parser.
For Whom: End User.
Remedy: Correct the request based on the above explanation and resubmit it.

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