Central Dehydration Store

Hi I have a simple question (I hope)
As of SOA Suite 11g is it now possible to use one database with multiple dehydration stores?
The example is:
I have to developers on seperate machines both with JDeveloper 11g WLS and SOA Suite 11g components installed the dehydration store that each developers SOA Suite component would point to the same database. Is this possible?
Thanks in advance

Hi Saheem,
I have one Oracle instance with 2 x SOA 11g dehydration store: one using prefix DEVA (DEVA_SOAINFRA, DEVA_MDS) and one using prefix DEVB (DEVB_SOAINFRA, DEVB_SOAINFRA).
I have 2 types of developers: one set with SOA suite components setup for DB Schema prefixed DEVA and one with SOA components setup for DB Schema prefixed DEVB.
I evane have in same oracle instance a 10g dehydration (with orabpel, oraesb schema) as we still maintain 10g apps.
Hope this helps.
JP

Similar Messages

Where the task payload is stored in the dehydration store

Hi All,
I wanted to get the taskPayload from the BPEL dehydration store. I have gone thru the WFTASK table but I didn't see any column which conains the taskpaylod.
I need this payload to do the following..
- Get the taskPayload
- Modify it so that I can get modifications in the BPEL process when I submitted the task back to BPEL.
Can the above be done from the bpel dehydration store? If yes please help me in finding the exact table for this task payload.
If not guide me how can I access and modify the task payload.
Thank you.

