Separating isolated region data into a custom table space
See Isolated region recovery overview for general information.
The following diagram shows high-level examples of how you can separate isolated region data into custom table spaces.
Default configuration - All of the Process Engine data for the isolated regions are in the default table spaces.
Custom table space - The database administrator has created a custom table space (TS1), and moved Region 1 tables from the default table space into TS1. You might use this configuration to put the indexes or queues for a region in their own table space to improve performance. For more information, see Advanced table space settings.
Note that the database administrator can move some of the data for a particular region (in this case, Region 1), but some system data for Region 1 are still in the Process Engine default table spaces.
Recovery enabled - The database administrator has created one or more custom table spaces (TS1) and moved all of the data (data, indexes, and so on) for Region 1 into those table spaces. In addition, the Process Engine administrator has specified that region as 'Enabled for region recovery'. This moves all of the Process Engine system data (timeout, e-mail notification, and so on) for Region 1 into the custom table spaces, making it possible to backup, rollback, and recover the data for Region 1 independent of other regions. This is possible only when the region does not share table spaces with any other region. For information on creating a custom table space and enabling it for recovery, see Regions.