Teradata SQL Error and Failure Codes from Error 15026 to 15035

SQLServerF1

15026 TVS vproc %d does not have any AMPs assigned to it.
Explanation: The TVS vproc entry shown is not the assigned allocator for any AMP in the clique. This is an illegal configuration.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Repair the vconfig.

15027 TVS subpool %d contains at least 1 AMP but has no PDISKs.
Explanation: At least one AMP is assigned to the subpool shown. However, no PDISKs belong to that subpool. This
would result in no available storage for the affected AMP(s). This is an illegal configuration.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Repair the vconfig.

15028 PDISK %d in subpool %d is not used by any AMPs.
Explanation: The given pdisk is assigned to a subpool which does not have a TVS vproc managing it or any AMP vprocs
using it. This is an illegal configuration.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Repair the vconfig.

15029 Previously reported error %d should have caused a restart
Explanation: The given error which was previously reported by the TVS Node Agent was expected to cause a restart but
it did not. This is most likely caused by improper error handling in the TVS Node Agent. When reporting the problem,
please show both this and the previous error from the log.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15030 Unable to collect CPU statistics (error %d)
Explanation: A system-specific problem has prevented the TVS Node Agent from collecting CPU workload statistics on
this node. The Node Agent will therefore not be able to send this information to the TVS Migrator, so current CPU workload
will not be a factor in any possible migration decisions.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15031 System stats sampling rate was changed from once per %d to once per %d seconds
Explanation: The TVS Node Agent reduced the requested system statistics sampling rate because the requested rate was
either not supported by the underlying platform or was judged to be too expensive for the benefit gained.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Adjust the configured rate to avoid seeing this message.

15032 System stats distribution rate was changed from once per %d to once per %d seconds
Explanation: The TVS Node Agent reduced the requested system statistics distribution rate to match the sampling rate.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Adjust the configured rate to avoid seeing this message.

15033 Error %d determining local ID for global device %d
Explanation: An error prevented determination of the device local ID from the given device global ID. This is most
likely an error in the vconfig. The device will be marked as inaccessible and all affected amps will be made fatal as a result of this error.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

15034 The I/O error flag has been cleared for AMP Vproc %d.
Explanation: The failing device that previously caused the indicated amp to be marked FATAL due to an I/O error has
been fixed, or has been configured out of the amp. The amp is still fatal, but because the I/O error has been cleared, the amp may now be brought back online with vprocmanager.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: N/A

15035 AMP %d device conversion to TVS format failed: %s
Explanation: The conversion of a device to TVS format has failed. This may be due to the user not having run filer’s
“upgradetvsa” command on the device under the pre-TVS version of Teradata software, a corrupted device, or an
unforseen disk format. It may also be due to a newly installed device that has not been properly initialized.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Revert to the pre-TVS version of Teradata software, bring up PDE (leaving the DBS down), and run the filer.
Check the disk integrity, run the “upgradetvsa” commmand, and try switching Teradata versions to the TVS-enabled one
again. If this event recurs, contact the Global Support Center.

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