Payloads are generally stored as BLOBS. Here is a definition of all the tables. You can make the payload editable withing the human task if required, so you don't need to go to the DB.
Main tables used by the BPEL engine
cube_instance – stores instance metadata, eg. instance creation date, current state, title, process identifier
cube_scope – stores the scope data for an instance … all the variables declared in the bpel flow are stored here, as well as some internal objects to help route logic throughout the flow.
work_item – stores activities created by an instance … all BPEL activities in a flow will have a work_item created for it. This work item row contains meta data for the activity … current state, label, expiration date (used by wait activities) … when the engine needs to be restarted and instances recovered, pending flows are resumed by inspecting their unfinished work items.
document - stores large XML variables. If a variable gets to be larger than a specific size (configurable via the largeDocumentThreshold property via the domain configuration page) then the variable is stored in this table to alleviate loading/saving time from the cube_scope table.
audit_trail - stores the audit trail for instances. The audit trail viewed from the console is modelled from an XML document. As the instance is worked on, each activity writes out events to the audit trail as XML which is compressed and stored in a raw column. Querying the audit trail via the API/console will join the raw columns together and uncompress the contents into a single XML document.
audit_details - audit details can be logged via the api … by default activities such as assign log the variables as audit details (this behavior can be set via the auditLevel property on the domain configuration page). Details are separated from the audit trail because they tend to be very large in size … if the user wishes to view a detail they click a link from the audit trail page and load the detail separately. There is a threshold value for details too … if the size of a detail is larger than a specific value (see auditDetailThreshold) then it is place in this table, otherwise it is merged into the audit trail row.
dlv_message – callback messages are stored here. All non-invocation messages are saved here upon receipt. The delivery layer will then attempt to correlate the message with the receiving instance. This table only stores the metadata for a message. (eg. current state, process identifier, receive date).
dlv_message_bin – stores the payload of a callback message. The metadata of a callback message is kept in the dlv_message table, this table only stores the payload as a blob. This separation allows the metadata to change frequently without being impacted by the size of the payload (which is stored here and never modified).
dlv_subscription – stores delivery subscriptions for an instance. Whenever an instance expects a message from a partner (eg. receive, onMessage) a subscription is written out for that specific receive activity. Once a delivery message is received the delivery layer attempts to correlate the message with the intended subscription.
invoke_message – stores invocation messages, messages which will result in the creation of a instance. This table only stores the metadata for an invocation message (eg. current state, process identifier, receive date).
invoke_message_bin – stores the payload of an invocation message. Serves the same purpose the dlv_message_bin table does for dlv_message.
task – stores tasks created for an instance. The TaskManager process keeps its current state in this table. Upon calling invoking the TaskManager process, a task object is created, with a title, assignee, status, expiration date, etc… When updates are made to the TaskManager instance via the console the underlying task object in the db is changed.
schema_md – (just added via patch delivered to Veerle) contains metadata about columns defined in the orabpel schema. Use case driving this feature was how to change the size of a custom_key column for a cube_instance row? Changing the db schema was simple but the engine code assumed a certain length and truncated values to match that length to avoid a db error being thrown. Now, column lengths are defined in this table instead of being specified in the code. To change a column length, change the column definition in the table, then change the value specified in this table, then restart the server.
Column-by-column description:
table ci_id_range
- next_range (integer) – instance ids in the system are allocated on a block basis … once all the ids from a block have been allocated, another block is fetched, next_range specifies the start of the next block.
table cube_instance
- cikey (integer) – primary key … foreign key for other tables
- domain_ref (smallint) – domain identifier is encoded as a integer to save space, can be resolved by joining with domain.domain_ref.
- process_id (varchar) – process id
- revision_tag (varchar) – revision tag
- creation_date (date)
- creator (varchar) – user who created instance … currently not used
- modify_date (date) – date instance was last modified
- modifier (varchar) – user who last modified instance … currently not used
- state (integer) – current state of instance, see com.oracle.bpel.client.IInstanceConstants for values
- priority (integer) – current instance priority (user specified, has no impact on engine)
- title (varchar) – current instance title (user specified, no engine impact)
- status (varchar) – current status (user specified)
- stage (varchar) – current stage (user specified)
- conversation_id (varchar) – extra identifier associated with instance, eg. if passed in via WS-Addressing or user specified custom key.
- root_id (varchar) – the conversation id of the instance at the top of the invocation tree. Suppose A -> B -> C, root( B ) = A, root( C ) = A, parent( B ) = A, parent( C ) = B. This instance, instance at the top of the tree will not have this set.
- parent_id (varchar) – the conversation id of the parent instance that created this instance, instance at the top of the tree will not have this set.
- scope_revision (integer) – internal checksum of scope bytes … used to keep caches in sync
- scope_csize (integer) – compressed size of instance scope in bytes
- scope_usize (integer) – uncompressed size of instance scope in bytes
- process_guid (varchar) – unique identifier for the process this instance belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
- process_type (integer) – internal
- metadata (varchar) – user specified
table cube_scope
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- modify_date (date) – date scope last modified
- scope_bin (blob) – scope bytes
table work_item
- cikey (integer) – foreign key
- node_id (varchar) – part of work item composite key, identifier for bpel activity that this work item created for
- scope_id (varchar) – part of work item composite key, identifier for internal scope that this work item created for (note this is not the scope declared in bpel, the engine has an internal scope tree that it creates for each instance, bpel scopes will map to an internal scope but there will be other internal scopes that have no mapping to the bpel definition).
- count_id (integer) – part of work item composite key, used to distinguish between work items created from same activity in the same scope.
- domain_ref (integer) – domain identifier
- creation_date (date)
- creator (varchar) – user who created work item … currently not used
- modify_date (date) – date work item was last modified
- modifier (varchar) – user who last modified work item … currently not used
- state (integer) – current state of work item, see com.oracle.bpel.client.IActivityConstants for values
- transition (integer) – internal use, used by engine for routing logic
- exception (integer) – no longer used
- exp_date (date) – expiration date for this work item; wait, onAlarm activities are implemented as expiration timers.
- exp_flag (integer) – set if a work item has been called back by the expiration agent (ie. expired).
- priority (integer) – priority of work item, user specified, no engine impact
- label (varchar) – current label (user specified, no engine impact)
- custom_id (varchar) – custom identifier (user specified, no engine impact)
- comments (varchar) – comment field (user specified, no engine impact)
- reference_id (varchar) -
- idempotent_flag (integer) – internal use
- process_guid (varchar) – unique identifier for the process this work item belongs to … if changes need to be made for all instances of a process, this column is used to query (eg. stale process).
table document
- dockey (varchar) – primary key for document
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- classname (varchar) – no longer used
- bin_csize (integer) – compressed size of document in bytes
- bin_usize (integer) – uncompressed size of document in bytes
- bin (blob) – document bytes
- modify_date (date) – date document was last modified
table audit_trail
- cikey (integer) – foreign key
- domain_ref – domain identifier
- count_id (integer) – many audit trail entries may be made for each instance, this column is incremented for each entry per instance.
- block (integer) – when the instance is dehydrated, the batched audit trail entries up to that point are written out … this block ties together all rows written out at one time.
- block_csize (integer) – compressed size of block in bytes
- block_usize (integer) – uncompressed size of block in bytes
- log (raw) – block bytes
table audit_details
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- detail_id (integer) – part of composite key, means of identifying particular detail from the audit trail
- bin_csize (integer) – compressed size of detail in bytes
- bin_usize (integer) – uncompressed size of detail in bytes
- bin (blob) – detail bytes
table dlv_message
- conv_id (varchar) – conversation id (correlation id) for the message…this value is used to correlate the message to the subscription.
- conv_type (integer) – internal use
- message_guid (varchar) – unique identifier for the message…each message received by the engine is tagged with a message guid.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – identifier for process revision
- operation_name (varchar) – operation name for callback port.
- receive_date (date) – date message was received by engine
- state (integer) – current state of message … see com.oracle.bpel.client.IDeliveryConstants for values
- res_process_guid (varchar) – after the matching subscription is found, the process guid for the subscription is written out here. – res_subscriber (varchar) – identifier for matching subscription once found.
table dlv_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of delivery message payload in bytes
- bin_usize (integer) – uncompressed size of delivery message payload in bytes
- bin (blob) – delivery message payload
table dlv_subscription
- conv_id (varchar) – conversation id for subscription, used to help correlate received delivery messages.
- conv_type (integer) – internal use
- cikey (integer) – foreign key
- domain_ref (integer) – domain identifier
- process_id (varchar) – process identifier for instance
- revision_tag (varchar) – revision tag for process
- process_guid (varchar) – guid for process this subscription belongs to
- operation_name (varchar) – operation name for subscription (receive, onMessage operation name).
- subscriber_id (varchar) – the work item composite key that this subscription is positioned at (ie. the key for the receive, onMessage work item).
- service_name (varchar) – internal use
- subscription_date (date) – date subscription was created
- state (integer) – current state of subscription … see com.oracle.bpel.client.IDeliveryConstants for values
- properties (varchar) – additional property settings for subscription
table invoke_message
- conv_id (varchar) – conversation id for message, passed into system so callbacks can correlate properly.
- message_guid (varchar) – unique identifier for message, generated when invocation message is received by engine.
- domain_ref (integer) – domain identifier
- process_id (varchar) – identifier for process to deliver the message to
- revision_tag (varchar) – revision tag for process
- operation_name (varchar) – operation name for receive activity
- receive_date (date) – date invocation message was received by engine
- state – current state of invocation message, see com.oracle.bpel.client.IDeliveryConstants for values
- priority (integer) – priority for invocation message, this value will be used by the engine dispatching layer to rank messages according to importance … lower values mean higher priority … messages with higher priority are dispatched to threads faster than messages with lower values.
- properties (varchar) – additional property settings for message
table invoke_message_bin
- message_guid (varchar) – unique identifier for message
- domain_ref (integer) – domain identifier
- bin_csize (integer) – compressed size of invocation message payload in bytes
- bin_usize (integer) – uncompressed size of invocation message payload in bytes
- bin (blob) – invocation message bytes
table task
- domain_ref (integer) – domain identifier
- conversation_id (varchar) – conversation id for task instance … allows task instance to callback to client
- title (varchar) – current title for task, user specified
- creation_date (date) – date task was created
- creator (varchar) – user who created task
- modify_date (date) – date task was last modified
- modifier (varchar) – user who last modified task
- assignee (varchar) – current assignee of task, user specified, no engine impact
- status (varchar) – current status, user specified, no engine impact
- expired (integer) – flag is set if task has expired
- exp_date (date) – expiration date for task, expiration actually takes place on work item in TaskManaged instance, upon expiration task row is updated
- priority (integer) – current task priority, user specified, no engine impact
- template (varchar) – not used
- custom_key (varchar) – user specified custom key
- conclusion (varchar) – user specified conclusion, no engine impact

