Teradata SQL Error and Failure Codes from Error 16048 to 16059

SQLServerF1

16048 The SAM update COD request failed due to another request in progress.
Explanation: Only one update cod request may be in progress at a time.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Wait for the current request to complete. If the request won’t complete, contact the Global Support Center.

16049 The SAM update COD request failed because an allocator could not read its configuration file.
Explanation: Each node must have a COD configuration file.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Install the COD configuration file.

16050 The SAM update COD request failed due to a configuration file mismatch.
Explanation: The COD configuration file on each node must match.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Install the correct COD configuration file on each node.

16051 The SAM update COD request failed due to the new limit being too small.
Explanation: For a COD update, the new limit must be at least 110% of the currently allocated cylinders
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Set the new limit needs to a higher percentage.

16052 The SAM update COD request failed due to exceeding the maximum downward adjustment.
Explanation: The COD update maximum downward adjustment limit was exceeded.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Set the new limit to a higher percentage.

16053 The SAM update COD request failed informing an AMP of the change.
Explanation: A COD_PARAMETER_ADJUSTMENT call failed.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

16054 The SAM update COD request failed updating dbc.
Explanation: The updatedbc call failed.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Contact the Global Support Center. Check the updatedbclog.TVS vproc.txt log in tpi-data

16055 Requested TVS Vproc is offline
Explanation: This SAMLIB call requires access to a TVS Vproc.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Use vprocmanager to bring the TVS Vproc back online before attempting this operation again.

16056 The SAM update COD request failed due to a problem with the configuration.
Explanation: For a COD update, at least one grade must be set to at least 30%.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Set the new limit to meet the configuration requirements.

16057 The update COD request failed due to finding sequestered cylinders.
Explanation: Sequestered cylinders indicate a fatal or offline AMP. All AMPs must be online to update COD.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Restart with all AMPS online.

16058 The update COD request failed due to problems with an AMP
Explanation: An offline or otherwise bad AMP was found during a COD update.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Restart with all AMPS online.

16059 A timeout was detected in SamReadCIs()
Explanation: When an MI rebuild is performed, synching is done amongst the AMPs on the node when they call Sam-
ReadCIs. One or more of the AMPs expected to participate in the MI rebuild took too long to call SamReadCIs causing a
timeout. This is normally a benign condition since the AMPs will continue on with the MI rebuild after the timeout. However
the cause of the timeout should be investigated since it is not a normal occurrence.
Generated By: TVS SAM Library
For Whom: Field Engineer
Remedy: Contact the Global Support Center.

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