Restarting Uncompleted Reorganization Requests with SAPDBA (SAP Library - SAP Database Guide: Informix (BC-DB-INF-DBA))

Restarting Uncompleted Reorganization Requests with SAPDBA

Use

A restart is automatically invoked by SAPDBA for Informix when you attempt to start a reorganization of a group of tables or dbspace using the same source dbspace and dbspace to reorganize as you used for a previous request that did not successfully complete.

For more information about how to proceed when a reorganization was unsuccessful, see Reorganization Troubleshooting with SAPDBA.

Prerequisites

SAPDBA is installed correctly. Refer to SAPDBA Setup.

You are logged on in expert mode, that is, as user informix , and you have started SAPDBA. Refer to Starting SAPDBA.

You start a reorganization and then see a message such as in the following example, indicating that SAPDBA is about to automatically perform a restart:

There already exists a request for tables selected from
‘psapddic’ that was not successful for all tables!

Do you want to restart the uncompleted request?

Note

You do not see this message unless you try to execute exactly the same request as one that previously failed.

Procedure

Decide whether to restart the uncompleted request or not:

If you decide

Then SAPDBA

To restart the request

Offers to update the request if any of the tables in the request have meanwhile been used (for example, if R/3 was productive during the interruption). You must update the request if the number of rows of any of the tables has changed.

Caution

Do not update the request if you have had a severe failure in which database data has been lost (for example, a database host machine or disk failure). In this situation, you must do a restore. Refer to "Database Host or Disk Crash" at the end of Fixing Difficult Reorganization Problems with SAPDBA.

The procedure continues below.

Not to restart the request

Offers to delete the request. You can also delete the request using Deleting Uncompleted Reorganization Requests with SAPDBA.

The procedure is now finished.

SAPDBA displays a summary of the tables comprising the uncompleted request, broken down into the following categories:

WAITING

These tables have not yet been processed by SAPDBA. This was probably due to a fatal problem found for another table, which caused SAPDBA to abort the entire processing run.

FAILED

These tables were not successfully processed by SAPDBA due to some critical problem and SAPDBA had to abort processing on such tables.

Select whether you want to include the tables in the above categories in the restarted processing run. If preferred, you can restart the process a number of times, until you have re-processed all the tables from the uncompleted request.
Choose Execute to perform the restart.

SAPDBA performs the reorganization. SAPDBA writes data to the same date-stamped directory used in the original request. For more information, see SAPDBA Files, Directories, and Reports and Reorganization Log with SAPDBA.

Result

After a reorganization, your database is less likely to run into space problems. However, you need to keep on monitoring the tables, especially if they are growing rapidly. Refer to Analyzing Tables by Fill Level, Size, and Extents with SAPDBA.

You must now finish the table reorganization.