SOA Suite 10.1.3.1 GA dehydration store

Since I haven't received a response on the oc4j-ra.xml configuration question, I decided to reinstall and specify an existing database to use as the dehydration store, effectively forcing myself off of my 10.1.2.0.2 installation. There is a catch 22 here though (surprise!). Installation insists on versions 10.2.0.2 or better, or 10.1.0.5 or better. Well, where are these databases available on a Windows platform? I don't see them in the db download area. I have confirmed that 10.2.0.2 doesn't work as well as 10.2.0.1.
Overall, I'm not having much success with 10.1.3.1 with dehydration, workflow/worklist and notification problems.

I don't know when this started or if it has always been this way. My worklist based notifications are being transmitted with the appropriate sender and title but the content remains encapsulated in html and comes in two separate pieces, Message and Content. The message looks like:
<br><br>
<html> <body> Task john junk requires your attention. Please access the task from the worklist application.<p><TABLE border="0"><TR><TD>Action Links: </TD><TD>Worklist Application</TD></TR></TABLE></body></html>
<br><br>
The email is not set to actionable as the content of this html structure would lead you to believe. Also the html tags are actually confusing the browser display as well. In the actual email text it is completely cancatenated together.
Normal notifications work as expected with only the text being sent through the SMTP server and displayed by the mail client.

