Teradata SQL Error and Failure Codes from Error 2724 To 2733

2724 The two-phase commit transaction is in-doubt.
Explanation: An in-doubt transaction was detected during a restart.
Generated By: AMP
For Whom: End User.
Notes: The transaction was in this state when the DBC was restarted.
Remedy: The transaction must be committed or aborted by the coordinator automatically, or by the TPCCONS utility.

2725 Too many 2PC transactions for COLDWAIT restart
Explanation: Too many in-doubt transactions exist to allow a COLDWAIT DBC restart. The DBC will be restarted with a
COLD restart.
Generated By: AMP
For Whom: Operator. DBA.
Notes: This condition occurs if the number of in-doubt 2PC transactions on the on-line AMPs in a cluster with a catch-up
AMP exceeds the total capacity (number of in-doubt transactions) the catch-up AMP would have to establish in a COLDWAIT
restart.
Remedy: Following COLD restart of the DBC, the in-doubt 2PC transactions must be committed/aborted in order to
reduce the number of in-doubt 2PC transactions. A subsequent COLDWAIT restart should allow the catch-up AMP to
come on-line.

2726 Referential constraint violation: cannot delete/update the Parent Key value.
Explanation: At least one of the Parent Key (i.e. referenced columns) values being deleted or updated is referenced by
some Foreign Key values. By definition, the Parent Key value cannot be deleted or updated if there exists a Foreign Key
value which is referencing it. Note, this is typically caused by an SQL Delete or Update statement on a referenced table.
Generated By: SutCKPRw.
For Whom: End user.
Remedy: Delete the corresponding Foreign Key value from the Child table (i.e. referencing table) first and then resubmit
the request.

2728 Aborted due to a non-valid reference index on %DBID.%TVMID.
Explanation: The table being accessed has a reference index that is not valid. This could be resulted from the following
two cases: (1) The target table or other table which references or being referenced by the target table was rollforward/back
or restored. (2) The target table has some unresolved references because it is referencing some non-existent tables.
For either case, no inserts, updates, or deletes are allowed.
Generated By: SutCK1Rw & SutCKNRw.
For Whom: End user.
Remedy: For the Roll and Restore case, drop the corresponding referential constraint and resubmit the request. For the
unresolved references case, create all the missing referenced table and resubmit the request.

2729 Dictionary parent count does not match header parent count.
Explanation: This message is displayed if the parent count field in the table header does not match the corresponding
parent count in the DBC.TVM record for the table.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2730 Warning: RI is not valid on one or more AMPs.
Explanation: This message is displayed if any AMP does not have the valid state set for the reference index. All remaining
checks for the index are bypassed. The possible RI states are ValidRI, InvalidRI, InconsistentRI, and UnresolvedRI.
ValidRI is the normal state. InvalidRI means that there has been a rollforward/rollback operation on the table. InconsistentRI
means there has been a restore operation on the table. Since the parent or child table might not be restored at the same
time, the state is marked as inconsistent. A Revalidate command can be used to revalidate the RI. UnresolvedRI means this
is a forward reference and the parent table has not been created yet. The RI state will be changed to ValidRI when the parent
table is created.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2731 Warning: Unable to access the parent table header.
Explanation: This message is displayed if any AMP fails to lock the parent table or fails to read the parent table header.
All remaining checks for the index are bypassed.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2732 Warning: Skipping parent key validation in level 3 checking.
Explanation: This message is displayed if any AMP fails to lock the parent table in order to check the parent keys. Only
parent key validation is bypassed in level 3 checking.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

2733 Primary and fallback RI row checksums do not match.
Explanation: A mismatch is detected when the checksum of the primary copy of a reference index row is compared to its
fallback copy.
Generated By: CheckTable.
For Whom: Site support representative.
Remedy: Contact your Support Representative.

Above are list of Teradata Errors or Failure Codes from Error 2724 To 2733 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 *