Teradata SQL Error and Failure Codes from Error 12911 to 13010

SQLServerF1

12911 Devi detected RCB Bad Op.
Explanation: An unsupported RCB op command was detected by the BNS device interface. This is a PDE kernel bug.
Generated By: BNS Device Interface (devi).
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: This event should never occur. If it does, contact the Global Support Center.

12914 Devi detected MakeService Error.
Explanation: The BNS device interface received an unknown return code from MakeService.
Generated By: BNS Device Interface (devi).
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: This event should never occur. If it does, contact the Global Support Center.

13003 this is a non-TPA node.
Explanation: This node was not found in the desired TPA node list. It is assumed to be a non-TPA node.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event indicates the node is a non-TPA node.
Remedy: No action is needed for non-TPA nodes. If this event occurs on a TPA node, the vconfig info may be invalid.

13004 invalid Node ID.
Explanation: This error might occur during unexpected network errors. The most likely cause would be a reconfiguration
of the network during the Config service.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Contact the Global Support Center if the frequency of the message is abnormally high.

13005 this node is a late joiner.
Explanation: A coordinator node has been selected and it is too late for this node to participate in the configured TPA.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Restart the TPA to add in the node.

13006 split net detected.
Explanation: The Config service will generate this event if it cannot see a majority of TPA nodes. This is intended to prevent
multiple TPAs from accessing the database at the same time.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Too many nodes may be offline or there may be a network problem preventing this node from seeing the minimum
number of nodes needed for a TPA. Use the Bynet utilities to verify the network configuration.

13007 unable to transmit.
Explanation: The Config service was unable to transmit its data because of an unrecoverable error. The most likely cause
would be a destination node being down or a reset in progress.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Contact the Global Support Center.

13008 coordinator has a bad TPA node list.
Explanation: This error indicates the net configuration has changed since the coordinator last examined the network.
One or more nodes in the TPA list are unreachable. This event may occur during TPA resets.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces a TPA restart.
Remedy: Contact the Global Support Center if the frequency of the message is abnormally high.

13009 Config service is busy.
Explanation: A new config cycle has been started before the current one has completed. This event can only happen if
multiple ntosinit processes are running.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Stop all ntosinit processes before restarting the TPA.

13010 this node has been dropped from the TPA.
Explanation: The coordinator has determined that this node cannot participate in the TPA because it cannot reach all
selected TPA nodes.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Use the Bynet utilities to verify the network configuration. Restart the TPA to add the node when the problem has been resolved.

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