Teradata SQL Error and Failure Codes from Error 11913 to 11923

SQLServerF1

11913 Resusage discarded some monitoring information because of insufficient resources; %s.
Explanation: ResUsage software was not able to keep up with its workload, as described in the message.
This usually happens because the system is too busy to handle the resusage log rate specified in the control GDO.
Generated By: PDE resource usage monitoring.
For Whom: System Administrator, 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: Consider setting longer resusage collect and log intervals or disabling one or more ResUsage tables. If this is
infeasible or the explanation does not seem to fit your case, contact the Global Support Center.

11914 RSS ecountered an anomaly in counting %s; expected %d but found %d.
Explanation: During tpa initialization, the Resource Sampling System tallies the storage device list, and subsequently
re-traverses the list building an internal table. On this re-traversal, the number of entries of interest had increased; however,
RSS was able to handle the increase without error.
This usually happens because some function like findit is still adding logical devices while tpainit is running.
Generated By: PDE resource usage monitoring.
For Whom: System Administrator, 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: If the above explanation seems to fit the case, no remedy is necessary. If the situation seems truly anomalous,
contact the Global Support Center.

11916 No data available for %s.
Explanation: The buffer ID passed to rssretrieve() identified a table for which no data was available.
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.

11918 Failure in acquisition or manipulation of a needed resource: %s.
Explanation: The RSS or ResUsage subsystem was not able to acquire, modify, or otherwise manipulate some system
resource that it needed, as described in the message.
This is usually caused by some system resource limitation or an internal error.
Generated By: PDE resource usage daemons.
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.

11919 The RSS subsystem has encountered a system call error. %s.
Explanation: An rss internal call to a system function has failed. The associated stack trace will help identify the problem.
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.

11920 Attempt to open, or assertain SCSI address of, a physical disk resulted in the following error: %s.
Explanation: RSS was attempting to generate a list of disks for data collection and was unable to adequately query this
disk. ResUsage data for this disk will not be collected.
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.

11921 Rssd exited due to an exception. Exception Code = 0x%08X Flags = 0x%08X Address = 0x%08X 64 bit addrs ext = 0x%08X
Explanation: General RSS exception handler caught an error in Rssd. The traceback is provided, and Rssd has exited.
Only RSS (ResUsage data collection) should be affected.
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.

11923 RSS: Expected and Actual wakeup time exceeded expected margin limits. Previous Time:
%d Sleep Start Time: %d Current Time: %d Delta: %d Expected Delta: %d LOG rate: %d COLLECT rate: %d TDWM rate: %d GCD rate: %d DYNAMIC rate: %d Expired Period: %s
Explanation: The system clock may have been changed either manually or automatically to keep it accurate. This adjustment
has exceeded the RSS timer adjustment for the current collect period.
Generated By: PDE resource usage monitoring.
For Whom: Operator.
Remedy: No action needed. If frequent, the cause of the system clock changes should be determined.

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