To organize isolated regions in table spaces, you must
first define the separate table spaces in the database, specify
the table spaces for the region in the administration console, and
move the existing isolated region data into those table spaces.
Procedure
- Before you run rdbConvertReg, ensure that the table space
in use is not shared, by selecting the isolated region in the
administration console:
Option |
Description |
For a workflow system: |
- In the domain navigation tree, click the object store.
- In the object store navigation tree, select the folder.
- Click the Isolated Regions tab.
- Click the isolated region to open it.
- Click the Table Spaces tab to view the
table spaces that are in use. If the table space in use is
shared, do not use it. Instead, create a new table space.
|
For a legacy workflow system: |
- In the domain navigation tree, click the Legacy Workflow
Systems folder.
- Select the workflow system in the tree.
- Click the Legacy Isolated Regions tab.
- Click the isolated region to open it.
- Click the Table Spaces tab
|
In the lower part of the page, there is a section for Custom
Table Space Associations.If the Restrict
the isolated region to only these custom table spaces is
checked, the table spaces are already restricted.
- Use vwtool to run the rdbConvertReg command
to verify that all of the RDB objects for the region are in the
correct table spaces. Use the l option, which will list
all the tables and their locations.
- Use the database tools to create one or more new table
spaces for the existing region, according to your database. Grant
table space privileges to the workflow system runtime user (such
as, f_sw). For example, for Region 100, create reg100data.
- If Case Analyzer is configured for the
workflow system, use the Take Offline action
in Case Analyzer Process Task Manager to take the Case Analyzer
store offline.
- In the administration console, specify one or more custom
table spaces for the region. See Step 1, the step about Custom Table Space
Associations. After you specify the new region information, ensure
that you apply your changes. When the changes are applied, verify
that the table space information is correct for the existing
region. The table spaces listed should include the original table
spaces along with the new table spaces.
- In the Actions menu in the General
tab for the isolated region, click Lock Isolated
Region to lock the isolated region.
- Purge as many log entries as possible before you run rdbConvertReg
so that when you move existing data, you do not have to move all of
the records. For more information, see Purge data from the event
log tab.
- In vwtool, use the rdbConvertReg command
to display a list of the current table and index names, the current
locations, and the location where the data will be moved.
- Lock the region. For the remaining steps in
this procedure, the region should remain locked and unavailable
for use until verification passes. Use the rdbConvertReg command
to lock the region. At the prompt, enter the c (convert)
option. For a hardcopy, choose Yes to save a file of the manifest.
At the prompt, choose Yes to confirm that you want to convert
the region. The region data will not be converted until you move all
of the data into the correct table spaces.
- Use the database tools to move the data to the new table
spaces, as specified in the manifest.
- After you complete moving the data, run vwtool and enter rdbConvertReg
with the c option again. The command
verifies that the workflow system region tables and indexes were
moved from the current database table spaces to the new region-defined
table spaces.
- Unlock the region.
- Use the Bring Online action
in the Case Analyzer Process Task Manager to bring the Case Analyzer
store online.
- In the Custom Table Space Associations section, of the
isolated region page, select the Restrict the isolated
region to only these custom table spaces check box.
- Optional: After the conversion process, existing
database views are still usable. Because the tables are moved
to another location in the database, the database views are not affected.
To re-create the database views, complete the following steps:
- In vwtool, set the correct region, and then use the createDBViews command
to re-create the database views.
- Select either the v or s options.
The v option automatically creates the views
and the s option creates a script that you
can run manually from the RDBMS database.