Posts Tagged ‘Critical Patch Collection’


Critical Patch Update for October is Being Delayed

September 9th, 2009 by Robert McMillen • No Comments »

On a quarterly basis Oracle releases a series of Critical Patches in a bundle which is often referred to as the “CPU” or “CPC” (Collection).

Normally we will see these CPU’s arriving in January, July, April and October but there will be a delay on the October patch.  Given that the last quarter is an important business quarter because of the holiday business and payroll changes that have to be applied, this October patch is always important.

Here’s the text with an update on the October CPU.

Dear Oracle Customer,

There is a change in the previously announced release date of the October 2009 Critical patch Update.

Since many Oracle customers with responsibility for deploying the Critical Patch Update within their respective organizations will be attending Oracle OpenWorld October 11-15, 2009, the October 2009 Critical Patch Update originally scheduled to be published on Tuesday, October 13th 2009, will be released on October 20th 2009.

Please note: this date change only impacts the October 2009 Critical Patch Update. As usual, Oracle will issue a pre-release announcement on the Thursday before the publication of the Critical Patch Update (Thursday, October 15th). All other aspects of the Critical Patch Update (where to find the documentation, how to download the patches, etc.) remain the same.

The next four Critical Patch Update release dates are:

October 20, 2009,   January 12, 2010,  April 13, 2010, and  July 13, 2010

You will be notified via email once the Critical Patch Update for October 2009 has been released.

No Comments »

 

Release 12 Critical Patch Collection for November Available

December 1st, 2008 by Robert McMillen • No Comments »

In a previous post we discussed the new patching bundle, the Critical Patch Collection (CPC) that Oracle began issuing in October.  As a recap, this is what Oracle says about CPC’s.

R12 Financials Critical Patch Collections (CPC) are consolidated critical patches that all R12 Financials customers must apply to ensure proper operation of their systems. Advantages of applying CPCs over one-off fixes and RUPs are as follows:

  • CPCs are fully quality assured against current RUP levels. Individual one-off patches are not.
  • CPCs are consolidated and only contain critical patches that apply to broad customer usages. They are smaller in footprint and therefore much easier to apply and uptake than RUPs.
  • CPC Readmes have detailed business and functional information about the fixes included. Customers can leverage the Readmes to determine impact and testing required for specific process flows and software components involved.

The header entry for CPC’s is found in Doc 557869.1 which describes all released CPC’s.

Be aware that there is a new CPC for November, release November 12th.  This second CPC applies to just Payables and Receivables.

You can find out more about it in the following documents:

EBS: R12 Payables Critical Patch Collection November 2008, (Doc 745767.1, Patch 7456652, 23Mb)

This first patch requires a minimum of R12.AD.A.delta.2,R12.ATG_PF.A.delta.2 and R12.PJ_PF.A.delta.2

Also there is a pre-requisite for Latin American users you should check in the README.

EBS: R12 Receivables Critical Patch Collection November 2008, (Doc 745769.1, Patch 7387254, 26Mb)

This second patch requires a post-install step of running the “Import Application Accounting Definitions” concurrent request.

We haven’t applied this yet in our environments but will be doing so soon so I’ll update this post when complete.

No Comments »

 

Applying RUP6 for Release 12.0.6

December 1st, 2008 by Robert McMillen • No Comments »

I recently applied the latest RUP for Release 12 at a client that is in the midst of a new R12 installation.  I thought I’d recap my experience.

The 12.0.6 patch was released on Friday, November 7th.  We were alerted to it because we ran a fresh version of patchsets.sh during the week and it indicated that everything we had installed was superseded by an unreleased patch.  That got our curiosity going and we checked around Metalink finding that RUP6 was imminent.

The environment was using RedHat Linux 64 bit.  We had recently upgraded the Oracle database from 10.2.0.3 to 10.2.0.4.  They were already on RUP5 and we had recently applied the October CPU and the October Critical Patch Collection patches.  Bottom-line, we were very up-to-date.

Our environment consisted of two Application Servers and a single DB Server.  We were using ASM (10.2.0.4) but not using RAC.  We also had a shared APPL_TOP using OCFS2 for the two Application Servers.

You must start by applying the pre-requisite adpatch, R12 AD.A Delta 6 (Patch 7305520, Doc 736655.1).  It’s about 1.4Mb in size.  After downloading it there was a script to run for adgrants listed in the Patch 7305520 README.  We ran it, the adgrants.sql script, (as sysdba) to grant privileges to selected SYS objects and create PL/SQL profiler objects. We then applied patch 7305520 with adpatch.

Next we downloaded the RUP6 (Patch 6728000, Doc 743368.1).  It’s a big one at 2Gb in size.  It is multi-language but since we had an English-only installation we just downloaded the Linux86 version from Metalink.  It comes packaged in four files:

p6728000_R12_LINUX_1of4.zip  498Mb

p6728000_R12_LINUX_2of4.zip 546Mb

p6728000_R12_LINUX_4of4.zip 503Mb

p6728000_R12_LINUX_4of4.zip 429Mb

Looking at the README, it’s a straight-forward install with adpatch.  However if you have HR implemented there are some post-install steps which I didn’t have to do.  More information about that is in Document 145837.1 on Metalink.

The next step was to install the RUP6 Help Files (Patch 7109200, Doc 743368.1).  This is another multi-language patch where we only had to install the Generic version.  This is a simple adpatch install with no pre/post requirements.

In summary, it was a fairly simple patch exercise for our environment.  Hope yours is the same!

No Comments »