Teradata SQL Error and Failure Codes from Error 14054 to 14065

SQLServerF1

14054 Allocator found new device (should have been gerrymandered):%s
Explanation: Allocator found new device (should have been gerrymandered)
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

14055 Request state table is NULL:%s
Explanation: Request state table is NULL
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

14056 Caught exception while invoking timer func:%s
Explanation: Caught exception while invoking timer func
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

14057 Map block version mismatch: %s
Explanation: The version of the allocation map on disk does not match the expected version.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

14058 Evacuation of device failed: %s
Explanation: The device could not be evacuated.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

14059 The migration type selected requires that the number of devices be a multiple of the number of AMPs. %s
Explanation: Some pdisks will go unused because the number of pdisks is not a multiple of the number of AMPs. Several
devices may have this condition. Please check the system for other alerts.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Select a different migrator or contact the Global Support Center.

14060 The migration type selected requires device profile information to operate properly. %s
Explanation: Performance may be negatively affected because the device profiler has not been run on this device. Several
devices may be affected. Please check the system for other alerts.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Run the device profiler, select a different migrator type or contact the Global Support Center.

14061 Bad clique list size:%s
Explanation: Bad clique list size
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

14062 The extent map is being rebuilt. %s
Explanation: The allocator is rebuilding its extent map by scanning the Cylinder Indexes of each extent. This may take
several minutes to complete. The reason for the rebuild is given in the message text.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center if this is not due to an obvious cause such as a device failure, node crash or conversion from a prior release.

14063 The extent map is being rebuilt due to a configuration change. %s
Explanation: The allocator is rebuilding its extent map due to a change in the system configuration. This may take several minutes to complete. Several devices may be affected. Please check the system for other alerts.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center if this is not due to an obvious cause such as a change to the vconfig.gdo.

14064 The affinity area has been removed from a device: %s
Explanation: The device does not qualify for an affinity area. Usually this is due to the device being significantly different from others in the system or a configuration where the number of devices is not a multiple of the number of AMPs. Several devices may be affected. Please check the system for other alerts.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center if this is not due to an obvious cause such as a change to the vconfig.gdo.

14065 A forced rebuild of the Allocator’s map on has been requested %s
Explanation: File system code has called an interface to request that the allocator rebuild its map on a particular disk.
Generated By: TVS Allocator
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

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