From John.Fischer@sun.com Wed Mar 11 12:12:59 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n2BJCx2T000656 for ; Wed, 11 Mar 2009 12:12:59 -0700 (PDT) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2BJCaMS001943 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Wed, 11 Mar 2009 12:12:58 -0700 (PDT) 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 <0KGC0001LW1L9100@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 11 Mar 2009 13:12:57 -0600 (MDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KGC00C3AW1HS7C0@brm-avmta-1.central.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 11 Mar 2009 13:12:53 -0600 (MDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n2BJCrX9010945 for ; Wed, 11 Mar 2009 19:12:53 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KGC00F00VCBEF00@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 11 Mar 2009 13:12:53 -0600 (MDT) Received: from [192.168.10.13] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KGC00ASIW1COO10@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Wed, 11 Mar 2009 13:12:49 -0600 (MDT) Date: Wed, 11 Mar 2009 12:11:58 -0700 From: John Fischer Subject: LSARC/2009/166 - EOL of Berkeley DB 4.2 Sender: John.Fischer@sun.com To: lsarc-ext@sun.com Cc: Karen Langford Reply-to: John.Fischer@sun.com Message-id: <49B80CFE.5010305@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_Lq5+sv/c2iMYKdAdPTkRYQ)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.18 (X11/20090211) Status: RO Content-Length: 11743 This is a multi-part message in MIME format. --Boundary_(ID_Lq5+sv/c2iMYKdAdPTkRYQ) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT All, I am sponsoring this case for Karen Langford from the Database group. The case was originally started on Monday, March 9th, 2009 but it would appear that sac did not send out the case properly. I have reset the timer for Wednesday, March 18th, 2009. The case directory contains the attached proposal and the final package maps once BDB 4.2 is removed. This case deprecates the Berkeley Database version 4.2 from a Patch release of Solaris (Solaris 10 Update) and removes it from a Minor release of Solaris (Nevada). The project will deliver the EOL notice as part of the release notes. As you might recall from the BDB 4.7 case (LSARC/2008/570) there is a migration tool that can be used on a BDB 4.2 database. Thanks, John --Boundary_(ID_Lq5+sv/c2iMYKdAdPTkRYQ) Content-type: text/plain; name=eol_proposal.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=eol_proposal.txt Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: EOL of Berkeley DB 4.2 in Solaris. 1.2. Name of Document Author/Supplier: Karen Langford 1.3. Date of This Document: 03/05/09 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Database 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: Jeffrey.Pugh@sun.com 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Lars.Heill@sun.com 1.5.2. Responsible Engineer: Karen.Langford@sun.com 1.5.3. Marketing Manager: Rebecca.Hansen@sun.com 1.5.4. Interest List: sleepycat-productgroup-users@sun.com 2. Project Summary 2.1. Project Description: The Berkeley DB (BDB) 4.2 release was approved by ARC back in 2003 and integrated into Nevada and Solaris in 2007. In 2008 the latest release of Berkeley DB 4.7 was approved by ARC and integrated into Nevada along with the old 4.2 release. This project proposes the EOL and removal of the 4.2 release from Nevada. 2.2. Previous relevant ARC cases LSARC/2003/585 BDB 4.2 - Integrated into Solaris 10 and Nevada LSARC/2008/570 BDB 4.7 - Integrated along with BDB 4.2 into Nevada Note BDB 4.2 is not in OpenSolaris, neither is 4.7. 2.3. Risks and Assumptions: As we propose to leave 4.2 in the Solaris Updates we see no risks there. We will commit to delivering critical bug fixes for the duration of the Update's Active Service Life. We also see no risk in regards to removing 4.2 from Nevada as S11 has not been offically released. We contacted our sole Nevada customer, Evolution, and they confirmed that they have upgraded their product to use 4.7. 3. Business Summary 3.1. Problem Area: As mentioned above we foresee no problems with removing 4.2 from Nevada. 3.2. Market/Requester: Database Technology Group. This was recommended in the discussions around the ARC case for BDB 4.7 (LSARC/2008/570). 3.3. Business Justification: We want to reduce the amount of resources needed to sustain the old 4.2 release in the future. 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: We want to remove 4.2 from Nevada before FCS in 2010. We also want to include the EOF announcement in the S10U7 release notes. Deadline is March 30, 08. 3.6. How will you know when you are done?: When 4.2 has been removed from the ONNV consolidation. 4. Technical Description: 4.1. Details: This project will remove the 4.2 software from the following packages delivered to Nevada: SUNWbdb - Berkeley DB for C/C++ applications SUNWbdbj - Berkeley DB for Java applications 4.2. Bug/RFE Number(s): 6813821 4.3. Doc Impact: We will announce the EOL of 4.2 in S10U7 release notes. 4.4. Admin/Config Impact: None. 4.5. HA Impact: N/A 4.6. I18N/L10N Impact: No. 4.7. Packaging & Delivery: SUNWbdb - Berkeley DB for C/C++ applications SUNWbdbj - Berkeley DB for Java applications 4.7.1. Packages: Cluster id: SUNWCbdb Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq Cluster name: BerkeleyDB-Base Packages: SUNWbdb, SUNWbdbj 4.7.2. Package Layout For both the Solaris updates and Nevada, BDB 4.2 is currently installed under: /usr/lib/bdb - c utilities /usr/lib - libraries (versioned ie: libdb.so.1, libdb_java.so.1) /usr/share - db.jar In Nevada, BDB 4.7 is delivered under: /usr/lib/bdb47 - c utilities /usr/lib - libraries (versioned ie: libdb.so.5, libdb_java.so.5) /usr/share/bdb47 - db.jar 4.7.3. Proposed change for Nevada delivery We will update both packages, removing the 4.2 software prior to integrating into Nevada. See [1] for new package layout. 4.8. Upgrading Nevada customers using 4.2 must upgrade their products to use 4.7. As mentioned above, Evolution, our sole customer, has already upgraded their product. The topic of upgrading from 4.2 to 4.7 was discussed in LSARC 2008/570, below is the relevant section from that case: "The BDB software does not automatically inform applications that a new release is available. The decision to upgrade must be made by the customer. Existing applications will continue to access the old library (4.2) until the user performs the manual steps required to upgrade which include linking to the new library and recompiling. Before performing an upgrade customers must backup their database and log files. The upgrade process for the Berkeley database requires that customers perform a number of manual steps. These steps are clearly documented in Chapter 31 of BDB's Reference manual and must be followed by the customer. http://www.oracle.com/technology/documentation/berkeley-db/db/ref/toc.html The Berkeley database does provided a db_upgrade utility which must be used as part of the upgrade procedure. The 4.7 release introduces a number of modifications to existing APIs in the form of method name changes, and new parameters. These incompatibilities with the previous release may be transparent to a customer's application, depending on how the application is coded. An example of an API change in moving from 4.2 to 4.7: DB Cursor APIs were renamed from (for example) dbc->c_close() to dbc->close(). All code referencing these APIs would have to be updated. As part of the upgrade procedure each customer must determine whether their application requires modification based on changes introduced by 4.7. Again, this information is available in BDB's reference manual." 4.9. Interfaces: All interfaces provided by the 4.2 software will be deleted. See Appendix A for full list. 4.10. Security Impact: No impact. 5. Reference Documents: Berkeley DB Public Websites: http://www.oracle.com/technology/products/berkeley-db/index.html Berkeley DB 4.7.25 Release Notes: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html References: [1] ./pkgmaps.txt 6. Resources and Schedule: 6.1. Projected Availability: This project will be included in Nevada. This project will not be included in S10, note S10 include BDB 4.2 but not 4.7. This project will not be included in OpenSolaris. 6.2. Cost of Effort: Minimal; just removal of a component within packages. 6.3. Cost of Capital Resources: None. 6.4.1. Consolidation or Component Name: ON 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: BDB 4.7.25 binaries are available to test. 7.2. Prototype Cost: Minimal. Appendix A FULL LIST of EXPORTED INTERFACES in BDB 4.2.52: Proposed Former Stability Interface Stability Classification Name Classification and Other Comments ------------------ ------------- ---------------------------------- C API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris C++ API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris Java API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris TCL API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris DB_HOME env Obsolete Formerly External, Removed in a Variable Volatile Minor release of Solaris Used to configure the location of db files. DB_CONFIG Obsolete Formerly External, Removed in a config file Volatile Minor release of Solaris Used to configure a database database file Obsolete Removed in a Minor release of Solaris Project Private transaction log Obsolete Removed in a Minor release of Solaris Project Private temporary backing Obsolete Removed in a Minor release of Solaris files Project Private db_archive Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_checkpoint Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_deadlock Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_dump Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_load Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_printlog Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_recover Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_stat Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_upgrade Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_verify Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris --Boundary_(ID_Lq5+sv/c2iMYKdAdPTkRYQ)-- From John.Fischer@sun.com Mon Mar 23 11:31:03 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n2NIV3do000287 for ; Mon, 23 Mar 2009 11:31:03 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n2NIV2R0028272 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Mon, 23 Mar 2009 11:31:02 -0700 (PDT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KGZ00H5R23QXP00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 11:31:02 -0700 (PDT) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KGZ00DYB23PKU80@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 11:31:01 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n2NIV1Qg027736 for ; Mon, 23 Mar 2009 18:31:01 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KGZ006000J3YX00@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 12:31:01 -0600 (MDT) Received: from [192.168.10.7] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KGZ000LV23CI8B0@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 12:30:49 -0600 (MDT) Date: Mon, 23 Mar 2009 11:29:55 -0700 From: John Fischer Subject: +1 on LSARC/2009/166 (EOF of BDB 4.2)? Sender: John.Fischer@sun.com To: lsarc-ext@sun.com Cc: John.Fischer@sun.com, Karen Langford Reply-to: John.Fischer@sun.com Message-id: <49C7D523.8030009@sun.com> MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_oAYnlUxaxEHxXRGRdIhcNg)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.18 (X11/20090211) Status: RO Content-Length: 11613 This is a multi-part message in MIME format. --Boundary_(ID_oAYnlUxaxEHxXRGRdIhcNg) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT All, I still have an empty mail log for the EOL of BDB 4.2 thus need a +1. We (LSARC) approved BDB 4.7 in (2008/570). That case included a migration tool from BDB 4.2 to BDB 4.7. This case deprecates the interfaces of BDB 4.2 in a Patch release of Solaris (i.e., Solaris 10 Update) and removes them in a Minor release of Solaris (i.e., Solaris Nevada). The case will provide the necessary documentation for the Patch release of Solaris. The case directory shows the package map entries after BDB 4.2 is removed. I have attached the project proposal to this email for your convience. Thanks, John --Boundary_(ID_oAYnlUxaxEHxXRGRdIhcNg) Content-type: text/plain; name=eol_proposal.txt Content-transfer-encoding: 7BIT Content-disposition: inline; filename=eol_proposal.txt Template Version: @(#)onepager.txt 1.35 07/11/07 SMI Copyright 2007 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: EOL of Berkeley DB 4.2 in Solaris. 1.2. Name of Document Author/Supplier: Karen Langford 1.3. Date of This Document: 03/05/09 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Database 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: Jeffrey.Pugh@sun.com 1.4.4. The name of your business unit: Software 1.5. Email Aliases: 1.5.1. Responsible Manager: Lars.Heill@sun.com 1.5.2. Responsible Engineer: Karen.Langford@sun.com 1.5.3. Marketing Manager: Rebecca.Hansen@sun.com 1.5.4. Interest List: sleepycat-productgroup-users@sun.com 2. Project Summary 2.1. Project Description: The Berkeley DB (BDB) 4.2 release was approved by ARC back in 2003 and integrated into Nevada and Solaris in 2007. In 2008 the latest release of Berkeley DB 4.7 was approved by ARC and integrated into Nevada along with the old 4.2 release. This project proposes the EOL and removal of the 4.2 release from Nevada. 2.2. Previous relevant ARC cases LSARC/2003/585 BDB 4.2 - Integrated into Solaris 10 and Nevada LSARC/2008/570 BDB 4.7 - Integrated along with BDB 4.2 into Nevada Note BDB 4.2 is not in OpenSolaris, neither is 4.7. 2.3. Risks and Assumptions: As we propose to leave 4.2 in the Solaris Updates we see no risks there. We will commit to delivering critical bug fixes for the duration of the Update's Active Service Life. We also see no risk in regards to removing 4.2 from Nevada as S11 has not been offically released. We contacted our sole Nevada customer, Evolution, and they confirmed that they have upgraded their product to use 4.7. 3. Business Summary 3.1. Problem Area: As mentioned above we foresee no problems with removing 4.2 from Nevada. 3.2. Market/Requester: Database Technology Group. This was recommended in the discussions around the ARC case for BDB 4.7 (LSARC/2008/570). 3.3. Business Justification: We want to reduce the amount of resources needed to sustain the old 4.2 release in the future. 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: We want to remove 4.2 from Nevada before FCS in 2010. We also want to include the EOF announcement in the S10U7 release notes. Deadline is March 30, 08. 3.6. How will you know when you are done?: When 4.2 has been removed from the ONNV consolidation. 4. Technical Description: 4.1. Details: This project will remove the 4.2 software from the following packages delivered to Nevada: SUNWbdb - Berkeley DB for C/C++ applications SUNWbdbj - Berkeley DB for Java applications 4.2. Bug/RFE Number(s): 6813821 4.3. Doc Impact: We will announce the EOL of 4.2 in S10U7 release notes. 4.4. Admin/Config Impact: None. 4.5. HA Impact: N/A 4.6. I18N/L10N Impact: No. 4.7. Packaging & Delivery: SUNWbdb - Berkeley DB for C/C++ applications SUNWbdbj - Berkeley DB for Java applications 4.7.1. Packages: Cluster id: SUNWCbdb Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq Cluster name: BerkeleyDB-Base Packages: SUNWbdb, SUNWbdbj 4.7.2. Package Layout For both the Solaris updates and Nevada, BDB 4.2 is currently installed under: /usr/lib/bdb - c utilities /usr/lib - libraries (versioned ie: libdb.so.1, libdb_java.so.1) /usr/share - db.jar In Nevada, BDB 4.7 is delivered under: /usr/lib/bdb47 - c utilities /usr/lib - libraries (versioned ie: libdb.so.5, libdb_java.so.5) /usr/share/bdb47 - db.jar 4.7.3. Proposed change for Nevada delivery We will update both packages, removing the 4.2 software prior to integrating into Nevada. See [1] for new package layout. 4.8. Upgrading Nevada customers using 4.2 must upgrade their products to use 4.7. As mentioned above, Evolution, our sole customer, has already upgraded their product. The topic of upgrading from 4.2 to 4.7 was discussed in LSARC 2008/570, below is the relevant section from that case: "The BDB software does not automatically inform applications that a new release is available. The decision to upgrade must be made by the customer. Existing applications will continue to access the old library (4.2) until the user performs the manual steps required to upgrade which include linking to the new library and recompiling. Before performing an upgrade customers must backup their database and log files. The upgrade process for the Berkeley database requires that customers perform a number of manual steps. These steps are clearly documented in Chapter 31 of BDB's Reference manual and must be followed by the customer. http://www.oracle.com/technology/documentation/berkeley-db/db/ref/toc.html The Berkeley database does provided a db_upgrade utility which must be used as part of the upgrade procedure. The 4.7 release introduces a number of modifications to existing APIs in the form of method name changes, and new parameters. These incompatibilities with the previous release may be transparent to a customer's application, depending on how the application is coded. An example of an API change in moving from 4.2 to 4.7: DB Cursor APIs were renamed from (for example) dbc->c_close() to dbc->close(). All code referencing these APIs would have to be updated. As part of the upgrade procedure each customer must determine whether their application requires modification based on changes introduced by 4.7. Again, this information is available in BDB's reference manual." 4.9. Interfaces: All interfaces provided by the 4.2 software will be deleted. See Appendix A for full list. 4.10. Security Impact: No impact. 5. Reference Documents: Berkeley DB Public Websites: http://www.oracle.com/technology/products/berkeley-db/index.html Berkeley DB 4.7.25 Release Notes: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html References: [1] ./pkgmaps.txt 6. Resources and Schedule: 6.1. Projected Availability: This project will be included in Nevada. This project will not be included in S10, note S10 include BDB 4.2 but not 4.7. This project will not be included in OpenSolaris. 6.2. Cost of Effort: Minimal; just removal of a component within packages. 6.3. Cost of Capital Resources: None. 6.4.1. Consolidation or Component Name: ON 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: N/A 6.4.5. Is this a necessary project for OEM agreements: No 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: BDB 4.7.25 binaries are available to test. 7.2. Prototype Cost: Minimal. Appendix A FULL LIST of EXPORTED INTERFACES in BDB 4.2.52: Proposed Former Stability Interface Stability Classification Name Classification and Other Comments ------------------ ------------- ---------------------------------- C API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris C++ API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris Java API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris TCL API Obsolete Formerly External, Removed in a Volatile Minor release of Solaris DB_HOME env Obsolete Formerly External, Removed in a Variable Volatile Minor release of Solaris Used to configure the location of db files. DB_CONFIG Obsolete Formerly External, Removed in a config file Volatile Minor release of Solaris Used to configure a database database file Obsolete Removed in a Minor release of Solaris Project Private transaction log Obsolete Removed in a Minor release of Solaris Project Private temporary backing Obsolete Removed in a Minor release of Solaris files Project Private db_archive Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_checkpoint Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_deadlock Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_dump Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_load Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_printlog Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_recover Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_stat Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_upgrade Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris db_verify Obsolete Formerly Unstable, Removed in a Uncommitted minor release of Solaris --Boundary_(ID_oAYnlUxaxEHxXRGRdIhcNg)-- From mac@sun.com Mon Mar 23 11:44:30 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n2NIiT89001408 for ; Mon, 23 Mar 2009 11:44:30 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n2NIiPFM011927; Mon, 23 Mar 2009 18:44:29 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KGZ00A0B2Q4LU00@nwk-avmta-2.sfbay.sun.com>; Mon, 23 Mar 2009 11:44:28 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KGZ004RF2Q484A0@nwk-avmta-2.sfbay.sun.com>; Mon, 23 Mar 2009 11:44:28 -0700 (PDT) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n2NIiSnc002089; Mon, 23 Mar 2009 18:44:28 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KGZ00M002ILMW00@mail-amer.sun.com>; Mon, 23 Mar 2009 12:44:28 -0600 (MDT) Received: from [10.65.84.224] ([unknown] [166.196.160.59]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KGZ007FE2PM19D0@mail-amer.sun.com>; Mon, 23 Mar 2009 12:44:21 -0600 (MDT) Date: Mon, 23 Mar 2009 12:44:11 -0600 From: Mobile Mark Subject: Re: +1 on LSARC/2009/166 (EOF of BDB 4.2)? In-reply-to: <49C7D523.8030009@sun.com> Sender: Mark.Carlson@sun.com To: John Fischer Cc: "lsarc-ext@sun.com" , John Fischer , Karen Langford Message-id: <63BAD87D-3B70-49CA-9286-DE63930AF97A@sun.com> MIME-version: 1.0 X-Mailer: iPhone Mail (5H11) Content-type: text/plain; delsp=yes; format=flowed; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49C7D523.8030009@sun.com> Status: RO Content-Length: 12059 OK. I will +1 this. -- mark On Mar 23, 2009, at 12:29 PM, John Fischer wrote: > All, > > I still have an empty mail log for the EOL of BDB 4.2 thus > need a +1. > > We (LSARC) approved BDB 4.7 in (2008/570). That case included > a migration tool from BDB 4.2 to BDB 4.7. This case deprecates > the interfaces of BDB 4.2 in a Patch release of Solaris (i.e., > Solaris 10 Update) and removes them in a Minor release of Solaris > (i.e., Solaris Nevada). The case will provide the necessary > documentation for the Patch release of Solaris. The case directory > shows the package map entries after BDB 4.2 is removed. > > I have attached the project proposal to this email for your convience. > > Thanks, > > John > > > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > EOL of Berkeley DB 4.2 in Solaris. > > 1.2. Name of Document Author/Supplier: > Karen Langford > > 1.3. Date of This Document: > 03/05/09 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > > Database 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: > > Jeffrey.Pugh@sun.com > > 1.4.4. The name of your business unit: > > Software > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: Lars.Heill@sun.com > 1.5.2. Responsible Engineer: Karen.Langford@sun.com > 1.5.3. Marketing Manager: Rebecca.Hansen@sun.com > 1.5.4. Interest List: sleepycat-productgroup-users@sun.com > > 2. Project Summary > > 2.1. Project Description: > > The Berkeley DB (BDB) 4.2 release was approved by ARC back in > 2003 and integrated into Nevada and Solaris in 2007. > > In 2008 the latest release of Berkeley DB 4.7 was approved > by ARC and integrated into Nevada along with the old 4.2 release. > > This project proposes the EOL and removal of the 4.2 release from > Nevada. > > > 2.2. Previous relevant ARC cases > > LSARC/2003/585 BDB 4.2 - Integrated into Solaris 10 and Nevada > LSARC/2008/570 BDB 4.7 - Integrated along with BDB 4.2 into > Nevada > > Note BDB 4.2 is not in OpenSolaris, neither is 4.7. > > 2.3. Risks and Assumptions: > > As we propose to leave 4.2 in the Solaris Updates we see no > risks > there. We will commit to delivering critical bug fixes for the > duration > of the Update's Active Service Life. > > We also see no risk in regards to removing 4.2 from Nevada as S11 > has > not been offically released. We contacted our sole Nevada customer, > Evolution, and they confirmed that they have upgraded their product > to use 4.7. > > > 3. Business Summary > > 3.1. Problem Area: > > As mentioned above we foresee no problems with removing 4.2 > from Nevada. > > 3.2. Market/Requester: > > Database Technology Group. > > This was recommended in the discussions around the ARC case for > BDB 4.7 (LSARC/2008/570). > > 3.3. Business Justification: > > We want to reduce the amount of resources needed to sustain > the old 4.2 > release in the future. > > 3.4. Competitive Analysis: > > N/A > > 3.5. Opportunity Window/Exposure: > > We want to remove 4.2 from Nevada before FCS in 2010. > > We also want to include the EOF announcement in the S10U7 release > notes. > Deadline is March 30, 08. > > > 3.6. How will you know when you are done?: > > When 4.2 has been removed from the ONNV consolidation. > > > 4. Technical Description: > > 4.1. Details: > > This project will remove the 4.2 software from the following > packages > delivered to Nevada: > > SUNWbdb - Berkeley DB for C/C++ applications > SUNWbdbj - Berkeley DB for Java applications > > > 4.2. Bug/RFE Number(s): > > 6813821 > > 4.3. Doc Impact: > > We will announce the EOL of 4.2 in S10U7 release notes. > > 4.4. Admin/Config Impact: > > None. > > 4.5. HA Impact: > > N/A > > 4.6. I18N/L10N Impact: > > No. > > 4.7. Packaging & Delivery: > > SUNWbdb - Berkeley DB for C/C++ applications > SUNWbdbj - Berkeley DB for Java applications > > > 4.7.1. Packages: > > Cluster id: SUNWCbdb > Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq > Cluster name: BerkeleyDB-Base > Packages: SUNWbdb, SUNWbdbj > > > 4.7.2. Package Layout > > For both the Solaris updates and Nevada, BDB 4.2 is currently > installed under: > /usr/lib/bdb - c utilities > /usr/lib - libraries (versioned ie: libdb.so.1, > libdb_java.so.1) > /usr/share - db.jar > > In Nevada, BDB 4.7 is delivered under: > /usr/lib/bdb47 - c utilities > /usr/lib - libraries (versioned ie: libdb.so.5, > libdb_java.so.5) > /usr/share/bdb47 - db.jar > > > 4.7.3. Proposed change for Nevada delivery > > We will update both packages, removing the 4.2 software prior to > integrating > into Nevada. See [1] for new package layout. > > > 4.8. Upgrading > > Nevada customers using 4.2 must upgrade their products to use > 4.7. As > mentioned above, Evolution, our sole customer, has already > upgraded their > product. > > The topic of upgrading from 4.2 to 4.7 was discussed in LSARC > 2008/570, > below is the relevant section from that case: > > "The BDB software does not automatically inform applications > that a new > release is available. The decision to upgrade must be made by the > customer. > Existing applications will continue to access the old library > (4.2) until > the user performs the manual steps required to upgrade which > include > linking to the new library and recompiling. > > Before performing an upgrade customers must backup their > database and > log files. > > The upgrade process for the Berkeley database requires that > customers > perform a number of manual steps. These steps are clearly > documented > in Chapter 31 of BDB's Reference manual and must be followed > by the customer. > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/toc.html > > The Berkeley database does provided a db_upgrade utility > which must be > used as part of the upgrade procedure. > > The 4.7 release introduces a number of modifications to > existing APIs > in the form of method name changes, and new parameters. These > incompatibilities with the previous release may be transparent to a > customer's application, depending on how the application is coded. > > An example of an API change in moving from 4.2 to 4.7: DB > Cursor APIs > were renamed from (for example) dbc->c_close() to dbc- > >close(). All code > referencing these APIs would have to be updated. > > As part of the upgrade procedure each customer must determine > whether > their application requires modification based on changes > introduced by 4.7. > Again, this information is available in BDB's reference > manual." > > > 4.9. Interfaces: > > All interfaces provided by the 4.2 software will be deleted. > See Appendix A > for full list. > > 4.10. Security Impact: > > No impact. > > > 5. Reference Documents: > > Berkeley DB Public Websites: > > http://www.oracle.com/technology/products/berkeley-db/index.html > > > Berkeley DB 4.7.25 Release Notes: > > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html > > > References: > > [1] ./pkgmaps.txt > > > 6. Resources and Schedule: > > 6.1. Projected Availability: > > This project will be included in Nevada. > > This project will not be included in S10, note S10 include BDB > 4.2 but not 4.7. > > This project will not be included in OpenSolaris. > > 6.2. Cost of Effort: > > Minimal; just removal of a component within packages. > > 6.3. Cost of Capital Resources: > > None. > > 6.4.1. Consolidation or Component Name: > > ON > > 6.4.3. Type of CPT Review and Approval expected: > > FastTrack > > 6.4.4. Project Boundary Conditions: > > N/A > > 6.4.5. Is this a necessary project for OEM agreements: > > No > > > 6.5. ARC review type: > > FastTrack > > > > 7. Prototype Availability: > > 7.1. Prototype Availability: > > BDB 4.7.25 binaries are available to test. > > > 7.2. Prototype Cost: > > Minimal. > > > Appendix A > > FULL LIST of EXPORTED INTERFACES in BDB 4.2.52: > > Proposed Former Stability > Interface Stability Classification > Name Classification and Other Comments > ------------------ ------------- > ---------------------------------- > C API Obsolete Formerly External, Removed > in a > Volatile Minor release of Solaris > C++ API Obsolete Formerly External, Removed > in a > Volatile Minor release of Solaris > Java API Obsolete Formerly External, Removed in a > Volatile Minor release of Solaris > TCL API Obsolete Formerly External, > Removed in a > Volatile Minor release of Solaris > DB_HOME env Obsolete Formerly External, > Removed in a > Variable Volatile Minor release of Solaris > Used to configure the > location of db files. > > DB_CONFIG Obsolete Formerly External, > Removed in a > config file Volatile Minor release of Solaris > Used to configure a > database > > database file Obsolete Removed in a Minor > release of Solaris > Project Private > transaction log Obsolete Removed in a Minor > release of Solaris > Project Private > temporary backing Obsolete Removed in a Minor > release of Solaris > files Project Private > > db_archive Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_checkpoint Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_deadlock Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_dump Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_load Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_printlog Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_recover Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_stat Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_upgrade Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > db_verify Obsolete Formerly Unstable, > Removed in a > Uncommitted minor release of Solaris > From margot.miller@sun.com Mon Mar 23 11:45:45 2009 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 n2NIjjRG001518 for ; Mon, 23 Mar 2009 11:45:45 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n2NIjZR8011379; Tue, 24 Mar 2009 02:45:41 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KGZ00A0X2S3O600@nwk-avmta-2.sfbay.sun.com>; Mon, 23 Mar 2009 11:45:39 -0700 (PDT) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KGZ004K92S28EC0@nwk-avmta-2.sfbay.sun.com>; Mon, 23 Mar 2009 11:45:38 -0700 (PDT) Received: from [10.7.250.251] (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n2NIjZJa376220; Mon, 23 Mar 2009 11:45:36 -0700 (PDT) Date: Mon, 23 Mar 2009 11:41:16 -0700 From: Margot Miller Subject: Re: +1 on LSARC/2009/166 (EOF of BDB 4.2)? In-reply-to: <49C7D523.8030009@sun.com> To: John.Fischer@sun.com Cc: lsarc-ext@sun.com, Karen Langford Message-id: <49C7D7CC.90508@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49C7D523.8030009@sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 12066 +1 My only concern would be the migration/upgrade of customer data, but that looks like it is being addressed. Thanks Margot John Fischer wrote: > All, > > I still have an empty mail log for the EOL of BDB 4.2 thus > need a +1. > > We (LSARC) approved BDB 4.7 in (2008/570). That case included > a migration tool from BDB 4.2 to BDB 4.7. This case deprecates > the interfaces of BDB 4.2 in a Patch release of Solaris (i.e., > Solaris 10 Update) and removes them in a Minor release of Solaris > (i.e., Solaris Nevada). The case will provide the necessary > documentation for the Patch release of Solaris. The case directory > shows the package map entries after BDB 4.2 is removed. > > I have attached the project proposal to this email for your convience. > > Thanks, > > John > > > ------------------------------------------------------------------------ > > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > EOL of Berkeley DB 4.2 in Solaris. > > 1.2. Name of Document Author/Supplier: > Karen Langford > > 1.3. Date of This Document: > 03/05/09 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: > > Database 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: > > Jeffrey.Pugh@sun.com > > 1.4.4. The name of your business unit: > > Software > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: Lars.Heill@sun.com > 1.5.2. Responsible Engineer: Karen.Langford@sun.com > 1.5.3. Marketing Manager: Rebecca.Hansen@sun.com > 1.5.4. Interest List: sleepycat-productgroup-users@sun.com > > 2. Project Summary > > 2.1. Project Description: > > The Berkeley DB (BDB) 4.2 release was approved by ARC back in > 2003 and integrated into Nevada and Solaris in 2007. > > In 2008 the latest release of Berkeley DB 4.7 was approved > by ARC and integrated into Nevada along with the old 4.2 release. > > This project proposes the EOL and removal of the 4.2 release from > Nevada. > > > 2.2. Previous relevant ARC cases > > LSARC/2003/585 BDB 4.2 - Integrated into Solaris 10 and Nevada > LSARC/2008/570 BDB 4.7 - Integrated along with BDB 4.2 into Nevada > > Note BDB 4.2 is not in OpenSolaris, neither is 4.7. > > 2.3. Risks and Assumptions: > > As we propose to leave 4.2 in the Solaris Updates we see no risks > there. We will commit to delivering critical bug fixes for the duration > of the Update's Active Service Life. > > We also see no risk in regards to removing 4.2 from Nevada as S11 has > not been offically released. We contacted our sole Nevada customer, > Evolution, and they confirmed that they have upgraded their product > to use 4.7. > > > 3. Business Summary > > 3.1. Problem Area: > > As mentioned above we foresee no problems with removing 4.2 from Nevada. > > 3.2. Market/Requester: > > Database Technology Group. > > This was recommended in the discussions around the ARC case for > BDB 4.7 (LSARC/2008/570). > > 3.3. Business Justification: > > We want to reduce the amount of resources needed to sustain the old 4.2 > release in the future. > > 3.4. Competitive Analysis: > > N/A > > 3.5. Opportunity Window/Exposure: > > We want to remove 4.2 from Nevada before FCS in 2010. > > We also want to include the EOF announcement in the S10U7 release notes. > Deadline is March 30, 08. > > > 3.6. How will you know when you are done?: > > When 4.2 has been removed from the ONNV consolidation. > > > 4. Technical Description: > > 4.1. Details: > > This project will remove the 4.2 software from the following packages > delivered to Nevada: > > SUNWbdb - Berkeley DB for C/C++ applications > SUNWbdbj - Berkeley DB for Java applications > > > 4.2. Bug/RFE Number(s): > > 6813821 > > 4.3. Doc Impact: > > We will announce the EOL of 4.2 in S10U7 release notes. > > 4.4. Admin/Config Impact: > > None. > > 4.5. HA Impact: > > N/A > > 4.6. I18N/L10N Impact: > > No. > > 4.7. Packaging & Delivery: > > SUNWbdb - Berkeley DB for C/C++ applications > SUNWbdbj - Berkeley DB for Java applications > > > 4.7.1. Packages: > > Cluster id: SUNWCbdb > Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq > Cluster name: BerkeleyDB-Base > Packages: SUNWbdb, SUNWbdbj > > > 4.7.2. Package Layout > > For both the Solaris updates and Nevada, BDB 4.2 is currently installed under: > /usr/lib/bdb - c utilities > /usr/lib - libraries (versioned ie: libdb.so.1, libdb_java.so.1) > /usr/share - db.jar > > In Nevada, BDB 4.7 is delivered under: > /usr/lib/bdb47 - c utilities > /usr/lib - libraries (versioned ie: libdb.so.5, libdb_java.so.5) > /usr/share/bdb47 - db.jar > > > 4.7.3. Proposed change for Nevada delivery > > We will update both packages, removing the 4.2 software prior to integrating > into Nevada. See [1] for new package layout. > > > 4.8. Upgrading > > Nevada customers using 4.2 must upgrade their products to use 4.7. As > mentioned above, Evolution, our sole customer, has already upgraded their > product. > > The topic of upgrading from 4.2 to 4.7 was discussed in LSARC 2008/570, > below is the relevant section from that case: > > "The BDB software does not automatically inform applications that a new > release is available. The decision to upgrade must be made by the customer. > Existing applications will continue to access the old library (4.2) until > the user performs the manual steps required to upgrade which include > linking to the new library and recompiling. > > Before performing an upgrade customers must backup their database and > log files. > > The upgrade process for the Berkeley database requires that customers > perform a number of manual steps. These steps are clearly documented > in Chapter 31 of BDB's Reference manual and must be followed by the customer. > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/toc.html > > The Berkeley database does provided a db_upgrade utility which must be > used as part of the upgrade procedure. > > The 4.7 release introduces a number of modifications to existing APIs > in the form of method name changes, and new parameters. These > incompatibilities with the previous release may be transparent to a > customer's application, depending on how the application is coded. > > An example of an API change in moving from 4.2 to 4.7: DB Cursor APIs > were renamed from (for example) dbc->c_close() to dbc->close(). All code > referencing these APIs would have to be updated. > > As part of the upgrade procedure each customer must determine whether > their application requires modification based on changes introduced by 4.7. > Again, this information is available in BDB's reference manual." > > > 4.9. Interfaces: > > All interfaces provided by the 4.2 software will be deleted. See Appendix A > for full list. > > 4.10. Security Impact: > > No impact. > > > 5. Reference Documents: > > Berkeley DB Public Websites: > > http://www.oracle.com/technology/products/berkeley-db/index.html > > > Berkeley DB 4.7.25 Release Notes: > > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html > > > References: > > [1] ./pkgmaps.txt > > > 6. Resources and Schedule: > > 6.1. Projected Availability: > > This project will be included in Nevada. > > This project will not be included in S10, note S10 include BDB 4.2 but not 4.7. > > This project will not be included in OpenSolaris. > > 6.2. Cost of Effort: > > Minimal; just removal of a component within packages. > > 6.3. Cost of Capital Resources: > > None. > > 6.4.1. Consolidation or Component Name: > > ON > > 6.4.3. Type of CPT Review and Approval expected: > > FastTrack > > 6.4.4. Project Boundary Conditions: > > N/A > > 6.4.5. Is this a necessary project for OEM agreements: > > No > > > 6.5. ARC review type: > > FastTrack > > > > 7. Prototype Availability: > > 7.1. Prototype Availability: > > BDB 4.7.25 binaries are available to test. > > > 7.2. Prototype Cost: > > Minimal. > > > Appendix A > > FULL LIST of EXPORTED INTERFACES in BDB 4.2.52: > > Proposed Former Stability > Interface Stability Classification > Name Classification and Other Comments > ------------------ ------------- ---------------------------------- > C API Obsolete Formerly External, Removed in a > Volatile Minor release of Solaris > C++ API Obsolete Formerly External, Removed in a > Volatile Minor release of Solaris > Java API Obsolete Formerly External, Removed in a > Volatile Minor release of Solaris > TCL API Obsolete Formerly External, Removed in a > Volatile Minor release of Solaris > DB_HOME env Obsolete Formerly External, Removed in a > Variable Volatile Minor release of Solaris > Used to configure the > location of db files. > > DB_CONFIG Obsolete Formerly External, Removed in a > config file Volatile Minor release of Solaris > Used to configure a > database > > database file Obsolete Removed in a Minor release of Solaris > Project Private > transaction log Obsolete Removed in a Minor release of Solaris > Project Private > temporary backing Obsolete Removed in a Minor release of Solaris > files Project Private > > db_archive Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_checkpoint Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_deadlock Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_dump Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_load Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_printlog Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_recover Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_stat Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_upgrade Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > db_verify Obsolete Formerly Unstable, Removed in a > Uncommitted minor release of Solaris > > From John.Fischer@sun.com Mon Mar 23 12:04:00 2009 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 n2NJ3xco004717 for ; Mon, 23 Mar 2009 12:04:00 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n2NJ3vk5021468 for <@sunmail2sca.sfbay.sun.com:lsarc-ext@sun.com>; Tue, 24 Mar 2009 03:03:58 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KGZ00L113MLTA00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 12:03:58 -0700 (PDT) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KGZ00LTM3MK7Z00@nwk-avmta-1.sfbay.Sun.COM> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 12:03:57 -0700 (PDT) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n2NJ3ul9011831 for ; Mon, 23 Mar 2009 19:03:56 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KGZ00A002RXIC00@mail-amer.sun.com> for lsarc-ext@sun.com (ORCPT lsarc-ext@sun.com); Mon, 23 Mar 2009 13:03:56 -0600 (MDT) Received: from [192.168.10.7] ([unknown] [76.20.56.47]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KGZ00LY73MGS3D0@mail-amer.sun.com>; Mon, 23 Mar 2009 13:03:52 -0600 (MDT) Date: Mon, 23 Mar 2009 12:02:58 -0700 From: John Fischer Subject: Re: +1 on LSARC/2009/166 (EOF of BDB 4.2)? In-reply-to: <49C7D7CC.90508@sun.com> Sender: John.Fischer@sun.com To: Margot Miller Cc: lsarc-ext@sun.com, Karen Langford Reply-to: John.Fischer@sun.com Message-id: <49C7DCE2.90207@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <49C7D523.8030009@sun.com> <49C7D7CC.90508@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20090211) Status: RO Content-Length: 13059 All, This case has been approved with +1s from Margot and Mark. Thanks, John Margot Miller wrote: > +1 > > My only concern would be the migration/upgrade of > customer data, but that looks like it is being addressed. > > Thanks > Margot > > > John Fischer wrote: >> All, >> >> I still have an empty mail log for the EOL of BDB 4.2 thus >> need a +1. >> >> We (LSARC) approved BDB 4.7 in (2008/570). That case included >> a migration tool from BDB 4.2 to BDB 4.7. This case deprecates >> the interfaces of BDB 4.2 in a Patch release of Solaris (i.e., >> Solaris 10 Update) and removes them in a Minor release of Solaris >> (i.e., Solaris Nevada). The case will provide the necessary >> documentation for the Patch release of Solaris. The case directory >> shows the package map entries after BDB 4.2 is removed. >> >> I have attached the project proposal to this email for your convience. >> >> Thanks, >> >> John >> >> >> ------------------------------------------------------------------------ >> >> Template Version: @(#)onepager.txt 1.35 07/11/07 SMI >> Copyright 2007 Sun Microsystems >> >> 1. Introduction >> 1.1. Project/Component Working Name: >> EOL of Berkeley DB 4.2 in Solaris. >> >> 1.2. Name of Document Author/Supplier: >> Karen Langford >> >> 1.3. Date of This Document: >> 03/05/09 >> >> 1.4. Name of Major Document Customer(s)/Consumer(s): >> 1.4.1. The PAC or CPT you expect to review your project: >> >> Database 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: >> >> Jeffrey.Pugh@sun.com >> >> 1.4.4. The name of your business unit: >> >> Software >> >> 1.5. Email Aliases: >> 1.5.1. Responsible Manager: Lars.Heill@sun.com >> 1.5.2. Responsible Engineer: Karen.Langford@sun.com >> 1.5.3. Marketing Manager: Rebecca.Hansen@sun.com >> 1.5.4. Interest List: sleepycat-productgroup-users@sun.com >> >> 2. Project Summary >> >> 2.1. Project Description: >> >> The Berkeley DB (BDB) 4.2 release was approved by ARC back in >> 2003 and integrated into Nevada and Solaris in 2007. >> >> In 2008 the latest release of Berkeley DB 4.7 was approved >> by ARC and integrated into Nevada along with the old 4.2 release. >> This project proposes the EOL and removal of the 4.2 release from >> Nevada. >> >> >> 2.2. Previous relevant ARC cases >> >> LSARC/2003/585 BDB 4.2 - Integrated into Solaris 10 and Nevada >> LSARC/2008/570 BDB 4.7 - Integrated along with BDB 4.2 into >> Nevada >> >> Note BDB 4.2 is not in OpenSolaris, neither is 4.7. >> >> 2.3. Risks and Assumptions: >> >> As we propose to leave 4.2 in the Solaris Updates we see no risks >> there. We will commit to delivering critical bug fixes for the >> duration of the Update's Active Service Life. >> >> We also see no risk in regards to removing 4.2 from Nevada as S11 >> has not been offically released. We contacted our sole Nevada >> customer, Evolution, and they confirmed that they have upgraded >> their product to use 4.7. >> >> 3. Business Summary >> >> 3.1. Problem Area: >> >> As mentioned above we foresee no problems with removing 4.2 >> from Nevada. >> >> 3.2. Market/Requester: >> >> Database Technology Group. >> >> This was recommended in the discussions around the ARC case for >> BDB 4.7 (LSARC/2008/570). >> >> 3.3. Business Justification: >> >> We want to reduce the amount of resources needed to sustain >> the old 4.2 release in the future. >> 3.4. Competitive Analysis: >> >> N/A >> >> 3.5. Opportunity Window/Exposure: >> >> We want to remove 4.2 from Nevada before FCS in 2010. >> >> We also want to include the EOF announcement in the S10U7 release >> notes. Deadline is March 30, 08. >> >> >> 3.6. How will you know when you are done?: >> >> When 4.2 has been removed from the ONNV consolidation. >> >> >> 4. Technical Description: >> >> 4.1. Details: >> >> This project will remove the 4.2 software from the following >> packages >> delivered to Nevada: >> >> SUNWbdb - Berkeley DB for C/C++ applications >> SUNWbdbj - Berkeley DB for Java applications >> >> 4.2. Bug/RFE Number(s): >> >> 6813821 4.3. Doc Impact: >> >> We will announce the EOL of 4.2 in S10U7 release notes. >> 4.4. Admin/Config Impact: >> >> None. >> 4.5. HA Impact: >> >> N/A >> 4.6. I18N/L10N Impact: >> >> No. >> 4.7. Packaging & Delivery: >> SUNWbdb - Berkeley DB for C/C++ applications >> SUNWbdbj - Berkeley DB for Java applications >> >> >> 4.7.1. Packages: >> >> Cluster id: SUNWCbdb >> Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq >> Cluster name: BerkeleyDB-Base Packages: SUNWbdb, SUNWbdbj >> >> >> 4.7.2. Package Layout >> >> For both the Solaris updates and Nevada, BDB 4.2 is currently >> installed under: >> /usr/lib/bdb - c utilities >> /usr/lib - libraries (versioned ie: libdb.so.1, >> libdb_java.so.1) >> /usr/share - db.jar >> >> In Nevada, BDB 4.7 is delivered under: >> /usr/lib/bdb47 - c utilities >> /usr/lib - libraries (versioned ie: libdb.so.5, >> libdb_java.so.5) >> /usr/share/bdb47 - db.jar >> >> >> 4.7.3. Proposed change for Nevada delivery >> >> We will update both packages, removing the 4.2 software prior to >> integrating into Nevada. See [1] for new package layout. >> >> >> 4.8. Upgrading >> >> Nevada customers using 4.2 must upgrade their products to use 4.7. As >> mentioned above, Evolution, our sole customer, has already >> upgraded their product. >> >> The topic of upgrading from 4.2 to 4.7 was discussed in LSARC >> 2008/570, below is the relevant section from that case: >> "The BDB software does not automatically inform applications >> that a new release is available. The decision to upgrade must be >> made by the customer. Existing applications will continue to >> access the old library (4.2) until the user performs the manual >> steps required to upgrade which include linking to the new library >> and recompiling. >> Before performing an upgrade customers must backup their >> database and >> log files. >> The upgrade process for the Berkeley database requires that >> customers >> perform a number of manual steps. These steps are clearly >> documented >> in Chapter 31 of BDB's Reference manual and must be followed >> by the customer. >> http://www.oracle.com/technology/documentation/berkeley-db/db/ref/toc.html >> >> >> The Berkeley database does provided a db_upgrade utility which >> must be >> used as part of the upgrade procedure. >> >> The 4.7 release introduces a number of modifications to >> existing APIs in the form of method name changes, and new >> parameters. These incompatibilities with the previous release may >> be transparent to a customer's application, depending on how the >> application is coded. >> An example of an API change in moving from 4.2 to 4.7: DB >> Cursor APIs were renamed from (for example) dbc->c_close() to >> dbc->close(). All code referencing these APIs would have to be >> updated. >> As part of the upgrade procedure each customer must determine >> whether their application requires modification based on >> changes introduced by 4.7. >> Again, this information is available in BDB's reference manual." >> >> >> 4.9. Interfaces: >> >> All interfaces provided by the 4.2 software will be deleted. >> See Appendix A >> for full list. >> >> 4.10. Security Impact: >> >> No impact. >> >> 5. Reference Documents: >> >> Berkeley DB Public Websites: >> >> >> http://www.oracle.com/technology/products/berkeley-db/index.html >> >> >> Berkeley DB 4.7.25 Release Notes: >> >> >> http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html >> >> >> References: >> >> [1] ./pkgmaps.txt >> >> >> 6. Resources and Schedule: >> >> 6.1. Projected Availability: >> >> This project will be included in Nevada. >> >> This project will not be included in S10, note S10 include BDB 4.2 >> but not 4.7. >> >> This project will not be included in OpenSolaris. >> >> 6.2. Cost of Effort: >> >> Minimal; just removal of a component within packages. >> >> 6.3. Cost of Capital Resources: >> >> None. >> >> 6.4.1. Consolidation or Component Name: >> >> ON >> >> 6.4.3. Type of CPT Review and Approval expected: >> >> FastTrack >> >> 6.4.4. Project Boundary Conditions: >> >> N/A >> >> 6.4.5. Is this a necessary project for OEM agreements: >> >> No >> >> >> 6.5. ARC review type: >> >> FastTrack >> >> >> >> 7. Prototype Availability: >> >> 7.1. Prototype Availability: >> >> BDB 4.7.25 binaries are available to test. >> >> >> 7.2. Prototype Cost: >> >> Minimal. >> >> >> Appendix A >> >> FULL LIST of EXPORTED INTERFACES in BDB 4.2.52: >> >> Proposed Former Stability >> Interface Stability Classification >> Name Classification and Other Comments >> ------------------ ------------- >> ---------------------------------- >> C API Obsolete Formerly External, Removed in >> a Volatile Minor release of Solaris >> C++ API Obsolete Formerly External, Removed >> in a Volatile Minor release of Solaris >> Java API Obsolete Formerly External, Removed in >> a Volatile Minor release of Solaris >> TCL API Obsolete Formerly External, >> Removed in a Volatile Minor release of >> Solaris >> DB_HOME env Obsolete Formerly External, >> Removed in a Variable Volatile Minor release of >> Solaris >> Used to configure the >> location of db files. >> >> DB_CONFIG Obsolete Formerly External, Removed in a >> config file Volatile Minor release of Solaris >> Used to configure a >> database >> >> database file Obsolete Removed in a Minor release of Solaris >> Project Private transaction >> log Obsolete Removed in a Minor release of Solaris >> Project Private >> temporary backing Obsolete Removed in a Minor release of Solaris >> files Project Private >> db_archive Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_checkpoint Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_deadlock Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_dump Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_load Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_printlog Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_recover Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_stat Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_upgrade Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> db_verify Obsolete Formerly Unstable, Removed >> in a >> Uncommitted minor release of Solaris >> >