Received: (qmail 17080 invoked from network); 2 Feb 2011 15:07:14 -0600 Received: from freelists-180.iquest.net (HELO turing.freelists.org) (206.53.239.180) by static-ip-85-25-126-90.inaddr.intergenia.de with SMTP; 2 Feb 2011 15:07:06 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id CE133D64680; Wed, 2 Feb 2011 16:07:00 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=freelists.org; s=turing; t=1296680820; bh=1r75IO/dTpNa/TnC0e2F6ykQN1wfvTB+X/uXtb2e kWg=; h=Message-ID:From:To:Subject:Date:MIME-Version:Content-Type: Sender:Reply-To:List-help:List-unsubscribe:List-Id:List-subscribe: List-owner:List-post:List-archive; b=DqowQiRUWyYoTg/asLmvUlVncrp3i L8NwDqOBS53sCTj0mRnyQZAcQNUvHozDRXLVtJhee28Coqo+6y5EJOadr8tl0UX2uG8 1igeBbZBXeiL/WFRnBY/B6X0tcL2r7jIOs/GiU1B1+F8l5IhRtuGlLgoY+gL8AQIIez cNuQLMrA= X-Virus-Scanned: Debian amavisd-new at localhost.localdomain Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KX+CmsWJW6iG; Wed, 2 Feb 2011 16:07:00 -0500 (EST) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id D4CDBD645DE; Wed, 2 Feb 2011 16:06:16 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Wed, 02 Feb 2011 16:05:35 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 75C7DD645AE for ; Wed, 2 Feb 2011 16:05:35 -0500 (EST) Authentication-Results: turing.freelists.org; dkim=pass (1024-bit key) header.i=@gmail.com Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vet2XngolWFd for ; Wed, 2 Feb 2011 16:05:35 -0500 (EST) Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id EC811D6443B for ; Wed, 2 Feb 2011 16:05:34 -0500 (EST) Received: by qyj19 with SMTP id 19so445401qyj.10 for ; Wed, 02 Feb 2011 13:05:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date:mime-version :content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; bh=m9ciKXKVKT2eaJ6qJiAIRUXKMKqBTYqRSoveFi7Om9s=; b=P+4NfyyN2+D7ix0C1f4/0DSioSbEKGUUvKwpNCzVjqfI613V9hAkTpbG9qzIRxQglO TwtxqSZ/1Wg/j1BlhRVczQgcAGn7/z0rHvKgBllGcIBgM+Q2c9w0gQZZ9FPRBlTByjgQ shmgUEeJo5ksd+mZarnLiNTdWGTrwi5ENOyD4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:mime-version:content-type :x-priority:x-msmail-priority:x-mailer:x-mimeole; b=m+pr9MT8xrONfSvd4j52wZxUgORdQUS6u3YQkCJR7zqlIwvZOXT0+FQP+QjWK4IWQz /d32WhA5QXib4HoicY9L5RVbXypRTO570csMqdqueoWKchluF9fwxwOS5+jXSGxxDabP XPlMNhKbFvkYcrc7KDRO2zeksZq4vwwGXTdOg= Received: by 10.224.191.7 with SMTP id dk7mr9180360qab.195.1296680734321; Wed, 02 Feb 2011 13:05:34 -0800 (PST) Received: from CATHY ([69.183.234.73]) by mx.google.com with ESMTPS id p13sm29065qcu.5.2011.02.02.13.05.32 (version=SSLv3 cipher=RC4-MD5); Wed, 02 Feb 2011 13:05:33 -0800 (PST) Message-ID: From: "ed lewis" To: Subject: clusterware upgrade question Date: Wed, 2 Feb 2011 16:05:32 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01CBC2F3.04BA22A0" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-archive-position: 34106 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: eglewis71@gmail.com Precedence: normal Reply-To: eglewis71@gmail.com List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-subscribe: List-owner: List-post: List-archive: X-list: oracle-l ------=_NextPart_000_0028_01CBC2F3.04BA22A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I'm getting ready to upgrade our current cluster from 10.2.0.4 to 10.2.0.5 (Solaris 64-bit). The components being upgraded include=20 clusterware, RAC, ASM, RDBMS , and Dataguard. In regard to the clusterware, we have a 2 node cluster. In the patch notes, it states that all Oracle database instances on all cluster nodes, must be shut down before applying the=20 clusterware patch. Later on in the notes, it states that a rolling upgrade for the clusterware can be done. I'm seeing conflcting messages here. I've done rolling upgrades before with patch sets, but not with an = upgrade. I've contacted Oracle support about this,but they were of little help.=20 Can the clusterware upgrade be done in a rolling fashion ? In regard to Dataguard. We have physical standby, 2 - node cluster. From what I understand, the physical standby should be upgraded before the primary database (in this case a cluster). Once that is done, the primary environment is then upgraded. Does the primary need to be upgraded at the same time ? Can it=20 be upgraded a day or a week later ? thanks =20 ed ------=_NextPart_000_0028_01CBC2F3.04BA22A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
    I'm getting ready to = upgrade our current cluster
from 10.2.0.4 to 10.2.0.5 (Solaris=20 64-bit).
The components being upgraded include =
clusterware, RAC, ASM, RDBMS , and=20 Dataguard.
 
   In regard to the = clusterware, we=20 have a 2 node cluster.
In the patch notes, it states that all = Oracle=20 database instances
on all cluster nodes, must be shut down = before=20 applying the
clusterware patch. Later on in the = notes, it states=20 that a
rolling upgrade for the clusterware can = be done.=20 I'm seeing
conflcting messages here.
     I've done = rolling upgrades before with patch sets, but not = with an=20 upgrade.
I've contacted Oracle support about = this,but they=20 were of little help.
 
    Can the clusterware = upgrade be=20 done in a rolling fashion ?
 
     In regard to = Dataguard. We=20 have physical standby, 2 - node cluster.
From what I understand, the physical = standby should=20 be upgraded before
the primary database (in this case a = cluster). Once=20 that is done, the
primary environment is then = upgraded.
        = Does the=20 primary need to be upgraded at the same time ? Can it
be upgraded a day or a week later = ?
 
    = thanks   =20    
 
ed
    =
------=_NextPart_000_0028_01CBC2F3.04BA22A0-- -- http://www.freelists.org/webpage/oracle-l