SOA Schema Tablespace Growing Rapidly when Processing Large Payload

(Doc ID 1667304.1)

Last updated on MAY 18, 2018

Applies to:

Oracle SOA Suite - Version to [Release 11gR1]
Information in this document applies to any platform.


On : version, B2B Engine

When B2B passes debatched messages from a very large payload containing 1000's of transaction sets to a SOA composite, the schema tablespace grows exponentially.

The SOA schema tablespace should not grow out of control when processing trading partner data in B2B.

The issue can be reproduced at will with the following steps:
1. B2B receives inbound message with a payload containing over 3000 transaction sets.
2. Debatched messages are sent to SOA composite for backend processing.
3. Tablespace grows.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms