Teradata SQL Error and Failure Codes from Error 2534 to 2544

SQLServerF1

2534 System recovering from disk read error on spool file.
Explanation: A disk read error is encountered. The bad data block was in a spool file and will automatically recover
when the system restarts.
Generated By: RbkCtrl.
For Whom: Operator.
Remedy: None. The Teradata DBS will restart itself and automatically recover from the disk read error.

2536 Data lost while recovering from a read error.
Explanation: A disk read error occurred in a table which:
1) has no fallback copy, or 2) is an abended fastload table, or 3) is an abended restore table, or 4) is an invalid index table, or
5) is a permanent journal table, or 6) has been recovery aborted. 7) has been rebuild aborted. 8) has been reconfig aborted. 9)
has fallback copy with amp down in the cluster. 10) is one of the following mload work subtables: – private permanent journal.
– local checkpoint – foreign checkpoint – bit map – data 11) was corrupted in other amp in the cluster such as missing
table header or table is being rebuilt. 12) is mload dump work subtable.
Some data was lost, and the Teradata DBS cannot or will not rebuild it.
Generated By: U2URBK/RbkRcvy.
For Whom: Operator. DBA. End User.
Notes: Table header will be updated to indicate rebuild in process if rebuild failed.
Remedy: If the table has no fallback copy, you may recover the table from an archive.
If the table is in fastload state, you may delete all the associated fastload tables and resubmit the fastload job.
If the table is in restore state, you may recover the table from an archive.
If the table is an invalid index table, you may drop the index and recreate the index.
If the table has been recovery aborted, you may drop it or recover the data from an archive.
If the table has been rebuild aborted, you should try to rebuild the whole table via Rebuild utility.
If the table has been reconfig aborted, you may drop it or recover the data from an archive.
If the table is a permanent journal table, Contact your Support Representative.
If there is an amp down in the cluster, we should try to bring the down amp back to configuration and attempt to rebuild
the table again. If rebuild fails after down amp rejoins the configuration, it usually means the table has been rebuilt aborted
in more then one amp in the cluster. In order to recover the data, you may need to do restore and rollforward.
If the table is one of those mload work subtables which can not be recovered due to no fallback. In order to recover the target
table prior mload take place, restore (and rollforward) may require.
If the rebuild table was corrupted in other amp in the rebuild cluster, in order to recover the target table prior mload take
place, restore and rollforward may require.
If the table is mload dump work subtable, subtable will be deleted, however table header will NOT be marked as rebuild in process.

2537 ErrAmpSegV – Segmentation Violation in AMP
Explanation: This error occurs when a program attempts to access a memory location that is not allowed to access.
Accessing a nil ptr is one of the cases that leads to segv. The segmentation violation can also be caused by a task stack overflow.
This error leads to a system restart.
Generated By: AMP software.
For Whom: Site support representative.
Remedy: Save the crashdump. Have all the traceback information ready. Then contact your support representative.

2538 A disk read error occurred in the tables area.
Explanation: A disk read error occurred in DBS tables DCR5858-cy2-01 area of the disk. An attempt will be made to
recover the data. If recovery is not possible, either the system will crash or the data table will remain locked. An event will
be logged that indicates what action the Teradata DBS will take.
Generated By: RbkCtrl.
For Whom: Operator. DBA.
Remedy: This is an information only message. The next event logged will inform the user of the action taken as a result
of the error.

2542 Requested rebuild is already running.
Explanation: This is an internal status error created when a restartable rebuild is attempted on an AMP which is currently
running a rebuild.
Generated By: RbdRstar
For Whom: Operator.
Remedy: Allow the first rebuild to finish.

2543 Operation not allowed: %DBID.%TVMID is being Rebuilt.
Explanation: This error occurs only when a user issues a request for a table that is being Rebuilt.
Generated By: AMP Steps.
For Whom: End User.
Notes: The table does exist, but it is not in a form in which it may be accessed.
Remedy: Wait until the Table Rebuild is finished, then resubmit the request.

2544 Operation not allowed: %DBID.%TVMID had an error when Rebuilt.
Explanation: This error occurs only when a user issues a request for a table that was Rebuilt, and the rebuild did not successfully
complete.
Generated By: AMP Steps.
For Whom: End User.
Notes: The table does exist, but it is not in a form in which it may be accessed.
Remedy: Either resubmit the request after the table has been restored or drop the table.

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