Complilation Error When Starting the SOA Server After Upgrade

When you start the Oracle SOA Suite for the first time after upgrade, you may see the compilation error in the SOA server logs.

The following error is displayed in the SOA server logs:

[2016-07-01T02:04:18.239-07:00] [soa_server1] [ERROR] [] 
[oracle.soa.bpel.system] [tid: DaemonWorkThread: '8' of WorkManager: 
'wm/SOAWorkManager'] [userId: ] [ecid: 
4f969dd2-853a-4ddf-be01-0ac2ca0d2210-00000009,0:11854] [APP: soa-infra] 
[partition-name: DOMAIN] [tenant-name: GLOBAL] Error while loading process.[[ 
The process domain is encountering the following errors while loading the 
process "ApprovalProcess" (composite 
"default/DefaultRequestApproval!5.0*soa_c9c16746-016e-40c4-aaea-6ccd2d685cb4") 
. 
: BPEL 1.1 compilation failed. 
This error contained an exception thrown by the underlying process loader 
module. 
Check the exception trace in the log (with logging level set to debug mode). 
If there is a patch installed on the server, verify that the bpelcClasspath 
domain property includes the patch classes.

Check the SOA composites status from Oracle Enterprise Manager console after successful start of the Oracle Identity Manager Managed Server.

If the Enterprise Manager console shows DefaultRequestApproval!5.0 composite status as actively deployed, ignore this one time error.

If you have upgraded your 11g Release 2 (11.1.2.2.0) environments to 11g Release 2 (11.1.2.3.0), and then to 12c (12.2.1.3.0), you will see the compilation error for DefaultRequestApproval!3.0 composite. This composite was in use in 11g Release 2 (11.1.2.2.0). Before you upgraded to 11.1.2.3.0, this composite processed all of the inflight requests. After upgrading to 11.1.2.3.0, all of the new requests go via DefaultRequestApproval!5.0 composite.

DefaultRequestApproval!3.0 is irrelevant when upgrading from 11.1.2.3.0 to 12c (12.2.1.3.0). Therefore, this compilation error can be ignored.