Teradata SQL Error and Failure Codes from Error 15005 to 15014

SQLServerF1

15005 The TVS Node Agent received error %d when destroying a lock.
Explanation: The TVS Node Agent detected a failure when attempting to destroy a software lock. Because such locks are
a finite resource, this may indicate a resource leak which may cause a resource allocation failure at a later point in time.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: If this error occurs frequently, please contact the Global Support Center.

15006 The TVS Node Agent received error %d when obtaining a lock.
Explanation: The TVS Node Agent attempted to obtain a lock and the request failed. This is not normal, as the request
should have waited for the lock to become available. The Node Agent cannot continue executing without the lock.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15007 The TVS Node Agent received error %d when releasing a lock.
Explanation: The TVS Node Agent attempted to release a lock and the request failed. This is not normal, and may indicate
an unstable system state. Rather than risk a hang later (when the Node Agent attempts to acquire the same lock), the
Node Agent will stop executing now.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15008 The TVS Node Agent got bad message (type=%d, sending_vproc=%d).
Explanation: A TVS Node Agent worker task received a message of an illegal type. The unknown message will be discarded.
This event indicates that the TVS subsystem is malfunctioning, but not in a sufficiently severe manner to warrant a
reset.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15009 The TVS Node Agent was unable to open the TVS device: %s
Explanation: The TVS Node Agent was not able to open the TVS device. This indicates that the TVS device driver is
either not loaded or not accessible via the expected path. TVS cannot continue until this problem is resolved.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15010 The TVS Extent Driver returned an error on a probe request: %s
Explanation: The TVS Node Agent failed to complete a requested extent probe because the PROBE ioctl failed. This
should not happen but will not have an adverse effect unless it occurs frequently.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15011 The TVS Extent Driver returned an error on a migration request: %s
Explanation: The TVS Node Agent failed to complete a requested extent migration because the MIGRATION ioctl
failed. This should not happen but will not have an adverse effect unless it occurs frequently.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15012 An I/O was performed by AMP %d which is not a clique member.
Explanation: The TVS Extent Driver reported statistics on an I/O and the AMP which owns the affected extent is not a
member of this node’s clique. It may be possible for a diagnostic program to cause this behavior, but it is unexpected and
the statistics will not be recorded for this extent.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15013 The TVS Extent Driver returned an error on a break mirror request: %s
Explanation: The TVS Extent Driver rejected a request to break an extent mirror.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.
15014 The system service used for TVS Node Agent timing failed: %s
Explanation: The TVS Node Agent relies on the ability of a thread to sleep for a specified amount of time in order to collect
I/O statistics from the TVS Extent Driver without using an excessive amount of CPU time. The system service used to
implement this ability appears to be malfunctioning. This should never happen.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

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