Teradata SQL Error and Failure Codes from Error 15047 to 15057

SQLServerF1

15047 Pre-TVS disk conversion cannot proceed because device %d is in a different subpool than other pdisks of the vdisk
Explanation: Conversion of pre-TVS devices requires that each pdisk of a vdisk belong to the same storage subpool. The
given device is in a different subpool than other devices of its original vdisk, so disk conversion cannot proceed.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15048 Unable to allocate or initialize thread local storage %s
Explanation: The TVS Node Agent was unable to properly initialize its thread local storage. This probably indicates a
bug in the TVS Node Agent.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15049 Unable to read from device %s %s: error %d
Explanation: An error occurred when attempting to read from 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.

15050 Device format conversion failed due to %s: %s
Explanation: TVS was unable to perform device format conversion due to the indicated error.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15051 Device format conversion failed (pdisk %d) due to %s: %s
Explanation: TVS was unable to perform device format conversion due to the indicated error.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15052 Device format conversion failed (pdisk %d cyl %d) due to %s: %s
Explanation: TVS was unable to perform device format conversion due to the indicated error.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15053 Device prep for TVS not complete for AMP %d unexpected SEG0 version %d
Explanation: This indicates that the TVS preparation step was not properly completed for the amp shown. This should
have been done prior to switching to this version of the DBS.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Back down to the previous release of Teradata. With the database down, start the Filer and run the “upgradetvsa”
command. After it completes successfully, switch back to this version of Teradata and try to bring up the TPA. If this
error still occurs after performing these steps, contact the Global Support Center.

15054 System is stopping due to previous TVS Device conversion failure
Explanation: This indicates that the TVS device conversion process from pre-TVS to TVS versions of the Teradata Database
has failed. The specific failure should have already been logged.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Refer to the earlier, specific error to determine how to proceed.

15055 The vdisk mapping file maps device %d to invalid AMP %d
Explanation: The file that indicates the pdisk ordering within each vdisk of a pre-TVS system contains a record of an
AMP which does not exist in the current vconfig GDO. 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.

15056 The mapping of device %d to AMP %d causes subpool mismatch
Explanation: The file that indicates the pdisk ordering within each vdisk of a pre-TVS system contains a mapping from
a storage device to an AMP which are assigned to different subpools in the vconfig GDO. Because of this error, the file will
be ignored. Normally the file is not required for proper operation of TVS, but if it is, a subsequent error will be reported.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15057 AMP Vproc %d has been marked FATAL due to bad TVS device tag.
Explanation: The TVS Node Agent has marked the indicated AMP fatal because a valid device tag could not be found
on the device, and this device would potentially need to be accessed by that AMP. This determination is made because the
AMP belongs to the same TVS allocation subpool as the failed device. Please check other events to get all AMP Vprocs,
which are marked FATAL.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: The device must have a TVS device tag, or must be removed from the configuration. A restart will be required
before the AMP can be placed online.

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