Teradata SQL Error and Failure Codes from Error 11901 to 11911

SQLServerF1

11901 Buffer ID is not valid.
Explanation: The logical table Id passed to rssretrieve() was not valid. Legal values are RSS_SVPR, RSS_SCPU, etc. This
is usually caused by a coding error in the program logging the event.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11902 Buffer type is not valid.
Explanation: The buffer type passed to rssretrieve() was not recognized. Legal values are RSS_COLLBUF and
RSS_LOGBUF. This is usually caused by a coding error in the program logging the event.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11903 Buffer Id is not valid.
Explanation: The entity Id (e.g., CPU number, Vproc number) passed to rssretrieve() was not valid. In other words, no
entity with an equal or higher Id was known to RSS. This could be a legitimate condition, or it could be caused by a coding
error in the program logging the event.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
Remedy: Contact the Global Support Center.

11904 Too many NULL return parameters.
Explanation: There were too many NULL return parameters specified in an RSS function call. RSS permits NULL return
parameters for the case where the calling program is not interested in the returned value. However, in this case, the combination
of multiple NULL parameters resulted in a call which was effectively a no-op. This is usually caused by a coding
error in the program logging the event.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11905 Rate class is not valid.
Explanation: The rate class passed to rsssetrate() or rssgetrate() was not recognized. Legal values are RSS_COLLECT or
RSS_LOG. This is usually caused by a coding error in the program logging the event.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11906 The RSS rate %d is invalid.
Explanation: The rate passed to rsssetrate() was not legal. The rate must be a divisor of 3600 seconds, such as 60 seconds.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11910 Resource monitoring is unavailable.
Explanation: A ResUsage service was requested before the resource monitoring facility had been completely initialized.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11911 RSS was unable to access or update the Control GDO.
Explanation: An error occurred in attempting to read or write the Control GDO fields that pertain to ResUsage.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only, but the calling routine may be coded to terminate after the error
message is displayed.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

Above are list of Teradata Errors or Failure Codes from Error 11901 to 11911 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 *