Teradata SQL Error and Failure Codes from Error 15067 to 15075

SQLServerF1

15067 Unable to determine the size of PDISK %d: error %d
Explanation: The TVS Node Agent has detected a TVS storage device whose actual size cannot be determined. This may
be because the device does not exist, or because it is inaccessible. 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, whose sizes are not determined.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: If this device is actually a file, make sure the file exists. Otherwise, contact the Global Support Center.

15068 Name of PDISK %d is too long
Explanation: The name given for this pdisk in the vconfig GDO is causing an internal data structure to overflow.
Because of this, the pdisk will be marked as inaccessible. 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, whose names are long.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Edit the vconfig, use a shorter name for the pdisk, and regenerate the vconfig GDO. If it is not possible to use a shorter name, contact the Global Support Center.

15069 PDISK %d has incorrect System ID in its tag
Explanation: A mismatch was detected between the system ID contained on the indicated PDISK and the actual system
ID as contained in the tvsa_data file. This could occur because the device has not been properly initialized into the system’s configuration. If this error is appearing for all devices, it may be because the tvsa_data file (in the TDCONFIG directory) has been corrupted. Because of this error, the pdisk will be marked as inaccessible. 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 incorrect System ID.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Depending upon the reason, you must fix the cabling, use proper procedures to add storage devices to the system, or restore a good copy of the tvsa_data file.

15070 PDISK %d has incorrect device number %d in its tag
Explanation: A mismatch was detected between this pdisk’s global device number as given in the vconfig GDO, and the
disk’s actual global device number from its device tag. This is likely the result of a cabling error although it could be the result of adding disks to the system without following the recommended procedures. Because of this error, the pdisk will be marked as inaccessible. 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 incorrect device number.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Depending upon the reason, you must fix the cabling, or use proper procedures to add storage devices to the
system.

15071 AMP Vproc %d has been marked FATAL due to incorrect system ID on one of its pdisks.
Explanation: The TVS Node Agent has marked the indicated AMP fatal because one or more of its pdisks contains a system
ID not matching that of the system it is configured into. Please check other events to get all AMP Vprocs, which are
marked FATAL.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: The mismatched system ID needs to be corrected first. A restart will be required before the AMP can be placed
online.

15072 AMP Vproc %d has been marked FATAL due to incorrect device number on one of its pdisks.
Explanation: The TVS Node Agent has marked the indicated AMP fatal because one or more of its pdisks contains an
incorrect device number. Please check other events to get all AMP Vprocs, which are marked FATAL.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: The incorrect device number needs to be corrected first. A restart will be required before the AMP can be
placed online.

15073 TVS migration parameter %s from %d to %d.
Explanation: Some migration parameters in control GDO can be dynamically changed without a restart, initial and
changed values are logged.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: N/A

15074 Device global number %d is not unique.
Explanation: TVS relies on devices being tagged with a unique global device number in the Vconfig GDO. The given
device number was found duplicated in more than one device entry. Please check other events to get all devices, whose
numbers are not unique.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Fix the vconfig.

15075 Creation of storage capacity on demand file failed at line %s”
Explanation: An attempt to open and write entries to the /proc/tdsched/tvs_percentage file could not be completed.
Generated By: TVS Node Agent
For Whom: Field Engineer
Remedy: Agent log files will contain more information on the error. Repair the condition and restart.

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