Is there any way we can stop dehydration store

Hi All,
Is there anyway we can stop dehydration store in the BPEL,i have two BPEL process deployed in the SOA Suite.i want to make sure that one BPEL should not get impacted by dehydrations Store.
Please share your views.
Thanks,
Murali.

Check in System Preferences > Mission Control > Show Desktop: > Make sure the right column is set to "-" and not secondary mouse button.

Extracting payloads from Dehydration Store

Is it possible to write SQL against the dehydration store to extract the payloads being received into a process?
A quick look at the database appears to show they are stored as BLOB.
Pete

You might find some usefull info on this thread :
Re: Format of AUDIT_DETAILS.BIN?
Regard,
Rob

How to manage a SOA Dehydration Store (SOAINFRA)?

Good Day!
How its possible to know - how big is an oracle SOAINFRA, a dehydration store schema now?
And is there any tools for it managing?

Yes - there are purge scripts that you can use to delete instances
Please see this doc
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10226/soaadmin_partition.htm#CJHDHHGB

How to view Dehydration Store Performance in OEM 12c Cloud Control

Hi All,
I have installed OEM 12c Cloud Control.I want to view dehydration store performance for my fusion middleware domain.Can anyone please suggest me how can I achieve this?
I have added the database, where soa schemas are created, as a monitored target in OEM 12c Cloud Control. Also have added Fusion middleware domain for which I want to view dehydration store management.
Thanks in Advance!!
Edited by: Roshni Shankar on Sep 19, 2012 5:26 AM

You should open an SR and support can assist you with it. The only current case where that feature is known to not work is in the case where the Dehydration Store is running on RAC. Otherwise, it should be possible to get it to work. The main thing is that you need to have DB configuration properties (host, port, sid) that have a 3-way string match between the JDBC data source configuration in the WLS server, the JDBC properties you add to the Monitoring Properties of the SOA Infrastructure target, and the connect settings of the Database target in EM that matches to the dehydration DB.
If there isn't a match in all 3, the Dehydration Diagnostics page will not work. But again, to look into your specific setup, you should file an SR and work with support.

Moved dehydration Store to Oracle 10g DB

