Teradata SQL Error and Failure Codes from Error 11506 to 11514

SQLServerF1

11506 Invalid merge source mailbox.
Explanation: The source mailbox does not exist.
Generated By: Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11507 Merge has successfully been restarted.
Explanation: A merge operation has been restarted.
Generated By: Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11508 Merge processing cannot continue.
Explanation: The merge operation was aborted because there is already a merge going on with the same id.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11509 Invalid merge row.
Explanation: An invalid row has been supplied to merge.
Generated By: PDE Network Merge 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.

11510 Can’t change keepresponse flag.
Explanation: A rewind or continue was rejected because it attempted to change the keepresponse flag.
Generated By: PDE Network Merge 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.

11511 Can’t reposition.
Explanation: A reposition was rejected because the keepresponse flag isn’t set.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.

11506 Invalid merge source mailbox.
Explanation: The source mailbox does not exist.
Generated By: Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11507 Merge has successfully been restarted.
Explanation: A merge operation has been restarted.
Generated By: Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11508 Merge processing cannot continue.
Explanation: The merge operation was aborted because there is already a merge going on with the same id.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11509 Invalid merge row.
Explanation: An invalid row has been supplied to merge.
Generated By: PDE Network Merge 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.

11510 Can’t change keepresponse flag.
Explanation: A rewind or continue was rejected because it attempted to change the keepresponse flag.
Generated By: PDE Network Merge 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.

11511 Can’t reposition.
Explanation: A reposition was rejected because the keepresponse flag isn’t set.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Notes: This event normally causes an automatic DBS restart.

11512 Continue expected.
Explanation: The mrgcontinue flag wasn’t set for an in-progress merge.
Generated By: PDE Network Merge 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.

11513 BYNET merge has no rows.
Explanation: BYNET merge should only be invoked if at least one row will be returned. In this case BYNET merge has
been invoked and there are no rows. This abnormal condition may be the result of a DBS bug.
Generated By: PDE Network Merge 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.

11514 Invalid skip count.
Explanation: The supplied skip count is invalid.
Generated By: PDE Network Merge 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 11506 to 11514 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 *