BPEL Process Version 1.0 Is Set As Default Prior To Latest Versions Deployed

-
Oracle(R) BPEL Process Manager - Version: 10.1.3.1

Symptoms
You are deploying version 2.0 of a BPEL Process, and marking this version as default in the BPEL Console. When you call the application version 1.0 of the application is called by default despite your default setting. If you put the old version to Retired and Off to make sure it will not be called, then neither version 1.0 nor version 2.0 is called.

Cause
The latest loaded revision of a process was set as default instead of setting the default version, based on the information from the database

Bug 5837566 SUB PROCESS VERSION ONE GETS FAULTED PRIOR TO VERSION TWO

Solution

To implement the solution, please execute the following steps:

1. If no other patch is installed on the system, apply patch for Bug 5837566
2. If there are any other patches applied either
- Apply the fix for Bug 5837566 if it does not conflict with any other patches already applied
OR
- Apply 10.1.3.3 patch when it becomes available

Comments

Post a Comment

Popular posts from this blog

ORA-44412: XE edition memory parameter invalid or not specified

-
SQL> connect sys as sysdba Enter password: Connected to an idle instance. SQL> startup ORA-44412: XE edition memory parameter invalid or not specified SQL> startup pfile=C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 bytes Redo Buffers 2904064 bytes Database mounted. Database opened. SQL> create spfile from pfile='C:\oraclexe\app\oracle\product\10.2.0\server\config\scripts\init.ora'; File created. SQL> shutdown Database closed. Database dismounted. ORACLE instance shut down. SQL> startup ORACLE instance started. Total System Global Area 805306368 bytes Fixed Size 1289996 bytes Variable Size 209715444 bytes Database Buffers 591396864 byt
Read more

How to mount a WD Book Live as NFS in OEL6U3

-
Scenario : I have a Windows 8 (Host) laptop on which I am running two OEL6U3 (Guest) machines in a Virtual Box. I want to have a shared mount between the two Linux machine which will allow me to read/write from both the machines concurrently. Its a very common scenario for a High Availability Environment. Virtual Box provides a facility of creating sharable VDI disks which can be mounted on multiple machines, but it doesn’t allow concurrent read/write access from multiple machines. If you are installing RAC database then its still achievable, because ASM will provide the feature of concurrent read/writes, but if you want to install a WebLogic cluster with High Availability the recommended approach would be to have a Shared Mount. Step to create a shared nfs mount is fairly simple. I am using a WD My Book Live, and will mount the Public folder as shared mount 1. Get the hostname/ip of the WD device. 2. On the Linux Machine 1 create the folder where you want to mount the nfs
Read more

BPEL Sensor ExceptionsORABPEL 20300 - 20330

-
BPEL Sensor ExceptionsORABPEL 20300 - 20330 Sensor Exceptions 20300 - 20330 ORABPEL-20300 severity: 10 type: error name: Reports Error. description: A problem occurred while processing reports data. {0} fix: Please examine the log file to determine the problem. ORABPEL-20301 severity: 10 type: error name: Data Publisher failed. description: The Reporting Data Publisher {0} failed. fix: Please examine the log file for more details. ORABPEL-20302 severity: 2 type: warning name: JMS connection setup failed description: A problem occurred while setting up a connection to the JMS Destination {0} using the connection factory {1}. fix: Please verify the JMS configuration as well as the error to determine the problem. ORABPEL-20303 severity: 8 type: error name: JMS publish failed description: An error occurred while publishing reporting data to the JMS destination \"{0} \". fix: Please verify the JMS destination is valid. ORABPEL-20304 severity: 8 type:
Read more