Restart File for Reorganizations 

Name of a restart file: <ORACLE_HOME>/sapreorg/<timestamp>/restart.<ext>

Function ID <ext> : Indicates the SAPDBA function for which the corresponding scripts were written to the file.

List of possible function IDs during a reorganization

rsi

Reorganization of single tables or indexes

rli

Reorganization of a list of tables or indexes

rtc

Reorganization of tablespaces

rtd

Reorganization of tablespaces with data files

rmv

Change the data file allocation for a tablespace (move/rename data files of a tablespace)

 

These values are identical with the extension of the corresponding log, <ORACLE_HOME>/sapreorg/<timestamp>.<ext> .

The restart file contains the scripts required for performing the corresponding reorganization - that is, a subset of the following scripts:

alt<TSP>.sql , drc<TSP>.sql , exp<TSP>.sh , exc<TSP>.sh, unl<TSP>.sh , swi<TSP>.sql , dro<TSP>.sql , del<TSP>.sh, ren<TSP>.sql , tsp<TSP>.sql , tab<TSP>.sql , imc<TSP>.sh , imp<TSP>.sh, ldr<TSP>.sh , ind<TSP>.sql , imx<TSP>.sh, inx<TSP>.sql, con<TSP>.sql , grants.sql

For a complete overview of the scripts that are written and used by SAPDBA, please refer to SAPDBA Scripts and Files. Also note the changes to the scripts when you are using the tools SAP unload/SAP load or SAP unload/SQL*Loader (see SAP Unload/Load, SQL*Loader).

See also: Reorganization of a Single Object, Reorganization of a List of Objects, Reorganization of a Tablespace, Reorganization of a Tablespace with Data Files and Moving/Renaming the Data Files of a Tablespace.

Script Indicators

When a reorganization is started, the scripts in the restart file are processed in sequence. The indicator before each script indicates whether it was successfully processed or not.

The following indicators are possible:

Y

Script processed successfully.

N

Script either not yet processed or failed. Before a reorganization is started, all scripts have this indicator.

S

The data import (import or loader script) has already been started but SAPDBA could not process the import script properly due to an external error (e.g. import interrupted by user or power failure). SAPDBA terminated. Scripts indicated with S will automatically be newly processed in the event of a restart.

When using SAP unload/load or ORACLE SQL*Loader the same indicators also appear in the parameter file ldr<TSP>.par .

During a reorganization, all the scripts indicated with N are processed, and are changed to Y once the respective operation has been completed (exceptions are the scripts: imp<TSP>.sh, ldr<TSP>.sh : N ® S ® Y, in error condition N ® S ® N).

If the import did not run correctly the indicator of the corresponding script remains S. When restarting the reorganization in this case the contents of all the tables which were already imported are deleted, the indicator is reset to N and the script imp<TSP>.sh is processed again. SAPDBA deletes the contents of tables found in the script exp<TSP>.par (with the ORACLE command TRUNCATE).
If several export dump files are generated during export/import, SAP Unload/Load, SQL*Loader SAPDBA only deletes the contents of the tables found in script exp<TSP>_<n>.par of the canceled import process ( imp<TSP>_<n>.sh ).

During a loader restart only the data in the table where the interruption occurred is deleted. During loading every table is marked with a restart indicator (‘S’) in the parameter file ldr<TSP>.par.

See also

"Entries in Export dump destination - Script Names" in SAPDBA Scripts and Files).

Never change the sequence of scripts that appears in the restart file! It determines the flow of the corresponding reorganization.