Hi... I'd like to make sure that this error in starting up the BPEL PM ( version 2.2 ) is OK after moving the dehydration store to an Oracle 10g database. I loaded the LoanFlow Demo and it seems to run fine.
Thanks, Matt
###Details###
ORABPEL Schema objects in 10g Database
TABLE_NAME TABLE_TYPE
ADMIN_LIST_CI VIEW
ADMIN_LIST_CX VIEW
ADMIN_LIST_WI VIEW
AUDIT_DETAILS TABLE
AUDIT_TRAIL TABLE
CI_ID_RANGE TABLE
CI_INDEXES TABLE
CUBE_INSTANCE TABLE
CUBE_SCOPE TABLE
DBG_WI VIEW
DLV_MESSAGE TABLE
DLV_MESSAGE_BIN TABLE
DLV_SUBSCRIPTION TABLE
DOCUMENT TABLE
DOMAIN TABLE
INVOKE_MESSAGE TABLE
INVOKE_MESSAGE_BIN TABLE
LOAN_CUSTOMER TABLE
NAMESPACE TABLE
PROCESS_REVISION TABLE
SCOPE_ACTIVATION TABLE
SYNC_STORE TABLE
SYNC_TRAIL TABLE
TASK TABLE
TX_INFERIOR TABLE
TX_MESSAGE TABLE
TX_SUPERIOR TABLE
VERSION TABLE
VERSION_SERVER TABLE
WI_EXCEPTION TABLE
WORK_ITEM TABLE
WORK_LIST VIEW
Database Connections after BPEL PM is started....
USERNAME
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
ORABPEL
20 rows selected.
Portion of BPEL PM startup output....
05/02/17 16:02:23 Building Application TagLibrary Persistent Cache for owf
05/02/17 16:02:23 Done getting application current resources
05/02/17 16:02:23 Done initializing cache
05/02/17 16:02:23 Refreshing application cache - from existing cache ...
05/02/17 16:02:24 Found 0 listeners
05/02/17 16:02:24 java.sql.SQLException: ORA-00942: table or view does not exist
05/02/17 16:02:24 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
05/02/17 16:02:24 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
05/02/17 16:02:24 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
05/02/17 16:02:24 at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
05/02/17 16:02:24 at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
05/02/17 16:02:24 at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:661)
05/02/17 16:02:24 at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:951)
05/02/17 16:02:24 at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:693)
05/02/17 16:02:24 at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1057)
05/02/17 16:02:24 at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901)
05/02/17 16:02:24 at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2942)
05/02/17 16:02:24 at oracle.tip.pc.services.owf.BridgeDBWrapper.getOWFProcesses(BridgeDBWrapper.java:159)
05/02/17 16:02:24 at oracle.tip.pc.services.owf.callback.OWFMonitorServlet.init(OWFMonitorServlet.java:46)
05/02/17 16:02:24 at com.evermind.server.http.HttpApplication.loadServlet(HttpApplication.java:2141)
05/02/17 16:02:24 at com.evermind.server.http.HttpApplication.findServlet(HttpApplication.java:4582)
05/02/17 16:02:24 at com.evermind.server.http.HttpApplication.initPreloadServlets(HttpApplication.java:4676)
05/02/17 16:02:24 at com.evermind.server.http.HttpApplication.initDynamic(HttpApplication.java:820)
05/02/17 16:02:24 at com.evermind.server.http.HttpApplication.<init>(HttpApplication.java:542)
05/02/17 16:02:24 at com.evermind.server.Application.getHttpApplication(Application.java:889)
05/02/17 16:02:24 at com.evermind.server.http.HttpServer.getHttpApplication(HttpServer.java:690)
05/02/17 16:02:24 at com.evermind.server.http.HttpSite.initApplications(HttpSite.java:586)
05/02/17 16:02:24 at com.evermind.server.http.HttpSite.setConfig(HttpSite.java:263)
05/02/17 16:02:24 at com.evermind.server.http.HttpServer.setSites(HttpServer.java:261)
05/02/17 16:02:24 at com.evermind.server.http.HttpServer.setConfig(HttpServer.java:162)
05/02/17 16:02:24 at com.evermind.server.ApplicationServer.initializeHttp(ApplicationServer.java:2385)
05/02/17 16:02:24 at com.evermind.server.ApplicationServer.setConfig(ApplicationServer.java:1542)
05/02/17 16:02:24 at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:92)
05/02/17 16:02:24 at java.lang.Thread.run(Thread.java:534)
05/02/17 16:02:24 Oracle Application Server Containers for J2EE 10g (10.1.2.0.0)
initialized
<ServerManager::loadProcesses> Loading processes for all domains
<2005-02-17 16:02:25,512> <INFO> <default.collaxa.cube.engine> <CubeEngine::load
AllProcesses>
Loading processes for BPEL domain "default" ...
...

Matt, it seems like you are running the JDev Based Beta with the new workflow extensions. You should get the Technotes from the person that you supplied you the beta version.
Anyway, to install the additional tables, please run
pcttask.sql, pcowf.sql, catpcreports.sql using sql*plus into the right schema. You will find these files in <home>\integration\bpm\runtime\admin\sql
Sandor

How to enabling Monitoring of the SOA Dehydration Store

Hi All,
I am new to the Oracle Enterprise Manger 12c cloud control i have installed the OEM 12c in linux, configured the SOA agent to monitor the SOA composites its working fine.
can you please let me know how to setup the dehydration store for the SOA-Infrastructure. when i am trying click dehydration from the console its showing following error
(Failed connecting to SOA repository. The possible reason can be the dehydration store database target is not monitored using Enterprise Manager or the credentials required for monitoring are not set. Check the required details and try again)
Let me know is there configurations i need to do manually if required ? where i can do please tell me.
I installed the database agent also.
Thanks--laks

