If tables were renamed before the reorganization (see the HideTab option in the SAPDBA: Reorganization Menu) and/or constraints were deleted (only during export to tape), resetting will cancel these actions. (SAPDBA deletes primary and unique keys before the export.) All the con<TSP>sql and ren<TSP>.sql scripts are edited automatically during a reset. The database objects are set back to the state they had before the reorganization. You must check whether all the scripts were executed correctly using the logs and the restart plan.

Resetting a reorganization is usually only worthwhile when you do not want to carry out a restart of the same reorganization afterwards. If, despite this, you still want to implement a restart (after the reset), then before the restart you must manually set back all the ‘Y’ status indicators to ‘N’ in the restart plan.

It is not possible to reset if tables, indexes or the tablespace were already deleted after a successful export. The reorganization has to be followed by a restart once the error has been corrected.

See: Restarting a Reorganization.