Separating isolated region data into a custom tablespace
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 tablespaces.
Default configuration - All of the Process Engine (PE) data for the isolated regions are in the default tablespaces.
Custom tablespace - The database administrator has created a custom tablespace (TS1), and moved Region 1 tables from the default tablespace into TS1. You might use this configuration to put the indexes or queues for a region in their own tablespace to improve performance. For more information, see Advanced Tablespace 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 PE default tablespaces.
Recovery enabled - The database administrator has created one or more custom tablespaces (TS1) and moved all of the data (data, indexes, and so on) for Region 1 into those tablespaces. In addition, the PE administrator has specified that region as 'Enabled for region recovery'. This moves all of the PE system data (timeout, email notification, and so on) for Region 1 into the custom tablespaces, 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 tablespaces with any other region. For information on creating a custom tablespace and enabling it for recovery, see Regions.