Oracle SOA Suite (MOSC)

MOSC Banner

Design Patterns to Recover from Oracle SOA Database Failure?

edited Apr 27, 2017 5:00AM in Oracle SOA Suite (MOSC) 5 commentsAnswered

Hi,

We had a very peculiar case last week in our Production SOA Env (SOA 12.1.3), our database ASM disks ran out of space and DBAs missed alerts to increase the same resulting into tablespace full errors. What we noticed on SOA BPEL front is transactions were kicked off, but we just had the Flow ID, Composite Name and basic header details in RUNNING state, rest of the stuff could not be inserted due to tablespace full errors.

We knew we lost all the transactions, so we were wondering for future is there a better design pattern to recover from this scenario? I know running out of disk space is the most silly thing of all the possible major issues, still trying to see folks have dealt with such situation earlier and come up with a better design pattern, especially in case of where the SOA Layer DB runs of space or DB errors?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center