Teradata SQL Error and Failure Codes from Error 11598 to 11803

SQLServerF1

11598 Merge initiation encountered bad state: %x
Explanation: When the BNS merge subsystem is requested to initiate or continue a merge, the MrgInix thread inspects
the state of the existing associated context. If that state is undefined then this error is logged and the merge is aborted.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11599 Merge expected non-zero virtual processor nodes.
Explanation: The MrgMove thread is called to process an incoming data block from the application. This implies there
will be greater than zero virtual processors on this participant node. If we encounter zero, there has been a logic error in
MrgMove processing.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11600 Destination address is incorrect.
Explanation: The address class of the destination is unknown or is outside the valid range for the netq operation.
Generated By: PDE network services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11800 No more global semaphores are available.
Explanation: All available global semaphores have been allocated. This typically indicates that DBS software is getting
global semaphores and never releasing them.
Generated By: PDE network semaphore services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: If the automatic DBS restart does not clear up the problem, an operating system shutdown and reboot should
do so. However, this is possibly caused by a bug in DBS or PDE software, which should be reported to the Global Support
Center.

11801 Semaphore does not exist.
Explanation: An attempt was made to use a global semaphore that has not been allocated, or that has already been freed.
This typically indicates a problem in DBS software, possibly a timing problem where a task that got the semaphore frees it
before an associated task is done using it.
Generated By: PDE network semaphore services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11802 Cannot decrement a semaphore below zero.
Explanation: A gsmdecr() service was issued for global semaphore whose value is zero. This typically indicates a problem
with the DBS or other software that is issuing the service call.
Generated By: PDE network semaphore services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
The associated stack trace will help the Global Support Center determine the exact cause of the failure.
Remedy: Contact the Global Support Center.

11803 Semaphore value is too large.
Explanation: A gsmincr() or gsmwrite() service would set a global semaphore value to exceed the maximum value
allowed. This typically indicates a problem with the DBS or other software that is issuing the service call.
Generated By: PDE network semaphore services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
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 11598 to 11803 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 *