Teradata SQL Error and Failure Codes from Error 11804 to 11859

SQLServerF1

11804 Semaphore id or idnex is not valid.
Explanation: An attempt was made to use a global semaphore identifier or semaphore index which is not valid for the
requested service. This typically indicates a problem with the program which issued the 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.

11805 PMA down.
Explanation: An attempt was made to allocate a global semaphore on a PMA that is down. This typically indicates a
problem with the program which issued the 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.

11806 Bad gsmatomic() opcode.
Explanation: A bad opcode was passed to gsmatomic(). 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.

11807 Mismatched gsmatomic() gsmid.
Explanation: A mismatched gsmid was passed to gsmatomic(). All gsmatomic() semaphores must reside on the same
node. 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.

11853 Subop %d: RCB state Error:state:%d
Explanation: All GSM BNS services are declared wait-for-response by the caller. The caller is supposed to format the
RCB with the state flag set to REQUEST. If the state flag is not set to REQUEST, this event occurs.
Generated By: BNS GSM subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file and DBS event log. It does not appear on the console.
Remedy: This event should never occur. If it does, the PDE kernel is corrupted. Contact the Global Support Center if
rebuilding the kernel does not fix it.

11855 Subop %d reply = %d
Explanation: An unexpected or unknown reply was received by COR() of the semaphore service.
Generated By: BNS GSM subsystem.
For Whom: System Support Representative.
Remedy: This event should never occur. If it does, it is most likely caused by a hardware glitch that corrupted the reply.
Contact the Global Support Center if a DBS restart does not correct the problem.

11859 Invalid gsmid Subop %d gsmid %x
Explanation: BNS detected an invalid gsmid that no gsm owner node information is available in the gsmid. This event is
likely caused by application program that attempts to pass the NULL or un-initialized gsmid as a parameter to PDE gsm
syscall.
Generated By: BNS GSM subsystem.
For Whom: System Support Representative.
Notes: This message is only written to the log file. It does not appear on the console.
Remedy: This event is strictly an informational event. If this logevent causes the DBS restart, then contact the Global
Support Center to investigate and correct the problem.

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