Database Reference
In-Depth Information
•
Certain product tables in the Dehydration Store must be partitioned together.
•
Converting your partitioned tables back to non-partitioned ones requires
first executing the
soa_exec_verify.sql
script to determine when to
drop a partition and its equipartitioned dependent table. Refer to the Oracle
Fusion Middleware Administrator's Guide for Oracle SOA Suite 11g and
Oracle
Business
Process
Management
Suite
11g
Release
1
at
ht-
min_partition.htm#CJHFJDII
for more information.
•
Database partitioning is only supported for Oracle SOA Suite
11g
Release 1
(11.1.1.4 or higher).
•
There is no one-size-fits-all strategy to configuring and tuning your partitions.
The steps described in this section are specific to implementing database parti-
tioning on the Oracle SOA Suite
11g
product tables. The approach first involves
identifying which product component(s) to partition. Afterwards, for each com-
ponent, you must identify which tables will be affected and what range partition
keys are to be used. The appropriate tablespaces are then created based on
your environment and performance needs. Finally, the actual activity of partition-
ing the tables is performed.
Identifying components to partition
Each of the following Oracle SOA Suite
11g
components has its own database
schemas. From the following list, begin by choosing one or more components to
partition:
•
SOA Infrastructure
•
Oracle BPEL Process Manager
•
Oracle Mediator
•
Human workflow
•
Oracle BPM Suite
Identifying tables to partition
For the component(s) selected, refer to the following table. Say that you choose
to partition the tables in the SOA Infrastructure. In this case, there will be a total
