I would open up an SR with Oracle in parallel to ask which patch is actually applicable. On Wed, Mar 19, 2014 at 10:15 AM, Thomas Day <tomdaytwo@xxxxxxxxx> wrote: > Well, the Patch Set Update and Critical Patch Update January 2014 > Availability Document (Doc ID 1594621.1) document says that for 11.2.0.3.0 > the latest patch for Microsoft Windows x64 (64-Bit) BP 28 is Patch > 17906982<https://support.oracle.com/epmos/faces/ui/patch/PatchDetail.jspx?patchId=17906982>, > or > later<https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?id=161549.1>. > Patch 17906982 is not available. The later link leads to Oracle Database, > Networking and Grid Agent Patches for Microsoft Platforms (Doc ID 161549.1) > which has Patch 18075406: ORACLE 11G 11.2.0.3 PATCH 29 BUG FOR WINDOWS > (64-BIT AMD64 AND INTEL EM64) for 10.2.0.3.0 Patch 29. 10.2.0.3.0 Patch 30 > is not available yet. > > So now I can't figure out how I got to patch 18223971. I'm am not so > smart that a poorly engineered bit of technology can't flummox me. > > > On Wed, Mar 19, 2014 at 9:13 AM, John Hurley <hurleyjohnb@xxxxxxxxx>wrote: > >> First question is do you want to go to latest 11.2.0.3.x or to 11.2.0.4.x >> but question zero is do you have good closely matching test system to >> practice and test against? Big diff between going up to 11.2.0.4 plus ( >> rumors ) of issues with 11.2.0.4 on various platforms >> >> Sent from my iPhone >> >> > On Mar 19, 2014, at 8:56 AM, Thomas Day <tomdaytwo@xxxxxxxxx> wrote: >> > >> > We want to patch Oracle Database 11g Enterprise Edition Release >> 11.2.0.3.0 - 64bit running on Windows Server 2008 R2 Enterprise. >> > >> > I've searched My Oracle and here's the best that I can come up with: >> > >> > >> > You must use the OPatch utility version 11.2.0.3.5 or later to apply >> this patch. >> > >> > Pre-requisit for patch 18223971 is Oracle® Database Patch (18069285) - >> version 11.2.0.4.2. >> > >> > Oracle recomments Patch 18180390: AFTER APPLYING DBPSU 11.2.0.4.1 Patch >> (18069285) >> > >> > Known issues for >> > Oracle® Database Patch (18223971) - version 11.2.0.4.3 >> > >> > Bug 18180390 -- This can be safely ignored. Should be fixed by Patch >> 18180390 above. >> > >> > Now this looks like more than a patch. It's an upgrade to 11.2.0.4.3. >> But it can be done via the OPatch utility. I just thought that I'd check >> and see if I missed something obvious. Has anyone had any experience (good >> or bad) patching 11.2.0.3.0? >> > >> > Thanks. >> > > -- A life yet to be lived...