Teradata SQL Error and Failure Codes from Error 13407 to 13434

SQLServerF1

13407 Channel system reset from CUA = %X in slot %d
Explanation: OPLOUT Dropped on the channel.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: The client TDP has issued a restart to the Channel resulting in a flush of the input and output queues of the
Channel Adapter and Teradata Channel Driver. If the Channel reset was unexpected then contact the Global Support Center,
otherwise ignore this message.

13414 Slot = %d Undefined event %X from Channel Adapter
Explanation: The adapter delivered an undefined letter.
Generated By: PDE tchn channel driver.
For Whom: System Support Representative.
Remedy: Contact the Global Support Center.

13418 TCHN: Write aborted by the Channel: CUA=%X SLOT=%d Reason: %s
Explanation: Write abort received – probable TDP termination.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: If the frequency of the message is abnormally high, contact the Global Support Center. Otherwise, ignore this
message.

13419 TCHN:Read aborted by the Channel: CUA=%X SLOT=%d Reason: %s
Explanation: Read abort received – probable TDP termination.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: If the frequency of the message is abnormally high, contact the Global Support Center. Otherwise, ignore this
message.

13420 SetWaitableTimer() failed to schedule function:%X function arg=%X time_delay=%d
Explanation: NT system call failed.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: Determine why the Win32 call SetWaitableTimer() could not schedule the function. Contact the Global Support
Center.

13426 Protocol error:%X between msg subsystem and channel driver.
mtype:%d &nsmiscargs=%X mp=%X
Explanation: An error was returned by PDE.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: If the frequency of the message is abnormally high, contact the Global Support Center. Otherwise, ignore this
message.

13429 Host Channel Driver: line[%d] of %s Could not obtain %d bytes of user space memory.
Explanation: Process initialization failure – not enough memory.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This error prevents the Teradata Channel Protocol process from initializing. The channel interface will not go
active on the node where this message was issued. Contact the Global Support Center.

13430 Host Channel Driver: line[%d] of %s CreateEvent() returned error: %d.
Explanation: NT system call failed.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This error prevents the Teradata Channel Protocol process from initializing. The channel interface will not go
active on the node where this message was issued. Contact the Global Support Center.

13431 Teradata Channel Driver: fault %d, subtype %d on %s
Explanation: A hardware fault occurred on the adapter.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: The adapter reported this error. The driver may have been able to recover from it, but the adapter is now offline
and all its connections have been closed. Please check the driver’s log file for more detailed messages about the error and
the driver’s attempts to recover from it.

13434 Teradata Channel Driver: No response from adapter in slot = %d bus = %X. Channel interface traces have been captured automatically.
Explanation: The channel adapter is not responding.
Generated By: PDE channel interface driver.
For Whom: System Support Representative.
Remedy: This is the watchdog timeout error condition where the board has failed to communicate with the Driver after
the Driver specifically requested a response. It may be possible to clear the problem by doing a POST test on all the affected
boards, followed by a tpareset of the DBS system if it is up. Provide a copy of the tciproto logs and the automatically captured
trace files to the Global Support Center for analysis.

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