Restarting a Reorganization (SAP Library - Database Administration (Oracle) with SAPDBA)

Restarting a Reorganization

If an error occurs during the reorganization process, the system issues an appropriate warning message. If the error occurred during the main phase of the reorganization, you can continue the reorganization with the Restart option, once the error has been eliminated. Pay attention to both SAPDBA and ORACLE messages. If serious errors occur, the reorganization process is terminated at the appropriate point.

If you overwrite the default answer [N] to the question: Error in... - Do you want to continue<Y/N> [N] with Y(es) and continue the process despite the warnings, you alone are responsible for any and all consequences. SAPDBA continues the processing as if the error never occurred.

Examples of Error Situations

Errors during the production of the reorganization scripts (preparation phase): Nothing has been altered in the database. The error can be ignored and the reorganization repeated (a restart is not possible because some of the scripts are still missing or may be incorrect).

Errors during processing of scripts up until completion of exports (scripts have been completely created and processing has begun in the main phase):

Before the export, tables were renamed ( HideTab option) or constraints were deleted (i.e. the database has been altered in this respect). A restart of the reorganization is possible without any further action after correcting the cause of the termination. If you want to completely repeat the reorganization, you must reproduce the deleted constraints, or cancel the table renaming. To do this, you can use the Resetting a Reorganization option in the restart menu (process script con<TSP>.sql or ren<TSP>.sql).

Before the export, no tables were renamed and no constraints were deleted (this means that the database is unchanged in this respect). A restart or a complete repeat of the reorganization is possible.

Errors during processing of one of the scripts after the export script (in the main phase): tables, indexes or tablespaces have already been deleted. In this case you cannot repeat the reorganization. Instead, you must make a restart after fixing the error (or reproduce the initial status manually).

To restart the reorganization process after a termination, you can use the SAPDBA restart function.

To do this, proceed as follows:

Examine the logs as Preparing for the Restart.
Use the SAPDBA menu Restart reorganization to execute the Restart.

Preparing for the Restart

Restart Procedure

Restart File for Reorganizations

Resetting a Reorganization