Teradata SQL Error and Failure Codes from Error 11973 to 11981

SQLServerF1

11973 Device Map call returns an error status. return status = 0x%08x.
Explanation: The call to get the Pdisk Device Map returns an error status. This failure may result in some pdisk attributes
having zero values in the ResUsageSpdsk table.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Pdisk ResUsage data may be invalid.
Remedy: Contact the Global Support Center.

11974 Pdisk count from device map is incorrect. count from device map = %d count from vconfig gdo = %d
Explanation: The number of Pdisk entries returned in the Pdisk device map is not matching the number of Pdisk entries
in the vconfig gdo. This failure may result in some pdisk attributes having zero values in the ResUsageSpdsk table.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Pdisk ResUsage data may be invalid.
Remedy: Contact the Global Support Center.

11976 rssd thread exit wait failed. WaitForSingleObject() returned 0x%08x, error code %d RSS may not log some or all data.
Explanation: The exit of the rssd thread is waited on during a tpareset. The wait has returned a failure status.
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.

11977 Data overflow or negative in a resusage counter. Counter = 0x%08x index = %d value = %d interval = %d ticks Pdh data = %.2f elapse time = %d new data = %08x %08x old data = %08x %08x
Explanation: The counter value is either negative or overflowing the max value.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11978 Two disk devices have the same device ID. Device ID = 0x%08x Device index %d: Major=%d, Minor=%d Device index %d: Major=%d, Minor=%d
Explanation: The disk device ID is formed from the device major and minor numbers. Dupliation of device ID is
detected while scanning the device list.
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.

11979 error encountered in deleting a file status = %d errcode = %d file = %s
Explanation: Error returned while deleting the RSS file.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: This RSS error message is informational only. Other events may have caused the file delete error.
Remedy: Contact the Global Support Center.

11980 CPU statistics error cpu number = %d cpu time = %d, expected time = %d, gather interval = %d percent err = %.2f%
Explanation: CPU usage time are expected to be within certain percentage with respect to the gather interval time. But
the gathered CPU time is outside this boundary.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the CPU statistic error.
Remedy: Contact the Global Support Center.

11981 Bad TOD value Current TOD sec = %d Current TOD usec = %d Previous TOD sec = %d Previous TOD usec = %d Elapse time = %d
Explanation: An unexpected Time Of Day value is detected.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the Bad TOD error.
Remedy: Contact the Global Support Center.

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