Teradata SQL Error and Failure Codes from Error 15036 to 15045

SQLServerF1

15036 pre-TVS device conversion is %d percent complete in clique %d.
Explanation: The devices in the system are being converted to TVS format. This message indicates how much of the conversion work has been completed up to this point in time. This message will be sent from each clique periodically during the device conversion phase.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: N/A

15037 A file error occurred in a netpde library call: %s
Explanation: A file operation performed through a call to one of the netpde calls has failed. This indicates a problem of some sort, but not severe enough to warrant a restart. It may result in reduced functionality for logging and tracing but will otherwise have no effect on the system.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: May be evident from the message

15038 A fatal file error occurred in a netpde library call: %s
Explanation: A file operation performed through a call to one of the netpde calls has failed. Due to the possible cascading failures that could result from this, it is considered a fatal problem.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: May be evident from the message

15039 Missing or incomplete tvsa_vdisk_mapping file.
Explanation: The file that indicates the pdisk ordering within each vdisk of a pre-TVS system is either missing, incomplete, or corrupt. This file, “tvsa_vdisk_mapping”, is required in order to convert the disks to TVS format. PUT in conjunction with upgrade scripts will normally create the tvsa_preferred_mapping and tvsa_vdisk_mapping files during an
upgrade from a pre-TVS version of Teradata to a TVS version.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15040 The tvsa_vdisk_mapping file has a duplicate reference to device %d
Explanation: The file that indicates the pdisk ordering within each vdisk of a pre-TVS system indicates more than one
amp assigned to the same device. Because of this error, the file will be ignored. If any devices require conversion from pre- TVS format to TVS format, the conversion will not be attempted due to this error. Otherwise the error is benign.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15041 The tvsa_vdisk_mapping file has no reference to device %d
Explanation: The file that indicates the pdisk ordering within each vdisk of a pre-TVS system indicates no amps
assigned to the given device. Because of this error, the file will be ignored. If any devices require conversion from pre-TVS format to TVS format, the conversion will not be attempted due to this error. Otherwise the error is benign.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15042 Unable to initiate TVS I/O tracing: error %d
Explanation: An unexpected error occurred when attempting to initiate TVS I/O tracing. Tracing parameters may be
illegal or tracing may already be activated.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15043 Unable to open device %s %s: error %d
Explanation: An error occurred when attempting to open one of the configured devices. This device will be marked
inaccessible, and depending upon the configuration this may result in one or more AMPs being marked fatal.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15044 An error occurred when attempting to read the TVS device tag: %s %s
Explanation: An device problem prevented the TVS Device Tag for the given device from being read. This device will be
marked inaccessible, and depending upon the configuration this may result in one or more AMPs being marked fatal.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: After repairing the failing device, the STATFLAGS_BADDEVICE flag can be cleared from the tag by running
tvsaFixTag with the -b option.

15045 Pre-TVS disk conversion cannot proceed because device %d is inaccessible
Explanation: Each of the pdisks associated with a particular AMP must be available for conversion from pre-TVS to TVS
format or the conversion for that AMP cannot be started.
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 15036 to 15045 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 *