Oracle Critical Update Patch (CPU) for April 2006 Now Available


The latest Oracle Critical Update Patch (CPU) for April 2006 has been released.  Due to extremely-strict Oracle security policies, I'm not permitted to discuss this in any way, other than reprinting the public notice sent to all Oracle customers yesterday:

The Critical Patch Update for April 2006 is now available. Oracle strongly recommends applying the patches as soon as possible.

The Critical Patch Update Advisory is the starting point for relevant information, and it provides instructions on how to obtain the patches. It contains a summary of the security vulnerabilities and links to other important documents.

It is essential to refer to the Pre-Installation Notes before applying patches, since it is where you can find clarifications and corrections to the installation instructions.

The Critical Patch Update Advisory is available at any of the following locations:

MetaLink as Doc ID 360044.1:
https://metalink.oracle.com/metalink/plsql/showdoc?db=NOT&id=360044.1

Oracle Technology Network:
http://www.oracle.com/technology/deploy/security/alerts.htm

Oracle PeopleSoft Enterprise and JD Edwards EnterpriseOne:   http://www.peoplesoft.com/corp/en/support/security_index.jsp

The next four Critical Patch Update release dates are:
  • July 18, 2006
  • October 17, 2006
  • January 16, 2006
  • April 17, 2007
Sincerely,
Oracle Security Alerts

Comments:

Prajvin,Your related SR was also circulated internally today, as well.  My answer is consistent with what the Support Engineers assigned to your SR have stated:  As a general policy, we strongly recommend that all customers take the latest version of Jinitiator. 
The latest Jinitiator release includes a variety of stability, performance, and security fixes.  This version of Jinitiator is also required for the 2007 Daylight Saving Time changes for specific applications.  I appreciate that deploying new versions of Jinitiator is costly, and all customers have their own criteria for deciding whether to upgrade or stay on their current release.  From a support perspective, remember that any Jinitiator issues will generally need to be reproduced on the latest version before patches can be issued; backports for older Jinitiator releases are rarer and harder to come by.Regards,Steven 

Posted by Steven Chan on May 07, 2007 at 04:31 AM PDT #

Steve,
Any technical reasons for Jinitator upgrade recommended in the Jan/Apr 2007 CPUs? If the customer is on 1.3.1.21, is the Jinitator upgrade required at all?

Posted by prajvin on May 07, 2007 at 07:04 AM PDT #

Steven,
Thanks for the quick feedback.
From the customer perspective, it is a very costly affair to have the jinitiator upgraded. Since the customer's use of Core Apps Modules are very limited, the plan is to stick with the 1.3.1.21 version and Apps is not an external facing one. The customer uses only Order managent and a few manufacturing modules. That too in order mangement it is 99% batch oriented..
With the module spectrum we have and the usage, we do not forsee any Jinitiator related issues that can come up.

Thanks again.

Posted by prajvin on May 08, 2007 at 03:37 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today