Teradata SQL Error and Failure Codes from Error 11569 to 11584

SQLServerF1

11585 Merge channel program transmitter failure.
Explanation: A hardware transmitter failure has occurred during a merge circuit. The merge thread will be aborted. This
typically occurs during a DBS restart.
Generated By: BNS Merge 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: Contact the Global Support Center.

11586 Merge expected an allocated virtual processor heap.
Explanation: During the MrgMove thread, a virtual processor heap must be allocated and initialized to receive incoming
data blocks from all participating virtual processors. This diagnostic implies a logic failure within MrgMove processing.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11587 Merge unexpected virtual processor heap.
Explanation: When the BNS merge subsystem decoded an RCB to create the merge service, it encountered an unexpected
subop.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11589 Merge unexpected RCB allocated.
Explanation: Before allocating an RCB to fetch the next data block, we check for an already existing one. The presence of
an RCB at this point implies a logic error in MrgMove processing.
Generated By: BNS Merge 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: Contact the Global Support Center.

11590 GDO File name not specified or exceed 64 characters
Explanation: The filename for the Gdo specified in either the pdestartup or tpastartup file is not correct. This typically
indicates a specification error by the user in specifying the name of the Gdo.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.
Remedy: Change the filename to be less than 64 characters.

11591 Merge expected service not available.
Explanation: Before dispatching a SendRow service, MrgMove logic first determines whether that service has been allocated.
When logged, this event implies a failure of MrgMove logic to have pre-allocated the SendRow service.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11593 Merge sorted row buffer has overflowed.
Explanation: The BNS merge subsystem collects rows on the coordinator node. If the size of the buffer exceeds the userspecified
maximum, this event is logged. It implies an error in the SendRow logic.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11594 Merge encountered row fragment with illegal length.
Explanation: An error has been detected while preparing to DMA a row from the participant node to the coordinator. A
row fragment is that part of a row which resides on a single memory page. The logic which tabulates the fragments which
constitute a given row has failed.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

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