Teradata SQL Error and Failure Codes from Error 15058 to 15066

SQLServerF1

15058 AMP Vproc %d has been marked FATAL due to failed TVS gerrymander.
Explanation: The TVS Node Agent has marked the indicated AMP fatal because an attempt to gerrymander one of the
AMP’s devices failed. The gerrymander operation is typically due to a configuration change. 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 be successfully gerrymandered, or must be removed from the configuration. A restart will be
required before the AMP can be placed online.

15059 PDISK %d has failed to gerrymander into the configuration.
Explanation: The TVS Node Agent has detected a gerrymander failure on the indicated PDISK. This may affect one or
more AMPs if there is a potential for those AMPs to have data on this device. Please check other events to get all PDISKs,
which have failed to gerrymander.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15060 PDISK %d has a missing or corrupted TVS device tag.
Explanation: The TVS Node Agent has detected a TVS device tag failure on the indicated PDISK. This may affect one or
more AMPs if there is a potential for those AMPs to have data on this device. Please check other events to get all PDISKs,
which have missing or corrupted TVS device tag.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: If the device is a new device, run the tvsaDeviceInit utility to format the device (or use PUT to do this). If the
device is an existing device whose TVS device tag has been corrupted, use the tvsaFixTag utility to place a new tag on the
device. WARNING: using tvsaFixTag on a device with any other corruption besides a missing TVS tag can cause other,
worse problems. Do not bring up the database on a system where a TVS tag has been manually applied unless you really
know what you are doing.

15061 Problem mapping pdisks to amps: %s
Explanation: This usually indicates that the vconfig GDO does not agree with the tvsa_vdisk_mapping file. The
tvsa_vdisk_mapping file is generated during upgrade to a release of Teradata software containing TVS, and is a snapshot
of the PUT-generated tvsa_preferred_mapping file at the time of the upgrade. Pre-TVS disk conversion cannot proceed
unless this problem is resolved.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Upgrades to releases of Teradata containing TVS must not be combined with any vdisk or amp configuration
changes. Contact the Global Support Center.

15062 AMP Vproc %d has been marked fatal due to a fatal TVS vproc.
Explanation: The TVS Node Agent has marked the indicated AMP fatal because it belongs to an allocation subpool serviced
by a fatal TVS vproc (the vproc that is logging this event). Please check other events to get all AMP Vprocs, which are
marked FATAL.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: The failed TVS vproc will be seen in previous event log(s). Fix the problem that caused this TVS vproc to go
fatal, then use vprocmanager to bring the fatal TVS vproc and all affected AMPs back online.

15063 An I/O was performed by AMP %d whose assigned TVS vproc is not online
Explanation: Normally if a TVS vproc is not online, its assigned AMPs are marked fatal and should be performing no
I/Os. But an I/O was performed either by the indicated AMP or by another process masquerading as the indicated AMP.
This message will appear a maximum of once per TPA cycle, regardless of how many different times the event occurs and
regardless of how many different AMPs are behaving this way.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15064 Pdisk device %d is mapped to more than one pdisk %s
Explanation: There is an error in vconfig that is causing the same physical device to be mapped to more than one pdisk.
This could be a simple typographical error in the vconfig, or it could be caused by incorrect entries in the system’s device
directory (different names aliased to the same physical device). It could also be caused by local disk name collisions in different
nodes which should be in different cliques but are mistakenly in the same clique. Because of the ambiguities inherent
in this error, it is regarded as fatal.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15065 Device %s %s has been failed intentionally
Explanation: The TVS Node Agent configuration has specified that a particular device is to be marked as failed intentionally.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15066 PDISK %d has a different size than specified in the vconfig.
Explanation: The TVS Node Agent has detected a TVS storage device whose actual size differs from the size specified
for it in the vconfig. This error must be corrected before the device will be used. This may affect one or more AMPs if there
is a potential for those AMPs to have data on this device. Please check other events to get all PDISKs, which have different
size than specified in vconfig.
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 15058 to 15066 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 *