You can reuse the database or table space of a deleted
object store for a new object store. Reuse allows you to retain settings
such as next extent size, special user permissions, settings on the
data files and transaction logs, and other customized settings.
To create an object store after following the preparation procedure
in this topic, see Creating
an object store.
Before you prepare a database for reuse, follow these steps:
- Delete the object store that uses the database or table space
before you attempt to reuse the database or table space for another
object store. For information about deleting an object store, see Deleting an object store.
- If a workflow system that shares the same database and schema
is associated with the object store, delete all the connection points
that are associated with the workflow system. The administration console
automatically deletes the associated database constructs for the workflow
system.
Note: Preparing a database or a table space for
reuse is an irreversible operation. The tables dropped as part of
this procedure are permanently deleted. Do not drop tables unless
you are certain that the tables belong to an object store that has been deleted.
In particular, do not drop any table whose name begins with FNGCD
unless you are also deleting a domain. (For more information, see
Deleting a domain.) When
you select tables and sequences to drop, be sure to select only database
constructs that are owned by the schema associated with the deleted
object store.