IBM FileNet P8, Version 5.2

Deleting an object store

Before you begin

You must be a GCD administrator to delete an object store. For more information, see GCD administrator.

About this task

You can delete an object store. Some reasons for doing so include no longer needing the object store and removing a misconfigured object store before attempting to re-create the object store. The following table shows the main component items of an object store and the means by which those items are deleted:

Item	Comment
Global configuration database entries for the object store.	Automatically deleted.
The object store node in the administration console.	Automatically deleted.
Database or table space for the object store.	Manually deleted or manually prepared for reuse. In the latter case, a new object store can optionally use the same database or table space as the deleted object store.
Storage areas that store content for the object store.	Manually deleted.

Attention: Deleting an object store is an irreversible operation.

Procedure

To delete an object store:

Determining the object store data location. Determine the database or table space that is used by the object store. This information is needed for the last step of this procedure. Proceed with this procedure only if you are certain of the data location for the object store.
Find the database schema name in the administration console.
1. In the domain navigation pane, click the object store.
2. In the object store navigation pane, click the name of the object store (the top-most item).
3. In the details pane, click the Properties tab.
4. On the Properties tab, see the value of the Database Schema Name property. This information is needed for the last step of this procedure. The schema name might be unique for the object store.
Stop user activity or any other ongoing activity in the object store.
Delete the following items that are associated with the object store.
1. Delete Image Services mapping prior to deleting the object store. Delete any Image Service-related document class and property mappings.
2. Deleting an isolated region or workflow system. Delete any workflow systems that are associated with the object store.
3. Deleting a file storage area or a fixed storage area. Delete any file storage areas or fixed storage areas for the object store that contain content for that object store only.
Delete the object store in the administration console.
1. In the domain navigation pane, right-click the object store and click Delete.
2. Click Yes when you are prompted to confirm that you want to delete the object store.
3. For future reference, write down the list of shared folders that the wizard displays. These folders contain the storage areas that are still assigned to the object store.
Delete or reuse the database or table space for the object store. To delete the database or table space, see the documentation provided with your database application. For information about reusing the database or table space for another object store, see Preparing an object store database or table space for reuse.

Example

You perform the following subprocedure for step 1 of the previous procedure.

To determine the database or table space that is used by an object store

Find the database connection name in the administration console:
1. In the domain navigation pane, click the object store.
2. In the object store navigation pane, click the name of the object store (the top-most item).
3. In the details pane, click the Properties tab.
4. On the Properties tab, see the value of the Database Connection property. For example, the name of the database connection might be DBConn1.
Find the JDNI data source name in the administration console:
1. In the domain navigation pane, click Global Configuration > Administration > Database Connections.
2. Click the name of the database connection that you found in the previous step. For example, if the database connection name is DBConn1, click DBConn1.
3. In the details pane, click the General tab.
1. On the General tab, see the value of the JNDI data source property. For example, the JNDI data source name might be FNOSDS.
In your application server console, find the data source information for the JNDI data source that you found in the previous step. For example, suppose that the JDNI data source name is FNOSDS. In WebLogic, look at the Java™ Database Connectivity data sources for FNOSDS. The database information is indicated in the URL for the connection pool.
Use the data source information and user authentication information, if necessary, to determine the database or table space that is used by the object store.