From Thu Sep 11 13:46:11 2008 Date: Thu, 11 Sep 2008 13:46:11 -0700 (PDT) From: Postmaster Subject: Message from mail server Content-Length: 95 Mime-Version: 1.0 Status: RO X-IMAP: 1221165971 4 Delete. This is a system message. --END+PSEUDO-- From sacadmin Mon Sep 8 16:32:29 2008 Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m88NWTNf010305; Mon, 8 Sep 2008 16:32:29 -0700 (PDT) Received: (from kasso@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id m88NWTYu010301; Mon, 8 Sep 2008 16:32:29 -0700 (PDT) Date: Mon, 8 Sep 2008 16:32:29 -0700 (PDT) From: Chris Kasso Message-Id: <200809082332.m88NWTYu010301@sac.sfbay.sun.com> To: LSARC-record@sac.sfbay.sun.com Cc: kasso@sun.com Subject: Berkeley DB 4.7.25 [LSARC/2008/570 FastTrack timeout 09/16/2008] Content-Length: 557 Status: RO X-Status: $$$$ X-UID: 0000000001 Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Berkeley DB 4.7.25 1.2. Name of Document Author/Supplier: Author: Karen Langford 1.3 Date of This Document: 08 September, 2008 4. Technical Description See the case directory for more detail 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: unknown 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From sacadmin Mon Sep 8 16:41:04 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 m88Nf3ZT010473 for ; Mon, 8 Sep 2008 16:41:04 -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 m88Nev6p004890; Tue, 9 Sep 2008 07:40:59 +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 <0K6W00D07HS91M00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 08 Sep 2008 16:40:57 -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 <0K6W00MRZHS85QB0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 08 Sep 2008 16:40:57 -0700 (PDT) Received: from dm-usca15-11.red.iplanet.com (host-185-56-18-192.iplanet.com [192.18.56.185] (may be forged)) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m88Neu13008509; Mon, 08 Sep 2008 23:40:56 +0000 (GMT) Received: from aha.red.iplanet.com (aha [192.18.122.65]) by dm-usca15-11.red.iplanet.com (8.11.7p1+Sun/8.11.7/IPLANET,v1.2) with ESMTP id m88Netm19813; Mon, 08 Sep 2008 16:40:55 -0700 (PDT) Received: from aha.red.iplanet.com (localhost [127.0.0.1]) by aha.red.iplanet.com (8.13.8+Sun/8.13.8) with ESMTP id m88Net5i012105; Mon, 08 Sep 2008 16:40:55 -0700 (PDT) Date: Mon, 08 Sep 2008 16:40:55 -0700 From: Chris Kasso Subject: Berkeley DB 4.7.25 [LSARC/2008/570 FastTrack timeout 09/16/2008] To: lsarc@sun.com Cc: Lars.Heill@sun.com, karen.langford@sun.com Reply-to: Chris Kasso Message-id: <200809082340.m88Net5i012105@aha.red.iplanet.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Content-Length: 240 Status: RO X-Status: $$$$ X-UID: 0000000002 Folks, I'm sponsoring the following proposal on behalf of Karen Langford for FastTrack approval. The timer is set for 09/16/2008. Proposed release binding is Minor. http://sac.sfbay.sun.com/LSARC/2008/570/materials/proposal.txt Chris From sacadmin Mon Sep 8 16:46:59 2008 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 m88Nkxpp010596 for ; Mon, 8 Sep 2008 16:46:59 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m88Nkc4k012136; Tue, 9 Sep 2008 00:46:54 +0100 (BST) 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 <0K6W00D01I24LN00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 08 Sep 2008 16:46:52 -0700 (PDT) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K6W00MF1I235ND0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 08 Sep 2008 16:46:51 -0700 (PDT) Received: from mumak.SFBay.Sun.COM (mumak.SFBay.Sun.COM [129.146.229.4]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m88NkoAF025122; Mon, 08 Sep 2008 16:46:50 -0700 (PDT) Received: from mumak.SFBay.Sun.COM (mumak [127.0.0.1]) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id m88Nltxv007882; Mon, 08 Sep 2008 16:47:56 -0700 (PDT) Received: (from dduvall@localhost) by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3/Submit) id m88NltoN007881; Mon, 08 Sep 2008 16:47:55 -0700 (PDT) Date: Mon, 08 Sep 2008 16:47:55 -0700 From: Danek Duvall Subject: Re: Berkeley DB 4.7.25 [LSARC/2008/570 FastTrack timeout 09/16/2008] In-reply-to: <200809082340.m88Net5i012105@aha.red.iplanet.com> To: Chris Kasso Cc: lsarc@sun.com, Lars.Heill@sun.com, karen.langford@sun.com Message-id: <20080908234755.GD22821@mumak.SFBay.Sun.COM> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-PMX-Version: 5.4.1.325704 References: <200809082340.m88Net5i012105@aha.red.iplanet.com> User-Agent: Mutt/1.5.16 (2007-06-27) Content-Length: 353 Status: RO X-Status: $$$$ X-UID: 0000000003 On Mon, Sep 08, 2008 at 04:40:55PM -0700, Chris Kasso wrote: > http://sac.sfbay.sun.com/LSARC/2008/570/materials/proposal.txt For the ease of those of us who don't want to go crawling around in a web browser or in the case directory, and for external folks (or is this deliberately not an external case), could you inline the proposal? Thanks, Danek From sacadmin Mon Sep 8 17:08:43 2008 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 m8908gBP012160 for ; Mon, 8 Sep 2008 17:08:42 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m8908Xil019450; Tue, 9 Sep 2008 01:08:38 +0100 (BST) 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 <0K6W00F01J2EYW00@nwk-avmta-1.sfbay.Sun.COM>; Mon, 08 Sep 2008 17:08:38 -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 <0K6W00MHGJ2D5QE0@nwk-avmta-1.sfbay.Sun.COM>; Mon, 08 Sep 2008 17:08:37 -0700 (PDT) Received: from dm-usca19-13.red.iplanet.com (host-179-56-18-192.iplanet.com [192.18.56.179] (may be forged)) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m8908aKV015772; Tue, 09 Sep 2008 00:08:36 +0000 (GMT) Received: from aha.red.iplanet.com (aha [192.18.122.65]) by dm-usca19-13.red.iplanet.com (8.11.7p1+Sun/8.11.7/IPLANET,v1.2) with ESMTP id m8908as05236; Mon, 08 Sep 2008 17:08:36 -0700 (PDT) Received: from aha.red.iplanet.com (localhost [127.0.0.1]) by aha.red.iplanet.com (8.13.8+Sun/8.13.8) with ESMTP id m8908a0P012369; Mon, 08 Sep 2008 17:08:36 -0700 (PDT) Date: Mon, 08 Sep 2008 17:08:36 -0700 From: Chris Kasso Subject: Re: Berkeley DB 4.7.25 [LSARC/2008/570 FastTrack timeout 09/16/2008] In-reply-to: Danek Duvall 's message of Mon, 08 Sep 2008 16:47:55 PDT. To: Danek Duvall Cc: lsarc@sun.com, Lars.Heill@sun.com, Karen.Langford@sun.com Reply-to: Chris Kasso Message-id: <200809090008.m8908a0P012369@aha.red.iplanet.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Content-Length: 25897 Status: RO X-Status: $$$$ X-UID: 0000000004 For the firewall impaired... From: Danek Duvall Date: Mon, 08 Sep 2008 16:47:55 -0700 On Mon, Sep 08, 2008 at 04:40:55PM -0700, Chris Kasso wrote: > http://sac.sfbay.sun.com/LSARC/2008/570/materials/proposal.txt For the ease of those of us who don't want to go crawling around in a web browser or in the case directory, and for external folks (or is this deliberately not an external case), could you inline the proposal? Thanks, Danek =================================================== Berkeley DB (BDB) 4.7.25 ARC Proposal =================================================== =============== 1. Introduction =============== 1.1. Project/Component Working Name: Berkeley DB 4.7.25 1.2. Name of Document Author/Supplier: Karen Langford (karen.langford@sun.com) Lars Heill (lars.heill@sun.com) 1.3. Email Aliases: 1.3.1. Responsible Manager: yngve.svendsen@sun.com lars.heill@sun.com 1.3.2. Responsible Engineer: karen.langford@sun.com 1.3.3. Marketing Manager: 1.3.4. Interest List: karine.excoffier@sun.com matt.wall@sun.com ================== 2. Project Summary ================== 2.1. Project Description Currently, the Berkeley Database (BDB) ships within a number of Sun products. This ARC case is to establish BDB 4.7.25, the latest version of the Berkeley Database, as an accepted database technology for product use within Sun, including Solaris, and the Sun Java Enterprise System. The Berkeley Database is third party software owned by Oracle. We have a commercial license and support contract with Oracle to use the BDB source. We do no development, just RE work: compile, package and deliver the bits to our Sun internal customers, as well as integrate into Nevada. Our group has ARCed the BDB versions 4.2 and 4.5. Packages containing BDB 4.5 and 4.2 were integrated into Nevada in b91 (May 08) and made available internally to product teams. In the interim, Directory Server and Messaging Server approached us with a request for the 4.7 release. Both teams have strong business cases as to why they require 4.7 for their next product releases. This project proposes replacing BDB 4.5 with 4.7 and integrating into Nevada. We will continue to deliver BDB 4.2 to support those customers not willing to update. We are targeting Nevada b100 (10/06/08). BDB 4.7 is a minor update release. 2.2. Previous relevant ARC cases LSARC/2003/585 BDB 4.2 - Integrated into Solaris 10 and Nevada LSARC/2007/299 BDB 4.5 - Integrated along with BDB 4.2 into Nevada Note BDB is not in OpenSolaris. =================== 3. Business Summary =================== 3.1. Problem Area: We do not fore see problems with replacing BDB 4.5 with 4.7, as Evolution is the only BDB 4.5 user in Nevada todate, and they have been notified of the version change. 3.2. Requester: The requester is the Database Technology Group on behalf of the Messaging Server, Communications Suite and Directory Server product teams. 3.3. Business Justification: Copy of business justification sent to DBTG from Karine Excoffier (Engineering manager for Directory) and Matthew Wall (Engineering manager for Messaging - Communications Suite) Let me explain why Messaging Server, Communications Suite and Directory Server require the latest release of BDB to improve concurrency and performance. Messaging Server and Communications Suite do need concurrency and performance in the message store that is the heart of this product. BDB forms a critical part of the internal embedded message store and is fundamental to the performance requirements. Messaging customers are among the largest service providers (and biggest Sun software and hardware customers, including one that is billed over $1B annually) and have long been demanding optimal performance in message database transactions. The differences between performance in this space between earlier versions and the latest release are noticeable. Messaging team had hoped to have 4.6 included in its major revenue release scheduled for May 5th, and the fact that it is not in there will be a problem with these customers. Performance is also critical for Directory Server which consistently have to propose better performance to its customers (NSN, Sprint...). The next major release is planned in March 09. In addition, there are a number of other bug fix issues related to the particular version numbering, of course, including some fixes to regressions that other key customers have been waiting on for some time, but the business-critical issue is the enhanced performance we require to maintain our largest customers' business. We cannot afford to be trailing-edge in this area. 3.4. Opportunity Window/Exposure: We would like this ARC case approved by October 01, in order to make Nevada b100 and for Directory Server to incorporate BDB 4.7 into their minor release due out later this year and allow them to fully port their major release due in March 09. ======================== 4. Technical Description ======================== 4.1. Details Berkeley DB is a C-based, record-level database package. It allows very fast, vertically scalable, transactional access to persistent data. It is already in heavy use within Sun; in particular it is the underlying data store for Sun Java Directory Service. We will follow guidelines for package delivery and release versioning as agreed upon in LSARC 2007/299, including the continued delivery of the 4.2 release. Our customers, namely Directory Server and Messaging Server, are most interested in the bug fixes, and performance improvements introduced by the 4.7.25 release. Summary of new features are: + Numerous bug fixes + Major improvements to performance + Support for new platforms (WinCE, S60, Qualcomm's BREW) + Addition of verbose output tracing for filesystem operations. + Configuration enhancements to locking, logging and replication functions resulting in improved performance. + Addition of Java Direct Persistence Layer API which provides a mechanism for storing and managing Java class objects in a BDB database. For more information on the new features of BDB 4.7.25 please see http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.7.html http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.6.html 4.2. Bug/RFE Number(s): 6723517 4.3. Upgrading 4.3.1. Releases The majority of our customers still use the 4.2 release and have not migrated to 4.5. We will continue to deliver 4.2 for customers not ready to move to 4.7 in a transistion period before 4.2 is EOLed. Note 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. Installation of the new packages will not overwrite the existing 4.2 install, the new 4.7 version will install into a separate directory .../bdb47/... See the attached pkgmap for detailed layout. The issues regarding the delivery of multiple libraries, 4.2 and 4.7, and the upgrading procedures are the same as presented and discussed at the 4.5 ARC commitment hearing: http://sac.sfbay/arc/LSARC/2007/299/20080205.2007.299.commitment.mp3 Note our group plans to depreciate the 4.2 release in the near future. 4.3.2. Upgrading/Compatibility 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.5 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. [2] 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.4. I18N/L10N Impact: NA 4.5. Packages SUNWbdb - Berkeley DB for C/C++ applications SUNWbdbj - Berkeley DB for Java applications 4.5.1. Packaging & Delivery: For Solaris and Nevada: Cluster id: SUNWCbdb Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq Cluster name: BerkeleyDB-Base Packages: SUNWbdb, SUNWbdbj We will update packages with the new release. These packages will not overwrite an old install of BDB. 4.5.2. Package Layout 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 We propose to install BDB 4.7 under: /usr/lib/bdb47 - c utilities /usr/lib - libraries (versioned ie: libdb.so.5, libdb_java.so.5) /usr/share/bdb47 - db.jar The case materials also includes the list of related pkgmap files for all installed packages. [1] 4.6. Security Impact: NA 4.7. Interfaces The Berkeley Database is embedded software. The Berkeley Database is a third party product and according to our licensing agreement the interfaces cannot be made available directly to the customer. This has not changed. 4.7.1. New Components Two new components have been added to the 4.7 release. - Java Direct Persistence Layer(DPL) API. This API provides a mechanism for storing and managing Java class objects in a BDB database. http://www.oracle.com/technology/documentation/berkeley-db/db/java/index.html - db_codegen utility. Generates application code to create and configure Berkeley DB database environments and databases based on a simple description language. http://www.oracle.com/technology/documentation/berkeley-db/db/utility/db_codegen.html 4.7.2 Removed Components None. 4.7.3 Interfaces added EXPORTED INTERFACES: Proposed Former Stability Interface Stability Classification Name Classification and Other Comments ------------------ ------------- -------------- -------------------- Java DPL API Volatile External db_codegen Uncommitted Unstable See Appendix A for full BDB 4.7.25 Interface table. ====================== 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 http://www.oracle.com/technology/documentation/berkeley-db/db/ref/changelog/4.6.html References: [1] ./pkgmaps.txt [2] ./low_level_api_changes.txt ========================= 6. Resources and Schedule ========================= 6.1. Projected Availability This project will be included in Solaris Nevada. This project will not be included in S10, note S10 does include BDB 4.2. This project will not be included in OpenSolaris. 6.2. Cost of Effort Estimated at 2 person months. 6.3. Cost of Capital Resources Negligible. 6.4. ARC review type: [Standard/FastTrack/SelfReview] FastTrack ========================= 7. Prototype Availability ========================= 7.1. Prototype Availability BDB 4.7.25 binaries are available to test. 7.2. Prototype Cost Minimal. No changes to packaging has occurred. Appendix A FULL LIST of EXPORTED INTERFACES in BDB 4.7.25 : Proposed Former Stability Interface Stability Classification Name Classification and Other Comments ------------------ ------------- ---------------------------------- C API Volatile External C++ API Volatile External Java API Volatile External Java DPL API Volatile External TCL API Volatile External Repl API Volatile External DB_HOME env Volatile External, Used to configure the variable location of db files. DB_CONFIG Volatile External, Used to configure a config file database database file Project Private transaction log Project Private temporary backing Project Private files db_archive Uncommitted Unstable db_checkpoint Uncommitted Unstable db_codegen Uncommitted Unstable db_deadlock Uncommitted Unstable db_dump Uncommitted Unstable db_hotbackup Uncommitted Unstable db_load Uncommitted Unstable db_printlog Uncommitted Unstable db_recover Uncommitted Unstable db_stat Uncommitted Unstable db_upgrade Uncommitted Unstable db_verify Uncommitted Unstable pkgmaps.txt: Package Maps for Berkeley DB 4.7.25 =================================== SUNWbdbj (sparc) : 1 0 1 i copyright 93 8257 1219422312 1 i depend 72 6053 1219422312 1 i pkginfo 579 46827 1219422312 1 f none usr/lib/libdb_java.so.1 0755 root bin 1319904 10886 1219360598 1 f none usr/lib/libdb_java.so.5 0755 root bin 2254756 38097 1219419212 1 d none usr/lib/sparcv9 0755 root bin 1 f none usr/lib/sparcv9/libdb_java.so.1 0755 root bin 1433088 25197 1219362577 1 f none usr/lib/sparcv9/libdb_java.so.5 0755 root bin 2440592 43831 1219421454 1 d none usr/share/bdb47 0755 root bin 1 f none usr/share/bdb47/db.jar 0444 root bin 168889 23214 1219360651 1 f none usr/share/db.jar 0444 root bin 168889 23214 1219360651 SUNWbdb (sparc) : 1 0 1 i copyright 93 8257 1219422306 1 i depend 72 6053 1219422306 1 i pkginfo 579 46742 1219422306 1 d none usr/lib/bdb 0755 root bin 1 f none usr/lib/bdb/NOTICE 0444 root bin 384 36065 1219360667 1 f none usr/lib/bdb/db_archive 0555 root bin 11964 53004 1219360651 1 f none usr/lib/bdb/db_checkpoint 0555 root bin 15084 48487 1219360652 1 f none usr/lib/bdb/db_deadlock 0555 root bin 14756 31956 1219360652 1 f none usr/lib/bdb/db_dump 0555 root bin 19808 32635 1219360653 1 f none usr/lib/bdb/db_load 0555 root bin 27748 33784 1219360653 1 f none usr/lib/bdb/db_printlog 0555 root bin 15196 3286 1219360653 1 f none usr/lib/bdb/db_recover 0555 root bin 13040 57289 1219360654 1 f none usr/lib/bdb/db_stat 0555 root bin 33624 22707 1219360654 1 f none usr/lib/bdb/db_upgrade 0555 root bin 12368 17504 1219360655 1 f none usr/lib/bdb/db_verify 0555 root bin 14780 49461 1219360655 1 d none usr/lib/bdb47 0755 root bin 1 f none usr/lib/bdb47/NOTICE 0444 root bin 384 36065 1219419338 1 f none usr/lib/bdb47/db_archive 0555 root bin 13424 11297 1219419313 1 f none usr/lib/bdb47/db_checkpoint 0555 root bin 17140 42442 1219419313 1 f none usr/lib/bdb47/db_codegen 0555 root bin 29520 41250 1219419314 1 f none usr/lib/bdb47/db_deadlock 0555 root bin 17340 55674 1219419314 1 f none usr/lib/bdb47/db_dump 0555 root bin 19336 25159 1219419315 1 f none usr/lib/bdb47/db_hotbackup 0555 root bin 23484 33913 1219419315 1 f none usr/lib/bdb47/db_load 0555 root bin 30788 28338 1219419316 1 f none usr/lib/bdb47/db_printlog 0555 root bin 81984 52893 1219419316 1 f none usr/lib/bdb47/db_recover 0555 root bin 14868 36349 1219419317 1 f none usr/lib/bdb47/db_stat 0555 root bin 18412 25998 1219419317 1 f none usr/lib/bdb47/db_upgrade 0555 root bin 14228 4389 1219419318 1 f none usr/lib/bdb47/db_verify 0555 root bin 16712 41948 1219419318 1 f none usr/lib/libdb.so.1 0755 root bin 1190580 3286 1219360574 1 f none usr/lib/libdb.so.5 0755 root bin 2043144 63277 1219419176 1 d none usr/lib/sparcv9 0755 root bin 1 d none usr/lib/sparcv9/bdb 0755 root bin 1 f none usr/lib/sparcv9/bdb/NOTICE 0444 root bin 384 36065 1219362646 1 f none usr/lib/sparcv9/bdb/db_archive 0555 root bin 13168 16913 1219362632 1 f none usr/lib/sparcv9/bdb/db_checkpoint 0555 root bin 16888 10248 1219362632 1 f none usr/lib/sparcv9/bdb/db_deadlock 0555 root bin 16288 55921 1219362632 1 f none usr/lib/sparcv9/bdb/db_dump 0555 root bin 21848 32519 1219362633 1 f none usr/lib/sparcv9/bdb/db_load 0555 root bin 30744 62513 1219362633 1 f none usr/lib/sparcv9/bdb/db_printlog 0555 root bin 17176 33517 1219362634 1 f none usr/lib/sparcv9/bdb/db_recover 0555 root bin 14464 18169 1219362634 1 f none usr/lib/sparcv9/bdb/db_stat 0555 root bin 36520 34834 1219362635 1 f none usr/lib/sparcv9/bdb/db_upgrade 0555 root bin 13840 49665 1219362635 1 f none usr/lib/sparcv9/bdb/db_verify 0555 root bin 16320 18025 1219362636 1 d none usr/lib/sparcv9/bdb47 0755 root bin 1 f none usr/lib/sparcv9/bdb47/NOTICE 0444 root bin 384 36065 1219421580 1 f none usr/lib/sparcv9/bdb47/db_archive 0555 root bin 14720 38224 1219421558 1 f none usr/lib/sparcv9/bdb47/db_checkpoint 0555 root bin 19016 8418 1219421558 1 f none usr/lib/sparcv9/bdb47/db_codegen 0555 root bin 31704 20049 1219421558 1 f none usr/lib/sparcv9/bdb47/db_deadlock 0555 root bin 19296 19207 1219421559 1 f none usr/lib/sparcv9/bdb47/db_dump 0555 root bin 21344 5220 1219421559 1 f none usr/lib/sparcv9/bdb47/db_hotbackup 0555 root bin 26480 56582 1219421560 1 f none usr/lib/sparcv9/bdb47/db_load 0555 root bin 33648 49300 1219421560 1 f none usr/lib/sparcv9/bdb47/db_printlog 0555 root bin 91616 62188 1219421561 1 f none usr/lib/sparcv9/bdb47/db_recover 0555 root bin 16552 1883 1219421561 1 f none usr/lib/sparcv9/bdb47/db_stat 0555 root bin 19920 61928 1219421562 1 f none usr/lib/sparcv9/bdb47/db_upgrade 0555 root bin 15640 38447 1219421562 1 f none usr/lib/sparcv9/bdb47/db_verify 0555 root bin 18264 5867 1219421563 1 f none usr/lib/sparcv9/libdb.so.1 0755 root bin 1287792 36464 1219362553 1 f none usr/lib/sparcv9/libdb.so.5 0755 root bin 2185688 23872 1219421418 SUNWbdbj (x86) : 1 12299 1 i copyright 93 8257 1219421709 1 i depend 72 6053 1219421709 1 i pkginfo 594 47582 1219421709 1 d none usr/lib/amd64 0755 root bin 1 f none usr/lib/amd64/libdb_java.so.5 0755 root bin 2487080 56783 1219418762 1 f none usr/lib/libdb_java.so.1 0755 root bin 1266272 27189 1219420133 1 f none usr/lib/libdb_java.so.5 0755 root bin 2154468 9548 1219421127 1 d none usr/share/bdb47 0755 root bin 1 f none usr/share/bdb47/db.jar 0444 root bin 162644 48888 1219420166 1 f none usr/share/db.jar 0444 root bin 162644 48888 1219420166 SUNWbdb (x86) : 1 12196 1 i copyright 93 8257 1219421705 1 i depend 72 6053 1219421705 1 i pkginfo 594 47490 1219421705 1 d none usr/lib/amd64 0755 root bin 1 d none usr/lib/amd64/bdb47 0755 root bin 1 f none usr/lib/amd64/bdb47/NOTICE 0444 root bin 384 36065 1219418824 1 f none usr/lib/amd64/bdb47/db_archive 0555 root bin 15416 63919 1219418802 1 f none usr/lib/amd64/bdb47/db_checkpoint 0555 root bin 19800 61195 1219418802 1 f none usr/lib/amd64/bdb47/db_codegen 0555 root bin 33008 60708 1219418803 1 f none usr/lib/amd64/bdb47/db_deadlock 0555 root bin 19952 34488 1219418803 1 f none usr/lib/amd64/bdb47/db_dump 0555 root bin 21928 63205 1219418803 1 f none usr/lib/amd64/bdb47/db_hotbackup 0555 root bin 27616 21547 1219418803 1 f none usr/lib/amd64/bdb47/db_load 0555 root bin 34432 40316 1219418803 1 f none usr/lib/amd64/bdb47/db_printlog 0555 root bin 93432 55009 1219418804 1 f none usr/lib/amd64/bdb47/db_recover 0555 root bin 16912 36897 1219418804 1 f none usr/lib/amd64/bdb47/db_stat 0555 root bin 20472 17303 1219418804 1 f none usr/lib/amd64/bdb47/db_upgrade 0555 root bin 16288 1692 1219418804 1 f none usr/lib/amd64/bdb47/db_verify 0555 root bin 18936 47455 1219418804 1 f none usr/lib/amd64/libdb.so.5 0755 root bin 2218576 56036 1219418748 1 d none usr/lib/bdb 0755 root bin 1 f none usr/lib/bdb/NOTICE 0444 root bin 384 36065 1219420182 1 f none usr/lib/bdb/db_archive 0555 root bin 11076 42343 1219420167 1 f none usr/lib/bdb/db_checkpoint 0555 root bin 14448 47608 1219420167 1 f none usr/lib/bdb/db_deadlock 0555 root bin 13832 50772 1219420167 1 f none usr/lib/bdb/db_dump 0555 root bin 18884 2612 1219420167 1 f none usr/lib/bdb/db_load 0555 root bin 26556 37656 1219420168 1 f none usr/lib/bdb/db_printlog 0555 root bin 14296 21172 1219420168 1 f none usr/lib/bdb/db_recover 0555 root bin 12032 1036 1219420168 1 f none usr/lib/bdb/db_stat 0555 root bin 33296 46621 1219420169 1 f none usr/lib/bdb/db_upgrade 0555 root bin 11588 27951 1219420169 1 f none usr/lib/bdb/db_verify 0555 root bin 13976 6491 1219420169 1 d none usr/lib/bdb47 0755 root bin 1 f none usr/lib/bdb47/NOTICE 0444 root bin 384 36065 1219421213 1 f none usr/lib/bdb47/db_archive 0555 root bin 12544 423 1219421190 1 f none usr/lib/bdb47/db_checkpoint 0555 root bin 16472 33036 1219421190 1 f none usr/lib/bdb47/db_codegen 0555 root bin 28820 19583 1219421190 1 f none usr/lib/bdb47/db_deadlock 0555 root bin 16448 36407 1219421191 1 f none usr/lib/bdb47/db_dump 0555 root bin 18416 28003 1219421191 1 f none usr/lib/bdb47/db_hotbackup 0555 root bin 23576 47918 1219421191 1 f none usr/lib/bdb47/db_load 0555 root bin 29884 48093 1219421192 1 f none usr/lib/bdb47/db_printlog 0555 root bin 80344 18468 1219421192 1 f none usr/lib/bdb47/db_recover 0555 root bin 13804 49684 1219421192 1 f none usr/lib/bdb47/db_stat 0555 root bin 17164 53335 1219421193 1 f none usr/lib/bdb47/db_upgrade 0555 root bin 13444 31564 1219421193 1 f none usr/lib/bdb47/db_verify 0555 root bin 15956 50099 1219421193 1 f none usr/lib/libdb.so.1 0755 root bin 1145568 64032 1219420118 1 f none usr/lib/libdb.so.5 0755 root bin 1959944 40901 1219421101 low_level_api_changes.txt Low Level API Changes ===================== Below is the full list of API changes which a programmer upgrading from 4.2 -> 4.7 would need to know about as noted in Chapter 31 in the Reference Guide: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/toc.html Functions: + Run time functions db_env_set_func_map/db_env_set_func_unmap replaced with functions db_env_set_func_region_map/db_env_func_file_map. Methods: + Base replication methods rep_elect, rep_get_nsites, rep_set_nsites, rep_get_priority, rep_set_priority now take arguments of type u_int32_t rather than int. + DB Env method set_intermediate_dir replaced with set_intermediate_dir_mode. + Log Configuration method set_flags replaced with log_set_config. + The DBC handle methods have been renamed for consistency with the C++ and Java APIs. The change is the removal of the leading "C_" from the names, ie: DBC->c_close changed to DBC->close. + DB_MPOOLFILE->put takes a new parameter: a page priority. + DB_MPOOLFILE->set has been removed. + The envid parameter to DB_ENV->rep_process_message has been changed to "int" rather than "int *" + The envid parameter to DB_ENV->rep_elect has been removed. + DB_REP_FULL_ELECTION flag specified to DB_ENV->repmgr_start has been removed. + Changes to default verbose message handling methods. + In replication the DB_REP_LOGSONLY flag to DB_ENV->rep_start replaced with DB_REP_CLIENT + New arguments nvotes, flags to DB_ENV->rep_elect. + New parameter passed to DB_ENV->set_errcall and DB->set_errcall. + Support for DB_ENV-set_verbose flag DB_VERB_CHKPOINT removed. + DB_ENV->set_msgcall/set_msgfile added to process message outputs. + For database environs using flag DB_TXN_NOTDURABLE replace with DB_LOG_INMEMORY. + DB_ENV->set_tas_spins/get_tas_spins renamed to DB_ENV->mutex_set_tas_spins/mutex_get_tas_spins + Flag DB_MUTEX_PROCESS_ONLY added to DB_ENV->set_isalive + Parameters priority & timeout no longer set via DB_ENV->rep_elect, use rep_set_priority & rep_set_timeout. + DB_ENV->set_rep_limit/get_rep_limit/set_rep_transport changed to rep_set_limit/rep_get_limit & rep_set_timeout + One of the informational returns from DB_ENV->rep_process_message changed to an event. + DB_MPOOL_DIRTY flag is now specified to the DB_MPOOLFILE->get method instead of the put method and the set method has been removed. DB_MPOOL_CLEAN flag is no longer supported. From sacadmin Wed Sep 17 09:00:23 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 m8HG04Qn026492 for ; Wed, 17 Sep 2008 09:00:09 -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 m8HFxkxg002770 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Thu, 18 Sep 2008 00:00:03 +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 <0K7C00K2VKG0QN00@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Wed, 17 Sep 2008 09:00:00 -0700 (PDT) Received: from sca-es-mail-2.sun.com ([192.18.43.133]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0K7C00C5DKG06EF0@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Wed, 17 Sep 2008 09:00:00 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m8HG00un009627 for ; Wed, 17 Sep 2008 09:00:00 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K7C00G01K79FI00@fe-sfbay-10.sun.com> (original mail from Chris.Kasso@Sun.COM) for lsarc@sun.com (ORCPT lsarc@sun.com); Wed, 17 Sep 2008 09:00:00 -0700 (PDT) Received: from [192.18.122.65] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K7C00MLZKFSW070@fe-sfbay-10.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Wed, 17 Sep 2008 08:59:52 -0700 (PDT) Date: Wed, 17 Sep 2008 08:59:51 -0700 From: Chris Kasso Subject: Re: Berkeley DB 4.7.25 [LSARC/2008/570 FastTrack timeout 09/16/2008] In-reply-to: <200809082340.m88Net5i012105@aha.red.iplanet.com> Sender: Chris.Kasso@Sun.COM To: lsarc@Sun.COM Cc: Lars.Heill@Sun.COM, Karen.Langford@Sun.COM Reply-to: Chris.Kasso@Sun.COM Message-id: <48D12977.9020403@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: <200809082340.m88Net5i012105@aha.red.iplanet.com> User-Agent: Thunderbird 1.5.0.8 (X11/20061110) Status: RO Content-Length: 355 This fasttrack timed out yesterday. Marking it closed - approved. Chris Chris Kasso wrote: > Folks, > > I'm sponsoring the following proposal on behalf of Karen Langford for > FastTrack approval. The timer is set for 09/16/2008. > > Proposed release binding is Minor. > > http://sac.sfbay.sun.com/LSARC/2008/570/materials/proposal.txt > > Chris