Teradata SQL Error and Failure Codes from Error 11569 to 11584

SQLServerF1

11569 %$EventInfo: Sort key length mismatch detected (lens %d %d, mrgid 0x%04x 0x%04x
0x%04x, ses# 0x%04x 0x%04x, txn# 0x%04x 0x%04x 0x%04x).
Explanation: Merge has detected a sort key length mismatch. All sort keys associated with a given merge should have
the same length. A sort key length mismatch implies a DBS failure.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11570 Merge row length exceeds internal limit.
Explanation: The application presents merge with blocks of rows to be merged across the network. If any of these rows
exceed the established maximum length, this diagnostic will be logged.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11571 Merge page allocator exhausted.
Explanation: When the BNS merge subsystem processes a merge request, it allocates the count of pages necessary to
hold the maximum user-specified size of the response buffer. This diagnostic implies that the page allocation logic has
failed.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11574 Merge user buffer too small: less than %d bytes.
Explanation: The user has requested a response buffer which is too small to hold a single response parcel. Merge
responds directly to the application by requesting a specific minimum size for the response buffer.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center if the frequency of the message is abnormally high.

11575 Merge detected illegal row count.
Explanation: Merge keeps a running tally of the number of rows it has extracted from a given data block. If this tally
ever exceeds the advertised count of rows in the block, this error will be logged. This implies an internal merge error.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11576 Merge encountered invalid data block.
Explanation: A data block becomes exhausted when the final row has been extracted from it. At this point merge needs
to pull in the next (possibly null) data block from the same node in the virtual processor heap. If the next data block is
invalid, an internal error has occurred during MrgMove processing.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11579 Merge thread encountered null RCB.
Explanation: Under certain circumstances, merge processing requires an RCB to have been pre-allocated. In this
instance, when merge requires the next data block from the application, it must have a pre-allocated RCB in order to send
the request. This failure implies failure in merge SendRow logic.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11581 Merge could not allocate resources.
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.

11582 Merge encountered a null virtual processor heap node.
Explanation: When the application delivers a data block to merge, the associated relative vprocid must match an existing
node in the participating vproc heap. Failure to find the related node may mean that the heap has been corrupted.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11583 Merge found no participants within merge group.
Explanation: Merge is fielding a data block from the application, but there are no participating virtual processors on the
node.
Generated By: BNS Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11584 Merge received unexpected channel program reply: %x
Explanation: Merge received a reply other than ack/nak from the participants. This is a logic error in MrgSendRow.
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 11569 to 11584 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 *