11,038
edits
Changes
From Gramps
→Version 2.2.x: GRDB corruption
Der Versuch einen Stammbaum nach einem downgrade zu öffnen, wird nicht unterstützt. Du erhältst einen Fehler, das die Datenbank mit einer neueren Version erstellt wurde.
== Version 2.2.x: GRDB corruption Beschädigung =====What causes this corruptionWas verursacht diese Beschädigung?===
The leading cause of grdb corruption is moving the grdb file from its original location. Whether you move the file to another directory, rename it, copy into another file, transfer to another machine, or another user account -- all of those will "corrupt" the file.
Not being able to open a /tmp/... file in GRAMPS 3.0.x on opening grdb files indicates database corruption. This is because the grdb file you want to open is copied to the /tmp dir, and then opened. All failure results in the '/tmp/tmpxxxxx could not be opened'
===What do I do nowWas mache ich jetzt?===
The answer depends on whether or not you have the environment for that database. If you just copied one file into another then the environment may still work. If you modified the original database since then, the original environment has changed and there's no good environment for the new file. If you removed your <code>.gramps</code> directory (why oh why?) then all environments are lost. So act depending on the situation, as explained below.
====The environment still existsDie Umgebung existiert noch ====
If you have environment directory for that file, copy it under the above gudelines.
;Example: You copied <code>/home/user/genealogy/MyData.grdb</code> to <code>/home/user/genealogy/backup/BackupData.grdb</code> and the new file is not working.
;Solution: Copy <code>/home/user/.gramps/env/home/user/genealogy/MyData.grdb</code> directory into <code>/home/user/.gramps/env/home/user/genealogy/backup/BackupData.grdb</code> and this should fix the problem.
====The environment is lostDie Umgebung existiert nicht mehr ====
If you don't have the original environment for that file, you may try dumping and loading your data using Berkeley DB tools. Depending on your system, they may be called <code>db_dump</code> and <code>db_load</code>, <code>db41_dump</code> and <code>db41_load</code>, <code>db4.4_dump</code> and <code>db4.4_load</code>, ... In Ubuntu you find them in the package <code>db4.4-util</code>. You might need more recent versions depending on the version your distribution uses in its python package. So for eg Ubuntu Hardy created files, you will need <code>db4.6-util</code>. Whatever they are called, there should be a dump tool and a load tool, and they should be version 4 or later.
Note: If you downgrade your distribution, it might be needed to do dump with 4.6 tools, and load with 4.4 or 4.5 tools.
===How to prevent corruptionWie einer Beschädigung vorbeugen?===
While moving the file is the leading cause of corruption, apparently there are other less frequent causes that we don't fully know. So preventing corruption is not always possible.
