Teradata SQL Error and Failure Codes from Error 11940 to 11949

SQLServerF1

11940 Rss was unable to complete a system call.
Explanation: This error is most likely due to a failed system call. This error may effect RSS data logging for the time
period.
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.

11942 Rss timer event 0x%08x returned an unexpected error code: %d
Explanation: A call to wait for an event or an elapsed time failed. RSS will continue to run and will retry the call. If it
fails repeatedly RSS may no longer produce ResUsage data.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Please inform the GSC when this message appears and the error code value.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11943 Rss was unable to create its timer event. Return code: %d
Explanation: Rss will not collect or log data.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only. In this case ResUsage will be non-functional. The rest of the system
should continue to operation normally.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11944 Rss event %d is being throttled. %d events have been logged
Explanation: This message is caused by the logging multiple rss errors of the same type within a one hour period.
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.

11945 RssMalloc was unable to allocate %d bytes of memory.
Explanation: This message is caused by a possible OS resource error. Rss will stop logging data. A tpareset might eliminate
this condition.
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.

11947 Rss was unable to access pdh information. return value = 0x%08x.
Explanation: This error is most likely due to a failed system call. This failure will result in RSS not logging the particular
counter data.
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.

11948 Invalid ldv id 0x%08x passed to rssgethdr().
Explanation: Determine if the LdvId is valid. Look for changed disk configurations. This failure will result in RSS not
logging data for this device. A tpareset will re-enable this device if it does not again produce an error.
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.

11949 Invalid host id %d passed to rssgethdr().
Explanation: Determine if the HstId is valid. Look for changed network configurations. This failure will result in RSS
not logging data for this device. A tpareset will re-enable this device if it does not again produce an error.
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 11940 to 11949 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 *