Teradata SQL Error and Failure Codes from Error 11401 to 11416

SQLServerF1

11401 Cannot allocate a buffer in user virtual memory.
Explanation: An attempt by a TOS service to allocate a temporary buffer to read a GDO failed. This may mean that the
program’s virtual address space has been exhausted, or that there is some sort of corruption in its dynamically allocated
memory heap.
Generated By: TOS compatibility PDE 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.

11403 Cannot start the host interface controller.
Explanation: The toshostenable() service was unable to start the specified host interface controller. This message should
be preceded by one from the host driver giving a more specific reason for the failure. TPA startup will continue, but the
host channel that failed to start will be inoperative.
Generated By: TOS compatibility PDE services.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

11404 Virtual processor ID is incorrect.
Explanation: The virtual processor identifier passed to a TOS service is out of range or specifies a virtual processor that
is not running. This is usually caused by a coding error in the program logging the event.
Generated By: TOS compatibility PDE 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.

11405 New vproc state is incorrect.
Explanation: The new state specified for a virtual processor by tossetvprocstate() is not a defined vproc state. This typically
indicates a coding error the program that logged the event.
Generated By: TOS compatibility PDE 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.

11413 System state type is undefined.
Explanation: An undefined type argument was provided to tosgetsysstate() or tossetsysstate() This typically indicates a
coding error in the program that logged the event.
Generated By: TOS compatibility PDE 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.

11414 System state value is undefined.
Explanation: The new state value provided to tossetsysstate() is not a legal value for the specified state type. This typically
indicates a coding error in the program that logged the event.
Generated By: TOS compatibility PDE 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.

11415 The counter number is out of range.
Explanation: The counter number passed to tosinitcounter() or tosgetcounter() is not between 0 and 15. This typically
indicates a coding error in the program that logged the event.
Generated By: TOS compatibility PDE 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.

11416 Counter value is too large.
Explanation: The counter that has been incremented by tosgetcounter() calls has overflowed the maximum value for a
counter. This indicates an problem with the logic of the program that logged the event.
Generated By: TOS compatibility PDE 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: 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.

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