Teradata SQL Error and Failure Codes from Error 11471 to 11505

SQLServerF1

11471 Unable to map the system resident GDO in the kernel.
Explanation: The function used to map a GDO in the kernel is failed
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11472 Unable to read the resident GDO into the user buffer.
Explanation: The function used to read the GDO in the kernel failed. This problem is a result of the user specifying a bad
pointer.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11473 Unable to write the resident GDO into the user buffer.
Explanation: The function used to write the GDO in the kernel failed. This problem is a result of the user specifying a
bad pointer.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

11500 The Merge-request has been aborted.
Explanation: The merge request has been aborted because we failed to create a merge daemon. This can happen if too
many processes are already running.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center if a DBS restart does not correct the problem.

11501 Invalid Merge application block.
Explanation: The format of the application block is invalid or the associated segment does not exist.
Generated By: Merge subsystem.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

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

11503 Invalid Merge-file identifier.
Explanation: The supplied identifier is unknown. The merge associated with it may have been aborted.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11504 Invalid Merge-group identifier.
Explanation: The merge group does not exist. The “merge continue” operation has been aborted.
Generated By: PDE Network Merge services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

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

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