During the reorganization of a tablespace with data files, SAPDBA performs - in addition to the import checks (see Freespace Check during Reorganization of a Tablespace) - a file system check. SAPDBA checks whether the selected file system has sufficient freespace for the new files of the tablespace (the first suggestion from SAPDBA is the file system containing file <tablespace name>.data1 of the tablespace).

The check considers the freespace that will be available once the tablespace is deleted.

SAPDBA specifies which directories the new data files for the tablespace will be stored in (file numbering starts again with the suffix "1") and asks whether you want to specify additional paths for the data files. If necessary, you can then specify a path in a file system with more space. Both the available sapdata<n> directories and the possible raw devices can be selected with a list which can be displayed by SAPDBA. In this case, SAPDBA repeats the import check and then performs the reorganization.

If the files are not in a standard SAP directory, SAPDBA proposes the directory <ORACLE_HOME>/sapdata<n>/<tablespace name>_<file number> , which is a symbolic link to the specified directory.

Please adhere to the SAP naming conventions whenever possible (see Naming Convention).

If a raw device should be used for the new data file, SAPDBA automatically generates a symbolic link to the specified raw device in directory sapraw . In most cases SAPDBA suggests the old distribution of the tablespace on the files (since the raw devices have a fixed size). You might have to take manual action to change this suggestion.