Teradata SQL Error and Failure Codes from Error 7458 To 7466

7458 Checkpoint failed for replication copy/compare operation.
Explanation: The error indicates a failed checkpoint on the destination side for a replication utility. The utility is to be
continued from the previous checkpoint.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: This error is internal between RS and TD. It is to notify RS that the checkpoint at destination side was not successful
and that the utility should be continued from the previous checkpoint on the source side.

7459 Table %DBID.%TVMID not allowed to be both the source and the destination of a replication utility.
Explanation: A table can not be both the source and the destination of a copy or compare operation.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: None.

7460 Cannot continue utility operation on %DBID.%TVMID because system configuration has changed.
Explanation: The utility was restarted after a source/destination system reset and the the configuration of the reset system
has changed.
Generated By: Replication Utility
For Whom: RSG (Replication Service Gateway)
Remedy: The current utility can not be continued and must be aborted. After the abort is completed, a new utility can be
submitted for the same object.

7461 Invalid logon user name for utility.
Explanation: The logon user name was not present in the utility Prepare message or the user name does not exist in system.
Generated By: Replication Utility.
For Whom: RSG (Replication Service Gateway)
Remedy: Resubmit the request with a valid user name.

7462 Operation not allowed: pending table copy operation on table %DBID.%TVMID.
Explanation: This error occurs when a user issues a request for a table that is being copied.
Generated By: AMP Steps/HUT/EDT
For Whom: RSG
Notes: The table does exist, but it is not in a form in which it may be accessed.
Remedy: Wait until the copy operation is finished, then resubmitting the request.

7463 Too many concurrent table copy operations running on system.
Explanation: The maximum number of table copy operations a user can run concurrently on a system is defined by the
constant RepMaxSimulUty (15).
Generated By: AMP.
For Whom: End user.
Remedy: Wait until other table copy operations are completed and system resources are freed up then resubmit the
request.

7464 Compare difference table %DBID.%TVMID has incorrect definition.
Explanation: The defintion of the compare difference table should have the following definition:
field 1 : error code (data type SMALLINT, Not Null) field 2 – N : primary key columns from target table. The data type of
each columns should be identical to that of target table and the columns should be in the order the primary key appears in
DBC.Indexes table (The FieldPosition in DBC.Indexes indicates the order of the index columns. It is in field Id order.) These
columns should also be defined as the nonunique primary index of the compare difference table.
Generated By: Replication Utility.
For Whom: RSG (Replication Service Gateway)
Notes: The primary key index Id of target table can be obtained from DBC.TVM and the primary key index columns and
the order of it can be obtained from DBC.Indexes. The data type of each column can be obtained from DBC.TVFields.
Remedy: Correct the definition of the compare difference table and start a new utility.

7465 Mload table %TVMID cannot be released because permanent journals exist.
Explanation: The user attempted to release an Mload Apply Lock on table that has permanent journals. The table had
been the target of an Mload that was aborted in the Apply Phase. There may be inconsistencies between the partial changes
done to the target table and its permanent journal images.
Generated By: STPERE
For Whom: User.
Notes: In order to be able to release an Mload Apply Phase or Restoration Lock, the table must not have permanent journals
or the table is empty.
Remedy: The table must be dropped from the database. If this table is defined as a member of the replication group, then
it must be removed from the replication group first using ALTER REPLICATION GROUP statement.

7466 Invalid utility Id.
Explanation: This error is returned in the following cases:
– The utility Id passed in the subsequent REP messages does not match with the utility Id in the RepPrepare message which
started the utility.
– The utility Id passed in the RepPrepare message for a restarted utility operation does not match with the utility Id
recorded in the system.
Generated By: AMP
For Whom: RSG
Remedy: None.

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