Teradata SQL Error and Failure Codes from Error 10502to 10506

SQLServerF1

10502 Location argument is an invalid pointer.
Explanation: An attempt to access a data buffer within a tasks’ space has failed. This can happen if the buffer is released
prematurely, or the task does not own the buffer being accessed.
Generated By: PDE message subsystem.
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.

10503 Mailbox is still linked to a channel.
Explanation: A mailbox cannot be released while it is still linked to a channel. This typically indicates an error in the program
logging the event.
Generated By: PDE message subsystem.
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.

10504 No mailboxes are available.
Explanation: An attempt to get a transient mailbox from the system has failed. This is possibly due to extremely heavy
message traffic, or message deliveries are not being completed.
Generated By: PDE message subsystem.
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: If the automatic DBS restart does not clear up the problem, an operating system shutdown and reboot should
do so. However, this is possibly caused by a bug in DBS or PDE software, which should be reported to the Global Support
Center.

10505 Mailbox is not in use.
Explanation: A message service was passed a mailbox identifier for a mailbox that is not currently allocated. Either an
incorrect argument was passed, or the mailbox has been deallocated by another task.
This event is also returned to the msgchnunlnk() service when the channel specified is not linked to any mailbox.
This is usually caused by an error in the logic of the program logging the event.
Generated By: PDE message subsystem.
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.

10506 Mailbox number is out of range.
Explanation: A source or destination mailbox number is outside the valid range for numbered mailboxes. A corrupted
message header can cause this error.
Generated By: PDE message subsystem.
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 10502to 10506 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 *