Teradata SQL Error and Failure Codes from Error 3427 To 3491

3427 Internal error: RBM ran out of contexts.
Explanation: The Resolver Base Module is unable to allocate space for a user request.
Generated By: Resolver Base Module
For Whom: Support Representative.
Remedy: Save all information. Contact your Support Representative.

3428 Internal error: RBM failed to resolve quiesced session %VSTR.
Explanation: The Resolver Base Module is unable to resolve the indicated quiesced (locked) session. The failure is indicated
by a failure response from the parser, or from the AMPs for RBM’s commit/abort session request.
Generated By: Resolver Base Module
For Whom: Support Representative.
Remedy: Save all information. Contact your Support Representative.

3429 Dispatcher is unable to rollback or commit, one or more in-doubt transactions.
Explanation: During rollback or commit processing, the Dispatcher raised the exception upon detecting one of the following
conditions: 1) An affected session or transaction is in an inconsistent state. 2) An affected transaction has a pending
request.
Generated By: Resolver Base Module
For Whom: Support Representative.
Remedy: Verify that the affected session exists and is in a quiesced state. Also ensure that the transaction has no pending
request.

3450 Internal error detected by Multi-Threaded Kernel.
Explanation: This error occurs when an abnormal situation caused by some malfunction of the kernel. This error generally
is not caused by the code calling the kernel.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3451 Internal Error: Multi-Threaded Kernel has run out of contexts.
Explanation: This error occurs if the code calling the Multi-Threaded Kernel tries to allocate a new thread context when
no free thread context left in the kernel work area.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3452 Internal Error: Counter was already zero before call to ThdTicSignal.
Explanation: This error occurrs when the code calling the Multi-Threaded Kernel tries to call ThdTicSignal when the tic
counter had reached 0.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3453 Internal Error: Buffer size too small in call to ThdInit or ThdWorkSize.
Explanation: This error occurs when some actual size constant is bigger than its pre-determined limit.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3454 Internal Error: No threads were waiting for count to become zero.
Explanation: This error occurs if a tic reaches 0 while no thread is waiting on it in the Multi-Threaded Kernel.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3455 Internal Error: The kernel received an odd message.
Explanation: This error occurs when the kernel receives a message that is neither an initial message nor a message some
thread is waiting for.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3456 Internal Error: The thread is not found.
Explanation: This error occurs when one tries to release a thread that doesn’t exist.
Generated By: Multi-Threaded Kernel.
For Whom: Support Representative.
Remedy: Contact your Support Representative.

3490 Bad thread event detected by application.
Explanation: The application detected a bad thread event.
Generated By: thdx2, thdx3, thdx3a, thdx3b, thdx4, thdx5, thdx6, thdx7, thdx8
For Whom: Support Representative.
Notes: One of the multi-threaded kernel tests detected an error.
Remedy: Contact your Support Representative.

3491 Bad TicId Count detected by application.
Explanation: The application detected a bad TicId count.
Generated By: thdx6
For Whom: Support Representative.
Notes: One of the EXMTest6 tests detected an error.
Remedy: Contact your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 3427 To 3491 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 *