Troubled SOA Patch Set 2

Grrrr, lost about one whole day trying to figure out a problem that is caused by 'improper' patch of SOA suite from 11.1.1.2.0 to 11.1.1.3.0.

Scouted the internet and found only one thread in OTN, but there is no answer to it other than people suggesting re-installing the whole SOA and re-apply patch from scratch.

The problem is highlighted here http://forums.oracle.com/forums/thread.jspa?threadID=1005454

How I got into this problem? Here is what I suspected.

After installing the package SOA suite 11.1.1.2.0, I created my domain with soa_server and bam_server. Played around with it, unable to start the managed servers. Googled around, realised that I had to apply the PS2. Downloaded, and patched.

After that, the problem occurs during soa_server1 startup. After a bit of digging, I suspect it is the old cache of ear and jar in some tmp folder have caused the problem. Cleaning up the cache appears to have caused the startup to throw out different sort of problem, which said 'unable to find ... in xxx ear'. After some more efforts, I finally throw in the towel and figured it would be more productive just to re-install the entire WLS, SOA suite and Jdev.

Summary of the typical sequence of steps of installation:

1) Oracle DB 11g R1
2) rcu 11.1.1.3.0
3) WLS 10.3.3
4) SOA Suite 11.1.1.2.0
5) SOA PS2 11.1.1.3.0
6) Jdeveloper 11.1.1.3.0

Everything works now.