You should upgrade your Weblogic version to at least 10.3.6.0.12 - It's simple

Upgrading your weblogic version can help you improve stability and performance on your weblogic instance and also help deal with leaked connections and other issues.  Also, as far as upgrades go, it really doesn't get much easier than upgrading your weblogic version if you stay within the same release.

For example, we just upgraded a demo instance from 10.3.0.6.4 to .12

In case you are wondering, 10.3.0.6.12 is the current minimum supported version of Weblogic for R12.2 EBS, and based on the amount of downloads for it and other things I've read, its considered a "favorite" and stable release for many people.

I would recommend by first downloading the latest ETCC patch and running the checkMTpatch.sh against your EBS.  This will give you a FULL report on what patches you should apply for all of your currently installed applications in the tech stack.

Ours recommended we upgrade to at least 10.3.0.6.12 and then rerun checkMTpatch.sh for a new set of patch recommendations afterwards.

We did ample research before upgrading and came across a note that was pretty helpful, stating that we'd most likely need to remove some patches before we could apply the new .12 version to upgrade, but I'll get to that in a minute.

Getting Conflict When Applying Weblogic 10.3.6 PSU Patch 20780171 (Doc ID 2048247.1)


We shut down all the weblogic servers and OHS, then removed the following patches below.  How'd we know which ones to remove - easy.  When you try to install the new .12 patch version it does a crosscheck of the incompatible patches you need to first remove before it can be applied.  

First things first:

Navigate to the $FMW_HOME/utils/bsu directory.

E-WL: Weblogic Smart Update (BSU) Hangs when Starting (Doc ID 2002949.1)

Modify memory arguments to 1GB inside bsu.sh.  The patch will fail with a java error if you do not!

MEM_ARGS="-Xms1024m -Xmx1024m"


=====================

Next:

Download and unzip the  20780171 - 10.3.6.0.12 patch in the recommended directory:

$FMW_HOME/utils/bsu/cache_dir

When you unzip the patch it comes out as a Alpha-Numeric jar file. 

Example: unzip p20780171_1036_Generic.zip
extracting: EJUW.jar

You'll notice you will use this 4 character name (EJUW) to apply the patch, minus the dot jar at the end, as seen below:

 20780171 - 10.3.6.0.12 patch

bsu.sh -install -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir -patchlist=EJUW -prod_dir=$FMW_HOME/wlserver_10.3/

It came back with the list of incompatible patches:

D33T,LL4G,VFS8,Y5AP, and YIJF 

You may have to play with the order of removing as we tried all of them at first and got another dependency so that's why we pulled a particular one out and did it first.

>cd $FMW_HOME/utils/bsu/

bsu.sh -remove -patchlist=YIJF -prod_dir=$FMW_HOME/wlserver_10.3/

bsu.sh -remove -patchlist=D33T,LL4G,VFS8,Y5AP -prod_dir=$FMW_HOME/wlserver_10.3/

 20780171 - 10.3.6.0.12 patch

bsu.sh -install -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir -patchlist=EJUW -prod_dir=$FMW_HOME/wlserver_10.3/

 13729611 - immediately applied after according to note above (Doc ID 2048247.1)

bsu.sh -install -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir -patchlist=L34G -prod_dir=$FMW_HOME/wlserver_10.3/

Reran the checkMTpatch.sh script and it provided us with a new list of patches to apply:

 17319481, 19259028, 19687084, 20474010, 22128205, 22323006

bsu.sh -install -patch_download_dir=$FMW_HOME/utils/bsu/cache_dir -patchlist=N5FK,TYHS,8FBW,S8H6,GK5N,DI8E -prod_dir=$FMW_HOME/wlserver_10.3/

After applying these you should go ahead and run the checkMTpatch.sh again one more time to assure that there are no remaining patches to apply, we got the message that we were all up to date on our version of WLS afterwards.

At this point you can go ahead and start up your Admin Server and then all of your WLS managed servers, and lastly OHS.

Also if you are curious as to an easy way to find out what version you are using:

>cd $FMW_HOME/user_projects/domains/EBS_domain_<SID>/bin

>. setDomainEnv.sh     --make sure there is a space between to source

>java weblogic.version

WebLogic Server Temporary Patch for BUG22128205 Fri Nov 13 16:02:12 IST 2015
WebLogic Server Temporary Patch for BUG20474010 Sun Mar 01 17:22:18 IST 2015
WebLogic Server Temporary Patch for BUG19687084 Mon Jun 29 15:01:13 IST 2015
WebLogic Server Temporary Patch for BUG19259028 Wed Aug 19 14:57:09 IST 2015
WebLogic Server Temporary Patch for BUG17319481 Wed Jul 01 23:52:43 MDT 2015
WebLogic Server Temporary Patch for BUG13729611 Fri Jun 26 09:54:52 MDT 2015
WebLogic Server 10.3.6.0.12 PSU Patch for BUG20780171 THU JUN 18 15:54:42 IST 2015
WebLogic Server Temporary Patch for BUG17495356 Tue Sep 24 00:23:38 CDT 2013
WebLogic Server Temporary Patch for BUG17495356 Tue Sep 24 00:23:38 CDT 2013
WebLogic Server Temporary Patch for BUG17495356 Tue Sep 24 00:23:38 CDT 2013
WebLogic Server Temporary Patch for BUG17495356 Tue Sep 24 00:23:38 CDT 2013
WebLogic Server Temporary Patch for BUG17495356 Tue Sep 24 00:23:38 CDT 2013
WebLogic Server Temporary Patch for ${CRS} Mon Jul 30 16:45:20 EDT 2012
WebLogic Server Temporary Patch for ${CRS} Mon Jul 30 16:45:20 EDT 2012
WebLogic Server Temporary Patch for BUG13845626 Tue Mar 20 17:35:12 IST 2012
WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050


Cheers!  If anyone has any additional questions please let me know.