My Oracle Support Banner

Deadlocks in BPEL when Using Microsoft MSSQLServer as the Dehydration Database (Doc ID 881666.1)

Last updated on AUGUST 13, 2019

Applies to:

Oracle(R) BPEL Process Manager 10g - Version to [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 26-Apr-2011***


There are locks on the BPEL dehydration database which is running on MSSQL Server 2005 for the V4 of the BPEL DB scripts. These locks were seen when BPEL traffic increased.

In the log file the following exception is seen:

09/07/27 11:21:00 0 - ORABPEL-04025

Cannot decode properties.
The process domain was unable to decode the properties for message guid 10,
which are stored in column Cannot deserialize DOM element.
Failed to deserialize the DOM element from binary format, the document id
. The exception reported is Cannot
fetch document.
The process domain was unable to fetch the document
 from the datastore. The
exception reported is: Transaction (Process ID 106) was deadlocked on lock
resources with another process and has been chosen as the deadlock victim.
Rerun the transaction.
Please check that the machine hosting the datasource is physically connected
to the network. Otherwise, check that the datasource connection parameters
(user/password) is currently valid.
sql statement: SELECT dockey, bin_csize, bin_usize, bin_format, bin FROM
xml_document WHERE dockey = ?

; the exception reported is: {2}
sql statement: SELECT conv_id, message_guid, domain_ref, process_id,
revision_tag, operation_name, receive_date, state, priority, properties,
master_conv_id, headers_ref_id FROM invoke_message WHERE message_guid = ?


To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.