Recreate Database


You can recreate the database, that is, set up the SYSTEM tablespace. Logically this means that the SYSTEM tablespace is reorganized. The UNDO and TEMP tablespaces are also recreated. However, SAP data is unaffected. Only the metadata of SAP tablespaces are exported and imported.

You can recreate the database to:

·        Migrate the SYSTEM tablespace from dictionary to locally managed tablespaces (LMTS)

·        Defragment the SYSTEM tablespace

·        Solve the extent problem in the SYSTEM tablespace – for more information, see SAP Note 651796

This section describes how to approach recreate database.

For more information on how to perform recreate database, see Recreating a Database with BR*Tools.


The prerequisites are described in Recreating a Database with BR*Tools.


The following graphic shows how recreate database works:



       1.      Specify new database options.

You define the following database options:

Ў        Passwords for SYS and SYSTEM users

Ў        Maximum number of instances

Ў        Maximum number of datafiles

Ў        Maximum number of redo log groups

Ў        Maximum number of redo log members in a group

Ў        Maximum size of redo log history

Ў        Attributes for files of SYSTEM, SYSAUX, temporary and undo tablespaces

Ў        Attributes for files of original and mirror online redo logs

       2.      Export user tablespaces phase.

BRSPACE exports the metadata – that is, database object definitions – of all user tablespaces using the transportable feature of the Oracle EXP tool. This logically detaches the user tablespaces from the original database.

       3.      Export global objects phase.

BRSPACE exports global object definitions – such as users, roles, links, sequences, synonyms, views, procedures, triggers, and so on ­– using the full export feature of the Oracle EXP tool.

       4.      Create new database phase.

BRSPACE drops the old database and recreates a new one based on the options you specified. Oracle catalog views and stored procedures are also recreated, as described in the Oracle documentation.

       5.      Import global objects phase.

BRSPACE imports global object definitions previously exported using the full import feature of the Oracle IMP tool.

       6.      Import user tablespaces phase.

BRSPACE imports the metadata of all user tablespaces exported before using the transportable tablespace feature of the Oracle IMP tool. Therefore, the user tablespaces are logically reattached to the new database.