Re: Jan 14 PSU patches

From: Sanjay Mishra <smishra_97_at_yahoo.com>
Date: Fri, 31 Jan 2014 07:50:27 -0800 (PST)
Message-ID: <1391183427.52161.YahooMailNeo_at_web122106.mail.ne1.yahoo.com>



Thanks Rajesh and Raj for your comments and the document links. -- Sanjay On Friday, January 31, 2014 10:27 AM, Rajesh Aialavajjala <r.aialavajjala_at_gmail.com> wrote: Sanjay,  I cannot comment to the first of your points - I'm sure folks who have anything to report will pipe up...but as to the 2nd... The Patch README - specific to the release you are targeting of course - will normally contain a "Known Issues" Section...  There also will be MOS Documents published tracking known issues ... for example... My Oracle Support Document 1593200.1 Oracle Database Patch Set Update 11.2.0.4.1 Known Issues. My Oracle Support Document 1593188.1 Oracle Grid Infrastructure Patch Set Update 11.2.0.3.9 Known Issues. My Oracle Support Document 1593211.1 Oracle Database Patch Set Update 11.2.0.3.9 Known Issues. My understanding is that these documents are updated basing on feedback (SR/SR leading to Bugs) and they contain change history... I'd also suggest reviewing - these notes discuss patches that are to be "highly desirable" but not necessarily included in PSUs' - the title is a touch misleading - these should be reviewed prior to/in conjunction with PSU applications - not just upgrades... Things to Consider Before Upgrading to 11.2.0.3 to Avoid Poor Performance or Wrong Results (Doc ID 1392633.1) Things to Consider Before Upgrading to 11.2.0.2 to Avoid Poor Performance or Wrong Results (Doc ID 1320966.1)  To your 3rd point - once again - I shall defer to the expertise of other list members... Thanks, --Rajesh On Fri, Jan 31, 2014 at 9:53 AM, Sanjay Mishra <smishra_97_at_yahoo.com> wrote: Hi > > > * Does anyone experienced any major issue/bug reported for latest Jan '2014 SPU/PSU on any platform for both GI/RDBMS ? > * Is there any Oracle doc which might be updated to help to verify before applying any latest PSU patch for errors reported/workaround ? Or any best way to double check before going for the deployment. Ofcourse will follow Dev-test-Prod cycle. > * Isn't we can share in our listgroup one chain where people can report or share only if they encounter any issue where several of us are checking or getting the mail for the list. > > >--- >Sanjay >
--
http://www.freelists.org/webpage/oracle-l
Received on Fri Jan 31 2014 - 16:50:27 CET

Original text of this message