Teradata SQL Error and Failure Codes from Error 11950 to 11972

SQLServerF1

11950 Invalid table id %d passed to rssgethdr().
Explanation: Internal error possibly caused by incompatible software module versions.
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.

11951 Invalid number of CPUs %d indicated in toshardwarep.
Explanation: Internal error possibly caused by bad performance file configuration. Check the number of CPUs displayed
from the CTL hardware command.
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.

11960 RSS performance counter data collection failure. function return status = 0x%08x counter return status = 0x%08x counter = %s
Explanation: This error is most likely due to a failed system call. This failure will result in bad data for the particular
counter data.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS error messages are normally warnings only. The associated stack trace will help the Global Support Center
determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11968 Invalid pdisk index 0x%08x passed to rssgethdr().
Explanation: Determine if the Pdisk Index 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.

11969 Invalid vdisk index 0x%08x
Explanation: Determine if the Vdisk Index is valid. Look for changed disk configurations. This failure will result in RSS
not reporting 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.

11970 rssd thread did not exit. WaitForSingleObject() returned 0x%08x, WAIT_TIMEOUT == 0x00000102L. RSS may not log some or all data. On Windows please verify the contents of the PDH registry entries “Counters” and “Help” under:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPerflib009
Explanation: The exit of the rssd thread is waited on during a tpareset. If the wait times out then most likely the rssd
thread is hung. A backtrace of all the pdemain threads should indicate the problem area. If the backtrace shows PdhAddCounter
then the registry entries may be empty. This failure will result in RSS not logging some or all 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.
Remedy: Contact the Global Support Center.

11971 Unable to open Extent Driver Device. return value = 0x%08x.
Explanation: Error returned while opening the Extent Driver Device. 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: The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11972 Pdisk count from device map is zero. return status = 0x%08x.
Explanation: The number of Pdisk entries returned in the Pdisk device map is zero. 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.

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