Teradata SQL Error and Failure Codes from Error 9903 To 9915

SQLServerF1_Header_Small

9903 The privilege is not applicable to a server.
Explanation: The applicable grant privileges are SELECT, INSERT, SHOW for a server object.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9904 Specified operation not allowed for server %DBID.%TVMID.
Explanation: DbName or TableName Name value pairs specified as part of server definition should match with the
database name or table name of the query if this is a select or help foreign database statement.
Help foriegn server is not allowed when DbName or TableName name value pair is specified in server definition.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9905 Privilege cannot be granted as the specified server does not have an associated table operator.
Explanation: The user attempted to Grant Select/Insert privilege on a server object. Error is reported If SELECT privilege
is specified and no import operator is associated with the server object or If INSERT privilege is specified and no
export operator is associated with the server object.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9906 ’%VSTR’ is not a server.
Explanation: The specified item is a view, macro, permanent journal table, join index, or hash index and the context of
the statement returning the error requires the item to be a normal server.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Correct the statement and resubmit the request.

9907 Server object not associated with operator.
Explanation: Server object is not associated with the required operator for the statement.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Alter the server object to associate the required operator.

9908 ’%VSTR’ is not allowed when external security is associated with the server.
Explanation: Server object is associated or specified with external security. So ’proxyusername’ or ’proxypass’ NVP not
allowed in a server custom clause.
Generated By: RES Modules.
For Whom: End User.
Remedy: Remove ’proxyusername’ or ’proxypass’ from create or alter server and resubmit the request

9909 ’%VSTR’ is not allowed in a server custom clause.
Explanation: Custom clause for server object must not have names like Columns, Servermode, QualifyColumns,
IsNested, hExplain, Import and Export.
Generated By: Parser Modules.
For Whom: End User.
Remedy: Remove the name specified in error message from custom clause and resubmit.

9911 Invalid use of query %VSTR.
Explanation: The query system time period specification or query TransactionTime period specification or query Valid-
Time period specification must not be given at statement level.
Generated By: RES modules.
For Whom: The end user.
Remedy: Specify the query system time period specification or query TransactionTime period specification or query
ValidTime period specification at Table Level and resubmit.

9912 NORMALIZE is not allowed on a SYSTEM_TIME column.
Explanation: When a table is DDL normalized, then the <Normalize column> must not be system-time column.
Generated By: RES module.
For Whom: End User.
Remedy: Correct statement and resubmit.

9913 Value for system-time column is replaced by a system-generated timestamp.
Explanation: This is only a warning to let the user know that a value specified for a system-time column was replaced
by a system-generated timestamp.
Generated By: Resolver.
For Whom: End User.

9915 A cursor returning a result set to both caller and client is not allowed on select and consume.
Explanation: Teradata does not allow the cursor returning a result set to both caller and client on Select and Consume
statement from a stored procedure.
Generated By: Opt modules.
For Whom: End User.
Remedy: Do not use cursor on Select and Consume, if cursor returns a result set to both caller and client.

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