Teradata SQL Error and Failure Codes from Error 2905 To 2914

2905 Status of NVRAM differs among AMPs.
Explanation: Not all AMPs have the same NVRAM status, or a late joining AMP’s NVRAM status differs from the rest
of the system.
Generated By: SSSMain or SSSSPF.
For Whom: DBA Site support representative
Notes: This is a warning rather than an error. It does not cause a crash, but should be reported to a user.
Remedy: Make NVRAM status consistent across AMPs.

2906 Multiple restores had mismatching RESTORE FALLBACK options.
Explanation: During a sequence of all-AMP restores of a fallback table, some restores used the RESTORE FALLBACK
option while the current one did not, or vice-versa.
Generated By: Host Utilities.
For Whom: End User.
Remedy: All restores of the same tables must use the RESTORE FALLBACK option, or all must not use this option. If the
preceding restores did use the option, then correct the current one by using the RESTORE FALLBACK option. If the preceding
did not use the RESTORE FALLBACK option, then remove it from the current restore.

2907 The recovery configuration has changed.
Explanation: During a restore, rollforward or rollback operation using the primary data option upon a fallback table, or
during a build operation upon a fallback table, the DBC configuration which existed during the initial cluster restore of the
of the fallback table has changed.
Generated By: Host Utilities.
For Whom: End User.
Remedy: If an AMP was brought back online, then take the AMP offline again. If this is not reasonable, the repeat the
restore of the AMP’s cluster for the fallback table.
If an AMP was taken offline, then the restore of the AMP’s cluster must be repeated for the fallback table. If the error
occurred during an all-AMPs restore operation of a cluster dump then the entire restore process must be repeated.

2908 Specified Cluster does not exist.
Explanation: A cluster number specified by the user in a cluster-level host utility operation does not correspond to that
of a currently configured cluster.
Generated By: Host Utilities.
For Whom: End User.
Remedy: Resubmit the request with the correct cluster number.

2909 The restored journal already exists on the specified AMP
Explanation: The restored permanent journal already exists upon one or more AMPs referenced in a specific- AMP Host
Utilities permanent journal restore.
Generated By: HutRDB
For Whom: User.
Remedy: The restored journal must be deleted to perform the requested restore operation. This may be achieved by
using the Delete Restored Journal Host Utilities statement.

2910 The journal to restore does not match the one for
Explanation: A database references a different permanent journal table than the one being restored.
Generated By: HutInr
For Whom: User.
Remedy: If the journal being restored is the one that is wanted, drop the journaling in the database. Otherwise, the
restore must be done from a different archive data set.

2911 A specific-AMP restore specified more than the maximum sessions.
Explanation: A specific-AMP restore may specify no more than sixteen sessions per AMP. This value was exceeded.
Generated By: HutSTbl
For Whom: User.
Remedy: Correct the number of sessions in the SESSIONS= parameter of the Host Utility program. This number should
be an even multiple of the AMPs involved in the restore process.

2912 Permanent Journaling is inconsistent for a table being restored.
Explanation: Restore found a table that references a permanent journal which no longer exists.
Generated By: HutRecvy
For Whom: User.
Notes: When restoring a data table, a dictionary row for the data table contained a reference to a non-existent permanent
Remedy: The only way to restore the table is to restore the journal first. Since the journal does not exist, the journal
restore must be preceded by a restore of database DBC.

2913 A specific-AMP recovery was executed out of order.
Explanation: A specific-AMP rollback or rollforward was attempted on a nonfallback table with unique secondary
Generated By: HutRecvy
For Whom: User.
Notes: A specific-AMP rollback or rollforward of nonfallback tables with unique secondary indexes should never happen.
If a rollforward then it should have been preceded by either a restore (if recovering from a hardware failure) or by an
all-AMPs rollforward if recovering from some other error. Either of these actions would invalidate any unique secondary
indexes on the table. If a specific-AMPs rollback is being attempted then it should have been preceded by an all-AMPs rollback.
Remedy: Resubmit the Utility actions in the sequence described above. Note that dropping the index will cause the
structure version of the table to be changed. A rollforward or rollback is not allowed across a structure change.

2914 A TIP/Task Matchup failure has occurred.
Explanation: A terminating task’s transaction table has an erroneous task list.
Generated By: AwtTIPSt/AwtInfi
For Whom: Site support representative.
Notes: This error indicates that AMP software has detected an internal inconsistency of some sort. Determination of the
cause of the error requires analysis by your Support Representative.
Remedy: Contact your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 2905 To 2914 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.

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 *