Teradata SQL Error and Failure Codes from Error 2556 to 2567

SQLServerF1

2556 Duplicate match tag found.
Explanation: Duplicate match tag found in MLoad work tables.
Generated By: STPEDM
For Whom: MLoad Host Utility.
Notes: Each DML step should provide unique match tag, the utility should ensure the uniqueness of each match tag.
Remedy: Cancel the MLoad job on the host. Correct the error to ensure match tag uniqueness.

2557 Too many target tables in the MLoad job.
Explanation: DBS received too many MLOAD steps.
Generated By: AMP MLoad Processing.
For Whom: Mload host utility.
Notes: One MLoad operation can only handle 5 target tables. The Utility should terminate and report error if more than 5 target tables are used.
Remedy: Cancel the MLoad job on the Host. Correct the Utility to include the limit check.

2558 The Mload step was sent more than once.
Explanation: DBS received the same MLoad step.
Generated By: StpEED
For Whom: MLoad host utility.
Notes: If DBS receives the same MLOAD step more than once, this must be a programming error.
Remedy: Contact your Support Representative.

2559 MLoad not allowed: %DBID.%FSTR is a permanent journal table.
Explanation: This error occurs only when a user issues a request for a table that is a permanent journal table.
Generated By: STPEBE
For Whom: End User.
Notes: The table does exist, but it is not in a form in which it can be edited by user.
Remedy: Remove the journal table from your MLOAD job and resubmit the request.

2560 Mload table has not been initialized for MLoad.
Explanation: This error normally means field 4 is missing in the table header of the MLoad related table.
Generated By: AMP MLoad Steps
For Whom: Site support representative
Notes: All the MLoad related tables must have field 4 defined in their table headers.
Remedy: Contact your Support Representative.

2561 MLoad related table %TVMID has bad usage field in table header
Explanation: The usage field in the table header does not match with the real usage of the table.
Generated By: AMP MLoad Steps
For Whom: Site support representative
Notes: The usage field in field 4 of table header of target table and error tables should be Target. The usage field in field 4
of table header of work tables should be Worktable.
Remedy: Contact your Support Representative.

2562 MLoad not allowed: table %TVMID has been rebuilt.
Explanation: While the table is being edited, table was rebuilt and failed.
Generated By: AMP MLoad step.
For Whom: End User.
Notes: Some data is lost, and cannot be recovered.
Remedy: Drop this table and its associated tables, and resubmit the MLoad job.

2563 MLoad not allowed: DBS had been reconfigured.
Explanation: The Teradata DBS had been reconfigured before the table completed the editing.
Generated By: AMP MLoad step.
For Whom: End User.
Notes: Partial data was edited and the Teradata DBS was reconfigured. The data in the Teradata DBS was invalidated.
Remedy: Drop this table and its associated tables, recreate them, then resubmit the request.

2565 The operation does not honor Single Processor Recovery mode
Explanation: The operation that caused the system reset does not allow Single Processor Recovery mode. The operation
is most likely RECONFIG.
Generated By: ACTSPF.
For Whom: End User.
Remedy: None.

2566 Processor %s failed to respond.
Explanation: Processor is hung during Single Processor Recovery operation.
Generated By: SSSSPF.
For Whom: End User.
Remedy: None.

2567 The system has no PE or PEs running
Explanation: There must be at least one PE or PE available before Single Processor Recovery can be performed.
Generated By: SSSSPF.
For Whom: End User.
Remedy: None.

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