From oracle-l-bounce@freelists.org Tue Jun 28 13:43:34 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j5SIhYAr032133 for ; Tue, 28 Jun 2005 13:43:34 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180] (may be forged)) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j5SIhMIP032115 for ; Tue, 28 Jun 2005 13:43:23 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id E056B1C5A26; Tue, 28 Jun 2005 12:39:50 -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 23701-04; Tue, 28 Jun 2005 12:39:50 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 5625C1C5A25; Tue, 28 Jun 2005 12:39:50 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C57C08.135E2903" Subject: Oracle concurrent managers in 11i RAC environment Date: Tue, 28 Jun 2005 13:37:37 -0400 Message-ID: <77A4D80DB2ADD74EB5D7F1D31626F0C001EE1ABD@usa0300ms03.na.xerox.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Oracle concurrent managers in 11i RAC environment Thread-Index: AcV8CBMDIlhApavdTUeW4WBY24O5cA== From: "Hameed, Amir" To: X-OriginalArrivalTime: 28 Jun 2005 17:37:37.0867 (UTC) FILETIME=[138011B0:01C57C08] X-archive-position: 21767 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: Amir.Hameed@xerox.com Precedence: normal Reply-To: Amir.Hameed@xerox.com X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-mailscan-MailScanner-Information: Please contact the ISP for more information X-mailscan-MailScanner: Found to be clean X-MailScanner-From: oracle-l-bounce@freelists.org X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Status: No, hits=-3.5 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE autolearn=ham version=2.63 ------_=_NextPart_001_01C57C08.135E2903 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am looking for some help/input on managing concurrent managers in an 11i/RAC environment. Following is the environment configuration and the problem description : I am running Oracle E-business suite (11.5.9) in a three-node RAC environment using Veritas's "DBE/AC for 9i RAC" suite. PCP is configured and concurrent managers are running on all nodes. This is lab environment and I am in the process of engineering the design for deployment in production later this year. The managers work fine in terms of node or instance failure and they failover properly. The question I have is from the environment management standpoint: ** If I want to take a node down for scheduled/regular maintenance reasons, how do I "gracefully" migrate managers running on that specific node to their secondary node? Those managers may include ICM or other concurrent managers If there is someone in this list who currently has RAC deployed in production and is running concurrent managers in PCP configuration then I would really like to know what process they follow when they have to take a node down for scheduled maintenance. Thank you Amir ------_=_NextPart_001_01C57C08.135E2903 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Oracle concurrent managers in 11i RAC environment

Hi,
I am looking for some = help/input on managing concurrent managers in an 11i/RAC environment. = Following is the environment configuration and the problem description = :

I am running Oracle E-business = suite (11.5.9) in a three-node RAC environment using Veritas's = "DBE/AC for 9i RAC" suite. PCP is configured and concurrent = managers are running on all nodes. This is lab environment and I am in = the process of engineering the design for deployment in production later = this year. The managers work fine in terms of node or instance failure = and they failover properly. The question I have is from the environment = management standpoint:
** If I want to take a node down for scheduled/regular maintenance = reasons, how do I "gracefully" migrate managers running on = that specific node to their secondary node? Those managers may include = ICM or other concurrent managers
If there is someone in this = list who currently has RAC deployed in production and is running = concurrent managers in PCP configuration then I would really like to = know what process they follow when they have to take a node down for = scheduled maintenance.

Thank you
Amir

------_=_NextPart_001_01C57C08.135E2903-- -- http://www.freelists.org/webpage/oracle-l