[BDB 11gR2 Beta] [#18298] First Questions about DBD 11gR2

[Michael Brey]

Sandra,

  The beta 2 drop is 5.0.11.   This is the one that is posted and should 
be used. 

thanks
mike

Sandra Whitman wrote:
> Hi Dave,
>
>
> I just wanted to see where we are at with regard to sending a snapshot 
> to Luis. 
>
> I did verify the instructions from Alex/Michael.  Winnie corrected one 
> typo and with that I could run  test.db and verify that a database is 
> created by Berkeley DB.  I used the db-5.0.10 drop, db-5.0.10.zip with 
> Version 1.6 of
> the Java JDB, plus the two attached files from Alex:
> 18298_win_jdbc.diff
> Constants.java
>
>
> I did notice that db-5.0.11 is now available.  I don't know if 
> anything has changed with that drop.  If that is what Luis will be 
> getting, I can try it out.
>
>
> Winnie has some additional build instructions at: 
> https://sleepycat.oracle.com/trac/wiki/BDBSQL.JDBC.Build I must still 
> have something set up incorrectly with my environment because I can 
> not run javac at the command line prompt to test as per those 
> instructions.
>
>
> I will be out on vacation from Tuesday(2/23)-Friday(2/26) this week so 
> I am not positive I can get that resolved today.
>
>
>
> I followed these steps and this would basically be the instructions I 
> would send to Luis.
>
>
> 0) From the "Building the Java API" section of the Building Berkeley 
> DB for Windows documentation:
>
> The following instructions assume that you have installed the Sun Java 
> Development Kit in d:\java. If you installed elsewhere or have 
> different Java software, you will need to adjust the pathnames 
> accordingly.
>
>
> # Set your include directories. Choose Tools -> Options -> Projects -> 
> VC++ Directories. Under the "Show directories for" pull-down, select 
> "Include files". Add the full pathnames for the d:\java\include and 
> d:\java\include\win32 directories.
> Then click OK. These are the directories needed when including jni.h.
>
> # Set the executable files directories. Choose Tools -> Options -> 
> Projects -> VC++ Directories. Under the "Show directories for" 
> pull-down, select "Executable files". Add the full pathname for the 
> d:\java\bin directory, then click OK. This is the directory needed to 
> find javac.
>
>
>
> 2) Apply the attached patch 18298_win_jdbc.diff
> The directions for this are below under: APPLYING PATCHES ON WINDOWS
>
> To summarize, apply the patch like this:
> BerkeleyDB_root_dir>"<path to patch.exe>patch.exe" -p1 -i 
> 18298_win_jdbc.diff
>
>
>
> 3) Copy the attached "Constants.java" file into the sql/jdbc/SQLite/ 
> directory.
>
>
> 4) Open the build_windows/Berkeley_DB.sln file in Visual Studio
>
>
> 5) Select "File->Add->Existing Project", and add 
> "build_windows/db_sql_jdbc.vcproj" into the solution.
>
> 6) Right-click db_sql_jdbc in the solution explorer, and select 
> "Properties".
>
> 7) In Linker->General. Set the "Output File" to be 
> "$(OutDir)/sqlite_jni.dll" (it is "$(OutDir)/.dll" before you change it).
>
> 8) Either build the solution, or the "db_sql" project.
>
> 9) Build the db_sql_jdbc project. The project assumes you have Java 
> (1.6) installed in your path.
>
>
> To test:
>
> (Note that this process creates a "jdbc.jar" and a "sqlite_jni.dll".)
>
>
> $ cd build_windows/Win32/Debug (if you built Debug)
> $ java -classpath jdbc.jar -Djava.library.path=. SQLite.Shell test.db
>
> The shell can be used in a similar way to the default SQLite shell. To 
> verify that the resulting database is generated by Berkeley DB, verify 
> that a test.db-journal directory is created and the content look like:
>
>          ..
> log.0000000001
> __db.001
> __db.002
> __db.003
> __db.004
> __db.005
> __db.006
> __db.register
>
>
>
>
>
> APPLYING PATCHES ON WINDOWS
> ------------------------------------------------------
> 1. Download the patch utility. For Windows, the patch utility can be
> downloaded from:
> http://gnuwin32.sourceforge.net/packages/patch.htm
>
> 2. Install the patch utility.  On Windows, the default installation
> location is:
> C:\Program Files\GnuWin32\bin\patch.exe
>
> 3. Download the patch/patches into the appropriate Berkeley DB
> root directory for the release being patched.
> 4. cd to the Berkeley DB root directory for the release.
>
> 5. You may find that the patch files do not have the Windows end-of-line
> endings.  In this case the patch must be converted to follow the Windows
> end-of-line conventions.  There are several ways to perform this 
> conversion.  Some options for converting a patch to follow the Windows 
> end-of-line
> conventions are: 1) running a program like 'unix2dos'  2) using Visual 
> Studio.
>
> 6. Run the patch utility as shown below (this step requires that
> the patch has the Windows end-of-line format as discussed in step 5),
> replacing your path to 'patch.exe' if it was changed from the default 
> installation:
>
> BerkeleyDB_root_dir>"C:\Program Files\GnuWin32\bin\patch.exe" -p<num> 
> -i patch.<ver>
>
> Where
> - 'patch.<ver>' is the name of the patch
> - '-p<num>' -  indicates the number of leading slashes that are stripped
> from each file name found in the patch file.  - '-i' indicates read 
> from 'patch.<ver>'
>                    
> Thanks,
> Sandra
>
> Dave Segleau wrote:
>> Alex/Sandra,
>>
>> My suggestion is to wait for the second beta snapshot (it's a day or 
>> two away). I'd rather do that than possibly give him multiple 
>> snapshots. I'll update Luis as soon as it's ready. Can he follow 
>> those instructions and build the JDAVIE driver for Windows? Alex, 
>> since you're going to be on vacation, who can we follow up with if 
>> there's a problem?
>>
>> Thanks,
>>
>> Dave
>>
>> On 2/18/2010 9:29 PM, Alex Gorrod wrote:
>>> Hi,
>>>
>>> On 19/02/2010 4:20 PM, Sandra Whitman wrote:
>>>> Ok, so Luis has the 5.0.6 release as that was the original Beta. 
>>>> Does he
>>>> need the 5.0.10 release now?
>>>
>>> Yes, he will. I should have been clearer on this point.
>>>
>>> The 5.0.10 release is destined to be the second beta snapshot 
>>> candidate. It still needs to go through some testing before that is 
>>> finalized. Carol (or someone else) will send an email when the Beta 
>>> is generally available, but since Luis is actively working on this 
>>> at the moment, it might make sense to give him access sooner.
>>>
>>> Mike Brey/Dave: What do you think of the above suggestion - it's 
>>> really up to you.
>>>
>>> I'm trying to summarize now, since I'm going on vacation for a week 
>>> starting tomorrow, and wanted to get something usable before then.
>>>
>>> - Alex
>>
>> -- 
>> Oracle <http://www.oracle.com>
>> David Segleau | Director Product Management - Berkeley DB
>> Phone: +1 425 945 8533 | Mobile: +1 408 420 7350
>> Oracle Database Engineering
>>
>> Green Oracle <http://www.oracle.com/commitment> Oracle is committed 
>> to developing practices and products that help protect the environment