Teradata SQL Error and Failure Codes from Error 11982 to 11991

SQLServerF1

11982 Cliend ID not available
Process id = %d Task id = %d
Explanation: Can not assign a client ID to the RSS environment
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The processes in the node may have opened too many RSS environments
Remedy: Contact the Global Support Center.

11983 Bad RSS handle
Explanation: The handle to the RSS environment is invalid.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the bad handle error.
Remedy: Contact the Global Support Center.

11984 Bad cliend ID Clientid = %d
Explanation: Client ID is either out of range or not in use.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The client may have already closed the RSS environment.
Remedy: Contact the Global Support Center.

11985 Buffer not available
Explanation: Buffer needed for the RSS service is not available.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The RSS buffer is either not available or can not be created.
Remedy: Contact the Global Support Center.

11986 Bad mode parameter
Explanation: The mode parameter is invalid.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The mode parameter has invalid flag combinations.
Remedy: Contact the Global Support Center.

11987 RSS was unable to unmap a memory mapped file. return status = %d file size = %d file name = %s
Explanation: RSS gets an error status unmapping a memory mapped file
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the unmap error.
Remedy: Contact the Global Support Center.

11988 Buffer creation fail
Explanation: The buffers needed for the RSS environment can not be created
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: Other events may have caused the buffer creation error.
Remedy: Contact the Global Support Center.

11989 Bad buffer size parameter
Explanation: The buffer size parameter is invalid.
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The buffer size parameter contains invalid value.
Remedy: Contact the Global Support Center.

11990 RSS deamon is not ready
Explanation: The RSS deomon is not ready to service message requests
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: The caller for RSS services may retry at a later point.
Remedy: Contact the Global Support Center.

11991 Bad process for RSS environment
Explanation: The handle to the RSS environment does not belong to the process
Generated By: PDE resource usage monitoring.
For Whom: System Support Representative.
Notes: RSS service is invoked by a process that does not own the RSS handle.
Remedy: Contact the Global Support Center.

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