That didn't work either. I started with a fresh copy of the NOID directory
from before I tried the upgrade command:

gomez@gwnma:/var/www/nd/t1$ ls NOID
__db.001  __db.003  __db.005  lock  log.0000000001  noid.bdb
__db.002  __db.004  __db.006  log   logbdb          README

gomez@gwnma:/var/www/nd/t1$ sudo rm NOID/__*

gomez@gwnma:/var/www/nd/t1$ sudo db4.8_upgrade -v -h NOID noid.bdb
db4.8_upgrade: noid.bdb upgraded successfully

gomez@gwnma:/var/www/nd/t1$ curl localhost/nd/noidu_t1?mint+1
no "Env" object (No such file or directory)

I have been binding the IDs for the production NOID db (t1 is just the test
NOID), but I have also been storing them in a mysql DB on our dspace server
that I use to keep track of where things are in the workflow. So I suppose
I could try what you suggested: setup a new production NOID, mint as many
IDs as we have used so far, then rebind them all using the data in the
mysql DB. Redundant data is a good thing.

-Joshua

On Tue, Feb 14, 2012 at 1:07 PM, John A. Kunze <[log in to unmask]> wrote:

> Try removing the environment files before you upgrade (or after if
> you didn't save the old file).  When I released that version of NOID
> I have since regretted leaving in code that created a stub environment
> (that actually isn't used by NOID) because it just creates upgrade
> problems that I never figured out properly.
>
> If all else fails and you're just using NOID to mint (eg, no binding),
> it's quite easy to start a new minter from scratch and mint until you see
> the last id you minted prior to conversion.  The order of minting is
> deterministic, so in the end you'll have a new minter that's in the same
> "state" as the old minter (again, provided you haven't been doing holds
> and binds -- that's more complicated).
>
> -John
>
>
> --- On Tue, 14 Feb 2012, Joshua Gomez wrote:
>
>> Thanks John!  I tried running db_upgrade, but apparently the utilities
>> were
>> not included in my setup. So I ran the following:
>>
>> gomez@gwnma:/var/www/nd/t1$ sudo apt-get install db4.8-util
>>
>> That installed the utilities, but I'm still having some trouble:
>>
>> gomez@gwnma:/var/www/nd/t1$ sudo db4.8_upgrade -v -h NOID NOID/noid.bdb
>> db4.8_upgrade: Program version 4.8 doesn't match environment version 4.7
>> db4.8_upgrade: DB_ENV->open: DB_VERSION_MISMATCH: Database environment
>> version mismatch
>>
>> I tried leaving off the environment home flag
>>
>> gomez@gwnma:/var/www/nd/t1$ sudo db4.8_upgrade -v NOID/noid.bdb
>> db4.8_upgrade: NOID/noid.bdb upgraded successfully
>>
>> That looks like it worked. However, when I try making a call to the
>> service
>> I get the old error:
>>
>> gomez@gwnma:/var/www/nd/t1$ curl localhost/nd/noidu_t1?mint+1
>> no "Env" object (DB_VERSION_MISMATCH: Database environment version
>> mismatch)
>>
>> -Josh
>>
>>
>> On Mon, Feb 13, 2012 at 5:42 PM, John A. Kunze <[log in to unmask]> wrote:
>>
>>  The standard BerkeleyDB library probably changed when you upgraded
>>> Ubuntu, and it complains that the NOID database (written with the old
>>> library) is incompatible.
>>>
>>> You should be able to use db_upgrade to convert the NOID database
>>> (NOID/noid.bdb).  db_upgrade is a command line utility that comes with
>>> BerkeleyDB.
>>>
>>> -John
>>>
>>>
>>> --- On Mon, 13 Feb 2012, Joshua Gomez wrote:
>>>
>>>  Does anyone here have expertise with Berkeley DB?
>>>>
>>>> I was running an instance of NOID (which uses Berkeley DB) to mint and
>>>> resolve ARKs.  I updated the OS for the server it was running on from
>>>> Ubuntu 9 to Ubuntu 10.  Now NOID has stopped working and complains that
>>>> the
>>>> db version doesn't match: "Program version 4.8 doesn't match environment
>>>> version 4.7"
>>>>
>>>> I have no experience at all with Berkeley DB and could use some advice.
>>>>
>>>> Thanks,
>>>> Josh
>>>>
>>>> --
>>>> Joshua Gomez
>>>> Digital Library Programmer Analyst
>>>> George Washington University Libraries
>>>> 2130 H St, NW Washington, DC 20052
>>>> (202) 994-8267
>>>>
>>>>
>>>>
>>
>> --
>> Joshua Gomez
>> Digital Library Programmer Analyst
>> George Washington University Libraries
>> 2130 H St, NW Washington, DC 20052
>> (202) 994-8267
>>
>>


-- 
Joshua Gomez
Digital Library Programmer Analyst
George Washington University Libraries
2130 H St, NW Washington, DC 20052
(202) 994-8267