From oracle-l-bounce@freelists.org Fri Sep 3 13:24:25 2004 Return-Path: Received: from air189.startdedicated.com (root@localhost) by orafaq.com (8.11.6/8.11.6) with ESMTP id i83IOOa28808 for ; Fri, 3 Sep 2004 13:24:24 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air189.startdedicated.com (8.11.6/8.11.6) with ESMTP id i83IOOI28803 for ; Fri, 3 Sep 2004 13:24:24 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2F64072C338; Fri, 3 Sep 2004 13:26:56 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01536-82; Fri, 3 Sep 2004 13:26:56 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 9535672C37B; Fri, 3 Sep 2004 13:26:55 -0500 (EST) X-Original-To: oracle-l@freelists.org Delivered-To: oracle-l@freelists.org X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: RE: patch set testing Date: Fri, 3 Sep 2004 14:28:51 -0400 Message-ID: <4C9B6FDA0B06FE4DAF5918BBF0AD82CF09EFEB3E@bosmail00.bos.il.pqe> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: patch set testing Thread-Index: AcSR4b7V8YMZx/cCSoK4ABs8Frx6ugAAMNZQ From: "Bobak, Mark" To: , X-OriginalArrivalTime: 03 Sep 2004 18:28:51.0471 (UTC) FILETIME=[DC6951F0:01C491E3] X-Virus-Scanned: by amavisd-new at freelists.org X-archive-position: 9123 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: Mark.Bobak@il.proquest.com Precedence: normal Reply-To: Mark.Bobak@il.proquest.com X-list: oracle-l X-Virus-Scanned: by amavisd-new at freelists.org Josh, Guidelines we follow are: 1) When moving a major release, like 8.1.7 to 9.2.0, always go with the newest patchset that's out, in this case, 9.2.0.5. 2.) If just bumping up a patchset, don't go there, unless you need to fix a problem that you actually have. If you're going from 9.2.0.2 to 9.2.0.5 just cause 9.2.0.5 is there, that's not a reason to go. 3.) Regardless of if we are going from one major release to another, we always try to roll it out with the release of our product, so that it gets a full complement of QA testing,=20 capacity testing and soak testing. 4.) We try to stay away from one-off patches all together, but, sometimes you can't. In that case, we'll roll it into our pre-prod environment, run a 3-4 hour cap test, and if that succeeds, we'll run a weekend long soak test, to hopefully=20 catch memory leaks, and those types of problems. Patching is always an art and never a science. You just mitigate what you can and hope for the best. (And be prepared for the worst!) Hope that helps, -Mark -----Original Message----- From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org]On Behalf Of Josh Collier Sent: Friday, September 03, 2004 2:14 PM To: oracle-l@freelists.org Subject: patch set testing Greetings, =20 Is there a routine you follow for testing patch sets, such as an upgrade from 9.2.0.3 to 9.2.0.5? =20 thanks, =20 Josh C.=20 -- To unsubscribe - = mailto:oracle-l-request@freelists.org&subject=3Dunsubscribe=20 To search the archives - http://www.freelists.org/archives/oracle-l/ -- To unsubscribe - mailto:oracle-l-request@freelists.org&subject=unsubscribe To search the archives - http://www.freelists.org/archives/oracle-l/