Hello,

Deleting  files in mentioned directory  solved mine problem. Now I created new database in gramps 2.1.x

Probably from mine side not the best way is to have old version of gramps installed to /usr/ and new test in /home/asleiniu/newgramps. 
I keep this in mind.


Thanks for fast reply,
Arturasr Sleinius


On 7/23/06, Don Allingham < donaldallingham@comcast.net> wrote:
Arturas,

First, try deleting the ~/.gramps/bsddbenv directory. This is not always
the best thing to do, but since the db is reporting corruption, try
this. It removes temporary log files. Sometimes this helps clear up the
problem when nothing else works.

Don

On Sun, 2006-07-23 at 10:14 -0700, Alex Roitman wrote:
> Arturas,
>
> On Sun, 2006-07-23 at 19:54 +0300, Arturas Sleinius wrote:
> > 22507: ERROR: DbLoader.py: line 406: Failed to open database.
> > Traceback (most recent call last):
> >   File "/home/asleiniu/newgramps/share/gramps/DbLoader.py", line 396,
> > in read_file
> >     self.dbstate.db.load(filename,self.uistate.pulse_progressbar,mode)
> >   File
> > "/home/asleiniu/newgramps/share/gramps/GrampsDb/_GrampsBSDDB.py", line
> > 320, in load
> >     self.env.open(env_name,env_flags)
> > DBRunRecoveryError: (-30977, 'DB_RUNRECOVERY: Fatal error, run
> > database recovery -- PANIC: DB_RUNRECOVERY: Fatal error, run database
> > recovery')
>
>
> This means that either the database is corrupted, or more likely,
> that the grdb file that was created with 2.1 on one machine is being
> opened on another one. The grdb files in 2.1 are not portable, at
> least not at the moment. This is because of a missing method in
> the pythong bsddb bindings to reset the log files numbers. A silly
> thing, but it prevents us from properly opening grdb file one
> one machine that was created on another machine. In fact, it will
> also prevents file created by one user to be opened on the same machine
> by another user.
>
> We hate this, and the newest bsddb module in python2.5 will have the
> missing piece. Until then, one has to either use non-transactional
> environment (like in 2.0) or export to XML for portability. The
> non-transactional environment is both slower and susceptible to
> corruption during crashes. Hopefully this will not be a problem for
> too long.
>
> > 369424: ERROR: gramps.py: line 142: Unhandled exception
> > Traceback (most recent call last):
> >   File "/home/asleiniu/newgramps/share/gramps/ViewManager.py", line
> > 723, in new_activate
> >     self.post_load_newdb(filename,filetype)
> >   File "/home/asleiniu/newgramps/share/gramps/ViewManager.py", line
> > 783, in post_load_newdb
> >
> > self.state.change_active_person(self.state.db.find_initial_person())
> >   File
> > "/home/asleiniu/newgramps/share/gramps/GrampsDb/_GrampsDbBase.py",
> > line 1226, in find_initial_person
> >     the_ids = self.get_gramps_ids (PERSON_KEY)
> >   File
> > "/home/asleiniu/newgramps/share/gramps/GrampsDb/_GrampsDbBase.py",
> > line 1207, in get_gramps_ids
> >     return table.keys()
> > AttributeError: 'NoneType' object has no attribute 'keys'
>
> Once we don't have an open database, errors will amass :-)
>
> Alex
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________ Gramps-bugs mailing list Gramps-bugs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gramps-bugs


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEw7ECO+d2KKbE9WsRAk0tAKDcnPsret63HlNih5IC0NuZ1TnlxwCfQPfj
Yb3RVVLa41rzUaLSXV1zGMI=
=7834
-----END PGP SIGNATURE-----