From sac-owner Mon Jan 28 06:00:44 2008 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m0SE0gdx010946 for ; Mon, 28 Jan 2008 06:00:43 -0800 (PST) Received: from sunmail4.singapore.sun.com (localhost [127.0.0.1]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m0SE0goT007321 for ; Mon, 28 Jan 2008 22:00:42 +0800 (SGT) Received: (from noaccess@localhost) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/Submit) id m0SE0g1O007319 for one-pager-not-2b-used-directly; Mon, 28 Jan 2008 22:00:42 +0800 (SGT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id m0SE0c1Z007287; Mon, 28 Jan 2008 22:00:41 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JVC00H01XL41400@brm-avmta-1.central.sun.com>; Mon, 28 Jan 2008 07:00:40 -0700 (MST) Received: from gmp-eb-mail-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JVC002OZXL351D0@brm-avmta-1.central.sun.com>; Mon, 28 Jan 2008 07:00:40 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m0SE0dV9025764; Mon, 28 Jan 2008 14:00:39 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JVC00401X0NGN00@fe-emea-10.sun.com> (original mail from Steve.McKinty@Sun.COM); Mon, 28 Jan 2008 14:00:39 +0000 (GMT) Received: from [129.157.192.78] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JVC008U1XK85I40@fe-emea-10.sun.com>; Mon, 28 Jan 2008 14:00:08 +0000 (GMT) Date: Mon, 28 Jan 2008 14:59:45 +0100 From: Steve McKinty Subject: [2008/054]Oracle DataGuard Module for Solaris Cluster Geographic Edition. Sender: Steve.McKinty@sun.com To: one-pager@sun.com Cc: sc-odyssey-dev Message-id: <479DDFD1.6040604@sun.com> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_tC40Q1g0ldgvkfnbyQsVnQ)" X-PMX-Version: 5.2.0.264296 User-Agent: Thunderbird 2.0.0.4 (X11/20070615) Status: RO Content-Length: 4911 This is a multi-part message in MIME format. --Boundary_(ID_tC40Q1g0ldgvkfnbyQsVnQ) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Hi, Please find attached a 1-pager for an Oracle DataGuard Module for Solaris Cluster Geographic Edition. Although Solaris Cluster itself is usually reviewed by PSARC, historically the Geo Edition framework has been addressed by LSARC. Thanks Steve -- Steve McKinty Architect - Sun Cluster Geographic Edition Grenoble Engineering Centre, France: http://blogs.sfbay/gec/ --Boundary_(ID_tC40Q1g0ldgvkfnbyQsVnQ) Content-type: text/plain; name=SCGE_ODG_1-pager.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=SCGE_ODG_1-pager.txt 1. Introduction 1.1. Project/Component Working Name: Oracle dataGuard Module for Sun Cluster Geographic Edition ("Odyssey") 1.2. Name of Document Author/Supplier: Steve McKinty/Tim Read 1.3. Date of This Document: 01/28/08 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Solaris Cluster PAC JES PAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Meenakshi.Kaul-Basu@Sun.COM 1.4.4. The name of your business unit: Solaris 1.5. Email Aliases: 1.5.1. Responsible Manager: Burt.Clouse@Sun.COM 1.5.2. Responsible Engineer: Tim.Read@Sun.COM 1.5.3. Marketing Manager: Eve.Kleinknecht@Sun.COM 1.5.4. Interest List: sc-odyssey-dev@Sun.COM 2. Project Summary 2.1. Project Description: This is an additional component for the SCGE project that was described in LSARC/2004/281 and LSARC/2006/039. It covers the addition of a replication module to control Oracle DataGuard (ODG) 2.2. Risks and Assumptions: None. 3. Business Summary 3.1. Problem Area: Solaris Cluster Geographic Edition (SCGE), codenamed Odyssey, is management framework which integrates Solaris Cluster with one of several data replication products from various suppliers, including Sun. Each replication product is controlled by a specfic module in the form of a Cacao MBean, which plugs into the SCGE framework. This project describes the replication module for Oracle DataGuard (ODG). ODG is an application-based replication mechanism which enables an Oracle database called the Primary to send transaction information to remotely-located database (the Secondary) for security and backup purposes. 3.2. Market/Requester: Solaris Cluster. 3.3. Business Justification: Oracle users are a very large part of the Solaris Cluster market, which brings $60m/year of income to Sun. Recent disasters (floods, 9/11) have made people more aware of the need for disaster protection in their data centres, and ODG is the mechanism of choice for Oracle. We need to support it in order to maintain, and grow, our Oracle user base. 3.4. Competitive Analysis: Please see the table at: http://galileo.sfbay/odyssey/compInfo/index.html 3.5. Opportunity Window/Exposure: Already receiving several requests to support various Oracle RAC configurations with SCGE. 3.6. How will you know when you are done?: Successful integration of the product into the next SCGE release. 4. Technical Description: 4.1. Details: 4.2. Bug/RFE Number(s): See Solaris Cluster FBC 2007/1612 http://galileo.sfbay/SC/dev-process/features/2007/1612/ 4.3. In Scope: 4.4. Out of Scope: 4.5. Interfaces: 4.6. Doc Impact: SCGE has one document per supported replication type, so a new document will be added to the docset for DataGuard. The manpages will be updated to reflect the changes. 4.7. Admin/Config Impact: 4.8. HA Impact: As described above. 4.9. I18N/L10N Impact: No impact, I18N/L10N will be done as for the overall product. 4.10. Packaging & Delivery: The product will be shipped as standard Solaris packages. It will be installed by the JES installer or whatever replaces that. 4.11. Security Impact: 4.12. Dependencies: - Cacao 2.x - Oracle 10g R2 RAC 4.13. Upgrade. This is a new product. 5. Reference Documents: 6. Resources and Schedule: 6.1. Projected Availability: Beta at end-February 2008 GA with SC3.2u2, near end CY08 6.2. Cost of Effort: 1 development engineer, existing QA and doc resources. 6.3. Cost of Capital Resources: 6.4. Product Approval Committee requested information: N/A FBC already approved by Solaris Cluster PAC/CPT. 6.5. ARC review type: Standard (possibly combined inception/commitment) 6.6. ARC Exposure: Open. SCGE code is now open source, and all future changes will be made in the view of the OHAC community. 7. Prototype Availability: 7.1. Prototype Availability: Today, at Beta stage. --Boundary_(ID_tC40Q1g0ldgvkfnbyQsVnQ)--