Managing Space in the SOA Infrastructure Database

11-2 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 1. Log on to the Oracle WebLogic Administration console. 2. Expand the environment node on the navigation tree.

3. Click on Deployments.

4. Select the driver.

5. Click Stop-When work completes and confirm the operation.

6. Wait for the driver to transition to the Prepared state refresh the administration console page, if required.

7. Select the driver again, and click Start-Servicing all requests and confirm the

operation. Make sure that you verify in Oracle Enterprise Manager Fusion Middleware Control that the properties for the driver have been preserved.

11.3 Managing Space in the SOA Infrastructure Database

Although not all composites may use the database frequently, the service engines generate a considerable amount of data in the CUBE_INSTANCE and MEDIATOR_ INSTANCE schemas. Lack of space in the database may prevent SOA composites from functioning. Watch for generic errors, such as “oracle.fabric.common.FabricInvocationException” in the Oracle Enterprise Manager Fusion Middleware Control console dashboard for instances. Search also in the SOA server’s logs for errors, such as: Error Code: 1691 ... ORA-01691: unable to extend lob segment SOAINFRA.SYS_LOB0000108469C00017 by 128 in tablespace SOAINFRA These messages are typically indicators of space issues in the database that may likely require adding more data files or more space to the existing files. The SOA Database Administrator should determine the extension policy and parameters to be used when adding space. Additionally, old composite instances can be purged to reduce the SOA Infrastructure databases size. Oracle does not recommend using the Oracle Enterprise Manager Fusion Middleware Control for this type of operation as in most cases the operations cause a transaction time out. There are specific packages provided with the Repository Creation Utility to purge instances. For example: DECLARE FILTER INSTANCE_FILTER := INSTANCE_FILTER; MAX_INSTANCES NUMBER; DELETED_INSTANCES NUMBER; PURGE_PARTITIONED_DATA BOOLEAN := TRUE; BEGIN . FILTER.COMPOSITE_PARTITION_NAME:=default; FILTER.COMPOSITE_NAME := FlatStructure; FILTER.COMPOSITE_REVISION := 10.0; FILTER.STATE := fabric. STATE_UNKNOWN; FILTER.MIN_CREATED_DATE := to_timestamp2010-09-07,YYYY-MM-DD; FILTER.MAX_CREATED_DATE := to_timestamp2010-09-08,YYYY-MM-DD; MAX_INSTANCES := 1000; . DELETED_INSTANCES := FABRIC.DELETE_COMPOSITE_INSTANCES FILTER = FILTER, Managing the Topology 11-3 MAX_INSTANCES = MAX_INSTANCES, PURGE_PARTITIONED_DATA = PURGE_PARTITIONED_DATA ; This deletes the first 1000 instances of the FlatStructure composite version 10 created between 2010-09-07 and 2010-09-08 that are in “UNKNOWN” state. Refer to Chapter 8, Managing SOA Composite Applications in the Oracle Fusion Middleware Administrators Guide for Oracle SOA Suite for more details on the possible operations included in the SQL packages provided. Always use the scripts provided for a correct purge. Deleting rows in just the composite_dn table may leave dangling references in other tables used by the Oracle Fusion Middleware SOA Infrastructure.

11.4 Scaling the Topology