You can provide feedback here > Apple - Feedback

Multiple use of Dehydration Store Instance?

This may seem like a stupid question, but we just brought up our second App Server instance pointing to the same Dehydration store instance. It appears to be working, but we have only installed one process for the second BPEL instance. Can two instances of the BPEL manager on separate App server instances use the same dehydration store instance?

you may be able to do this with BPEL but you cannot do this with ESB as it will have conflicting issue with the JMS queues, you can't even use different schemas within the same dehydration database with the ESB dehydration store. This is because it uses global queues.
Obviously in a cluster the dehydration store must be shared between app servers. This post is only refering to 2 separate installs of SOA Suite using the same dehydration store.
cheers
James

How to logging off the assign activity to dehydration store

As per my understanding , every bpel process, logs data from assign activity in dehydration store. I changed the setting auditLevel to production to for logging off the assign activity.
But it didnt work I guess. Even I tried to query audit_details & audit_trail tables by instance id.
But didnt get the record that I got. Can we get variables stored ?
Please help me in logging off assign activity to dehydration store which is default behaviour. And also how to cross check it.
Thanks in advance.

Look here:
http://download.oracle.com/docs/cd/B31017_01/core.1013/b28942/tuning_bpel.htm#CIHEFIFH
Use the
"completionPersistPolicy BPEL Property"
"inMemoryOptimization BPEL Property"
In your BPEL process.
Marc

Anybody using MS SQL Server 2005 as dehydration store?

anybody using MS SQL Server 2005 as dehydration store?
Please give me a reply.
I am facing lot of issues with this.
Thanks
V Kumar
Edited by: user640551 on Oct 15, 2008 3:58 AM
Edited by: user640551 on Oct 16, 2008 2:38 AM
Edited by: user640551 on Oct 16, 2008 8:07 AM

I have raised an SR. I have provided them with error code,screen shots and log files.
They are suggesting me to do a fresh install of SOA. But I feel that is not the correct solution.
Now I can do that as i have only two processes running on the server.
Imagine If I have lof of processes running on the server. moreover I can't do it every time when i face this kind of errors on the PROD server.
Anyway thanks for your suggestion.
How long you have been working with oracle SOA suite?
Thanks
V Kumar

Anybody using MS SQL Server as dehydration store?

anybody using MS SQL Server 2005 as dehydration store?
Please give me a reply.
I am facing lot of issues with this.
Thanks
V Kumar
Edited by: user640551 on Oct 15, 2008 5:51 AM

I have raised an SR. I have provided them with error code,screen shots and log files.
They are suggesting me to do a fresh install of SOA. But I feel that is not the correct solution.
Now I can do that as i have only two processes running on the server.
Imagine If I have lof of processes running on the server. moreover I can't do it every time when i face this kind of errors on the PROD server.
Anyway thanks for your suggestion.
How long you have been working with oracle SOA suite?
Thanks
V Kumar

High CPU on BPEL Manager until Dehydration store purged

We are seeing that if we get run-time exceptions while running BPEL processes we will have high CPU on the system until we shut down the BPEL instance, purge the dehydration store, and restart the instance. If we shut the instance down and restart the instance without the purge we are getting seriously high CPU usage, the only cure being the purge. Any help or thoughts appreciated.
Art

When the SYSTEM process uses high cpu, it typically means there is an IO issue. Open up process explorer from sysinternals to see what thread on the SYSTEM process is using the CPU. Typically this is caused by slow disk or antivirus getting in the
way. You could temporarily disable the antivirus real scan to see if the issue clears up. If the issue clears up you should verify if the recommended antivirus exclusions are in place.

BPEL PM Dehydration Store

Hi All,
I could not find guide to setup Oracle DB as dehydration store for BPEL PM .
There is a guide for setting up SQL Server as dehydration store.
thanks

Is is part of the install guide. Here is a pointer to the install.
http://download.oracle.com/docs/cd/B31017_01/core.1013/b28938/setup.htm#BABGFAAB
cheers
James

Central Dehydration Store

Similar Messages

Maybe you are looking for