ARC1264 The previous message reported a problem with PPI error table %s.%s that must be corrected before this job can continue.

Archive/Recovery (ARC Prefix) Messages

brand
Teradata Tools and Utilities
prodname
Teradata Tools and Utilities
vrm_release
15.10
category
Programming Reference
featnum
B035-1096-151K

ARC1264 The previous message reported a problem with PPI error table %s.%s that must be corrected before this job can continue.

Explanation:

This is an error during a RESTORE or COPY of a PPI table. A PPI error table is required when restoring or copying a PPI table. DBS error codes 3803, 3807, and 6856 indicate that the DBS has detected a problem with the PPI error table. See the following for details.3803 error ("Table xyz already exists."). Means that the DBS is trying to create the PPI error table but it already exists. This generally occurs when a PPI error table is not deleted by a previous ARC job. A PPI error table will not be deleted if it contains one or more rows. Rows get inserted into the PPI error table because they were not inserted into the target table during a previously executed restore or copy job. The rows in the PPI error table need to be evaluated by the user to determine if they should be inserted into the target table or discarded. After inserting/discarding all rows, the user can re-submit the job. If the same job syntax is to be used when re-submitting this job, the specified PPI error table should either be dropped or renamed first. Alternatively, you could specify that another table (that doesn t already exist) be used as the new PPI error table. But in this case, you will need to change the job syntax to specify this new PPI error table with the ERRORDB or ERRORTABLES clause. 3807 error ("Object xyz does not exist."). Means that the PPI error table must already exist but it does not. This can occur during a cluster or specific AMP restore/copy if you don t execute a dictionary restore/copy (which will create the PPI error table to be used during the data tables restore/copy phase) before executing the data tables restore/copy statement. It could also mean that the user inadvertently dropped the PPI error table during the restore/copy. A 3rd possible cause would be if an invalid restart were to occur. One case of an invalid restart would be if you did a restart of the restore/copy statement but you restarted the restore/copy of the wrong database or table. If executing a cluster or specific AMP restore/copy, make sure that a dictionary restore/copy statement is included before the data restore/copy statement and re-submit the job. If not a cluster/AMP restore/copy, determine why the PPI table was dropped and correct it before re-submitting the job. 6856 error ("Restore error table has wrong structure."). Means that the PPI error table must exist, it does, but it is not the PPI error table for this target table. See the description of DBS error code 6856 for detailed information on the problem detected and how to correct it.

For Whom:

 End User.

Notes:

This error message is only displayed if a 3803, 3807, or 6856 error message was also displayed as the previous message.

Remedy:

See the "Explanation" section above for specific details on what problem was detected by each error code and how to correct it. Correct the problem with the PPI error table and re-submit the job.