Teradata SQL Error and Failure Codes from Error 7476 To 7487

7476 Replication utility not allowed on unhashed table %DBID.%TVMID.
Explanation: Replication utility operation is not allowed on a unhashed table.
Generated By: Replication Utility
For Whom: Replication Services Gateway
Remedy: None.

7478 Table %DBID.%TVMID is not a user table.
Explanation: The object of a replication utility must be an user table. This error indicates that the object is a dictionary
table, permanent journal or a spool/ materialized temporary/volatile table or a join index table.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: None.

7479 Table %DBID.%TVMID is not a replicated table.
Explanation: The object of a replication utility must be a replicated table. This error is detected when the RSErrorTblId
in the table header is AMPNullUnique. That is, an Add Table operation hasn’t been performed on this table.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: Perform an replication add table operation on this table before resubmitting the request.

7480 Error table does not exist for table %DBID.%TVMID.
Explanation: The error table for the copy destination table does not exist when Replication utility tried to access the
table using the RSErrorTblId from the copy destination table header.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: None.

7481 Operation with same utility Id and table Id already running.
Explanation: Teradata DBS uses both utility Id and table Id to uniquely identify an utility operation. This error informs
RS that there is already one utility operation running on behalf of the same utility Id and table Id.
Generated By: AMP
For Whom: RSG
Remedy: None.

7482 Cannot obtain lock on %DBID.%TVMID for error/difference row insert.
Explanation: This error is returned when inserting a row into error difference table failed because a lock could not be
obtained. This could due to a deadlock, lock busy or lock table is full.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: None.

7483 Warning: RI checks bypassed for Referential Constraints.
Explanation: This warning message is displayed for Referential constraints (soft RI/Batch RI). All remaining checks for
this Referential Constraint are bypassed.
Generated By: CheckTable.
For Whom: Site support representative.
Notes: This warning message is seen when CheckTable utility is run on a table containing Referential Constraints(soft
RI/Batch RI).
Remedy: Contact your Support Representative.

7484 Division by Zero occured while calculating the given OLAP function(s).
Explanation: This error is returned when Division by Zero occurs while calculating OLAP statistical functions like Mlinreg.
For Mlinreg function this error indicates that the Window width is less than or equal to the number of Non Unique Sort
keys. i.e., No. of rows with same sort key >= Window Width mentioned.
Generated By: STPSTATFN
For Whom: USER
Remedy: For Mlinreg function check the table given for calculating the function. Try changing the Window width and
also check the table so that no. of non unique sort keys are not greater than or equal to Window width value.

7485 The table is marked as being Fast/Multi loaded.
Explanation: This error will be displayed if the table is detected as being Fast/Multi loaded during AMP level restore. In
this situation, restore will skip the table and will continue on to the next table instead of aborting the whole job.
Generated By: HutRdb
For Whom: End User
Remedy: Finish Loading and restore the Table OR do All AMP restore.

7486 The table is marked as being restructured.
Explanation: This error will be displayed if the table is detected as restructured during AMP level restore. In this situation,
restore will skip the table and will continue on to the next table instead of aborting the whole job.
Generated By: HutRdb
For Whom: End User
Remedy: Do all AMP restore on the table.

7487 AMP step failure: Please do not resubmit the last request.
Explanation: The transaction was aborted due to an unexpected error while processing an AMP step. The failing step
and the specific error event are described in the variable text extension displayed in the one or two lines immediately following
the fixed error message text.
Generated By: AMP step handlers.
For Whom: End User. Site support representative.
Notes: The %VSTR variable string only will print at stream log, takes a variety of forms depending on the failing step,
the tables accessed by the step, and whether the error occurred on a table access operation. The general syntax of the message
is as follows:
DR53527-cy2-01 –>
Amp <amp-id> error <error-id> <curr-table> in <step-id>: <step-text>
where: <amp-id> := <amp-n> | <amp-n> on <node-n> <error-id> := <err-n> | <err-n>(<err-detail>) <curr-table> :=
<null> | on <table> |, at <table> <step-id> := stmt <stmt-n> step | step (<step-n>) | step (<step-n>.<substep-n>) <steptext>
:= <step-name> | <step-verb> <step-table> | <step-name> using <table> | Receive Hashed rows from <step-name>
| Receive Duplicated rows from <step-name>
<amp-n> = “%d” : failing Amp vproc <node-n> = “%d-%d” : node where <amp-n> is located <err-n> = “%d” : failing error
code <err-detail> = “%s” : short failure detail text <stmt-n> = “%d” : failiing statement number <step-n> = “%d” : failing step
number in request EXPLAIN <substep-n> = “%d” : failing parallel substep in EXPLAIN DR53527-cy2-01 <–
The transaction abort will be accompanied by a snapshot dump of the failing Amp task whenever the snapshot dump
capability is available on the system and enabled for general usage. If the user disables snapshot dumps for specific failure
cases, however, or if the amp logic disables snapshots temporarily because too many have been done recently, then the amp
will handle the failure with a full system restart rather than a transaction abort.
When used as the event code key in the software event log or the related streams log display, the ERRAMPFAILABORT
code is always coupled with another error code for the amp failure that caused the associated snapshot dump and abort
event. An event will also be logged under that associated error code, with additional information in some cases logged as
separate events using ERRAMPFAILINFO or ERRAMPFAILTEXT.
Remedy: END USER:
First, obey the admonition in the error message and do not resubmit the query containing the failing request until the
underlying problem in the AMP software has been analyzed. Although retries of the failing request might contribute to this
problem analysis, any such diagnostic tests should be performed only by authorized support personnel.
One possible outcome of the analysis is to conclude that the failure occurs rarely, with no harmful side-effects, and that it is
therefore safe to retry the query or job manually when it occasionally fails with the same reported symptoms. Note that this
sort of workaround should always be done manually, however, and only for the specific problem case for which it has been
authorized.
The following caveat should therefore be applied:
WARNING: Never use error-handling logic in a production application that treats the 7487 error code as retryable. SITE
SUPPORT STAFF:
If a snapshot dump was taken, make sure it is saved to the crashdumps database for offloading. Have all traceback and
associated information from the error log ready and then contact the Global Support Center.
As noted above, the Global Support Center might determine that the failing query or job can be manually retried for a specific
7487 failure case as a workaround until a fix for the underlying problem is available. These workaround details should
be carefully noted so that manual retries can be strictly limited to the authorized failure cases.

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