Database Reference
In-Depth Information
The preceding set of steps are used to provide a working example of how to
partition the Oracle SOA Suite 11g tables. It is recommended to capture basic
metrics before and after you partition the tables to observe the performance
impact and involve an Oracle DBA to fine tune the tablespace characteristics
as needed. Though database partitioning of the Oracle SOA Suite 11g product
tables is an activity that is rarely performed, it does support certain use cases
and may be appropriate for your particular installations.
Reducing audit levels
Another way to maintain database growth is to reduce the audit level for com-
posites by controlling the instance data being written to the Dehydration Store.
We recommend that all production environments should have the audit level set
to Production . This setting should be applied as a standard default for all
domains in production. Depending upon the business requirement each com-
ponent can override the default with its own audit level as needed. Changing
audit level from Development to Production results in significantly less to
and fro interaction with the database and greatly enhances performance. You
can further improve performance by turning Off auditing although this may not
be ideal. Configuration and management of audit levels is covered in detail in
Chapter 2 , Management of SOA Composite Applications.
Search WWH ::




Custom Search