Teradata SQL Error and Failure Codes from Error 13013 to 13021

SQLServerF1

13013 Config initialization did not complete.
Explanation: The system failed to create the necessary synchronization EVENT object to complete initialization.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This error forces the node down.
Remedy: Restart PDE. Contact the Global Support Center if this problem persists.

13014 TPA reset generated by Bynet driver.
Explanation: A reset has occurred due to a change in the TPA configuration. This error is usually caused by a TPA node
dropping offline.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces a TPA restart.
Remedy: Examine all TPA nodes to determine which node caused the reset. Contact the Global Support Center if the
cause of the reset is unknown or unexpected.

13015 System Reset Initiated by the Block queue Daemon.
Explanation: Block queue daemon is used to queue blocked services. It has detected an Operating System error which
makes it unable to proceed.
Generated By: BNS Config subsystem Block queue daemon.
For Whom: System Support Representative.
Notes: This error forces the node to reboot.
Remedy: Contact the Global Support Center.

13016 this node is a standby and has been dropped from the TPA.
Explanation: The coordinator has determined that this node is a standby that can be dropped from the TPA.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: None needed.

13017 node %s is out of the configuration.
Explanation: A node which was defined on the configuration originally is now no longer connected. Either this node is
no longer talking to the BYNET or it’s currently in a panic, or non-recoverable state.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Remedy: Check the status of the node, and bring it back on-line again if necessary. If it was set intentionally then this is
normal; no action is needed.

13018 %s.
Explanation: This event is informational. It is logged during TPA startup to report how many nodes are online and how
many are down. If one or more standby nodes have been configured this event also reports how many standby nodes are
being used, how many are available, and the total number of nodes in the system.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Remedy: No action is needed.

13020 Standby node %s local standby flag not set.
Explanation: This event is informational. It is logged during TPA startup by the coordinator in the event that a node that has been marked as a standby in the coordinator’s vconfig GDO isn’t marked as a standby in the node’s vconfig GDO. The status of the node is ambiguous and consequently the node will be included in the TPA despite the fact that it has been marked as a standby in the coordinator’s vconfig GDO.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Remedy: No action is needed.

13021 this node has been dropped from the TPA because it is illegal.
Explanation: The coordinator has determined that this node cannot participate in the TPA because to do so would be
illegal. Either an attempt has been made to bring more than four nodes into the TPA in an entry level system, or an attempt has been made to bring more than sixteen storage-connected nodes connected to a BYA32 into the TPA. Neither of these configurations is supported.
Generated By: BNS Config subsystem.
For Whom: System Support Representative.
Notes: This event forces the node down.
Remedy: Do not attempt to bring more than four nodes into the TPA in an entry level system. Do not attempt to bring
more than sixteen storage-connected nodes connected to a BYA32 into the TPA.

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