Start of Content Area

Procedure documentation Restarting Uncompleted Consistency Requests with SAPDBA  Locate the document in its SAP Library structure

Use

This process is automatically invoked by SAPDBA when you try to start any of the actions from Data Consistency using exactly the same input parameters as those used for a previous request that did not successfully complete.

Note

You do not see the uncompleted request unless you try to execute a request exactly like the one that previously failed.

Prerequisites

You tried to execute a request but it failed or you stopped it deliberately. You are now trying to re-execute exactly the same request.

Procedure

  1. Start a request exactly the same as one that previously failed.

    2. SAPDBA displays a message telling you there is already an uncompleted request. The uncompleted request is identical to the one you have just entered. SAPDBA asks if you want to restart the uncompleted request.

  2. Choose whether you want to restart the uncompleted request.

    3. – If you choose no restart, SAPDBA gives you the chance to delete the request. You can also delete the request using Deleting Uncompleted Consistency Requests with SAPDBA.

    – If you choose restart, SAPDBA displays a summary of the tables comprising the uncompleted request.

    Note

    The remainder of the procedure assumes you choose to restart the uncompleted request.

    The tables comprising the uncompleted request are broken down into the following categories:

    – Tables with a status of WAITING have not been processed by SAPDBA when the uncompleted request was run. This is normally due to a fatal problem found for another table, which caused SAPDBA to stop the entire processing run. The other reason why you might see tables with a status of WAITING is because you stopped the processing yourself.

    – Tables with a status of FAILED could not be successfully processed by SAPDBA due to a critical problem. SAPDBA had to stop processing on such tables.

    For both of these categories, you have the option of setting the current processing run to either re-process the tables in the category, or to leave them for the time being. This allows you to restart the process a number of times, until you have re-processed all the tables that make up the uncompleted request.

  3. Select the reprocessing option for each category of table.
  4. Choose Execute to perform the restart.

Result

Each time you do a restart, SAPDBA creates a new date-stamped directory. The directories are named as follows:

CHECK_<object name>_<date/time stamp>

For example, a check of the table a014 on the 6th January 1997 at 14:24:03 would produce a directory called:

CHECK_a014_970106142403

ONCHECK_cI_BLOB_<date/time stamp>

For example, CHECK_cI_BLOB_970106142403

ONCHECK_cD_BLOB_<date/time stamp>

For example, CHECK_cD_BLOB_970106142403

The date/time stamp is composed of the date (in reverse format) followed by the time.