Database corruption since LO 5.7.3 installed

users
#1

Since upgrading to LO 5.7.3 a database of mine keeps getting corrupted. When
I try to open it it opens in Writer with the text Ó×r6ÒÒ#v If I try
opening it in a Zip file reader I'm told it's not a valid Zip file. It's not
consistent though; sometimes it opens OK.

It's an embedded HSQLD database and I'm running Windows 7.

Has anyone else here seen this? It doesn't seem to be in Bugzillla.

#2

Hi Peter,

Since upgrading to LO 5.7.3 a database of mine keeps getting corrupted. When
I try to open it it opens in Writer with the text Ó×r6ÒÒ#v If I try
opening it in a Zip file reader I'm told it's not a valid Zip file. It's not
consistent though; sometimes it opens OK.

It's an embedded HSQLD database and I'm running Windows 7.

Has anyone else here seen this? It doesn't seem to be in Bugzillla.

There isn't a special database-problem with LO 5.3.7. Do you use LO and
Java in the same bit-version?

Seems to be you file is really corrupted. If you couldn't get the
content with unzipping the *.odb-file I don't know any way to get the
data back.
You could only use a copy from your last backup instead.

Regards

Robert

#3

Hi Ptoye and all:

You say that sometimes the data file open well. When it happen, I suggest you to save the file with a new name (Other file). I would solve your problems.

Regards,

Jorge Rodríguez

#4

Thanks Robert. Restoring from a backup is exactly what I've been doing. But
it's odd. It's a database I use about once or twice a week (depending on how
much wine I've been drinking), and it's failed to open 4 times since then:
the saved dates were 26 November, 24 December, 27 December and 5 Jan. I've
used it more often, though, and I've decided to save a copy whenever I save
the original. And possibly I'll save the original before opening it as well.

I agree that the database is corrupt, but what's corrupting it? I haven't
had any such corruptions on any other LO documents (famous last words?) or
other files. I've had a closer look, and the corrupt files seem to be the
last 46 KB (approx) of the original (which are 184 KB).

Both LO and Java are 64-bit versions. Is it a good idea to revert to 32-bit
versions? I'm not sure how LO decides which Java to use if given the choice;
I assume it picks up the same bit-version. Bugzilla doesn't show any obvious
connection between 64-bit and database corruption.

#5

Hi Peter,

Both LO and Java are 64-bit versions. Is it a good idea to revert to 32-bit
versions? I'm not sure how LO decides which Java to use if given the choice;
I assume it picks up the same bit-version. Bugzilla doesn't show any obvious
connection between 64-bit and database corruption.

It's right. It has only to be the same bit-version.

You could use the macro for copying the file to the backup-folder of LO
when opening the file. It's published in the Base-Handbook. I could post
it here also.

With this macro you get, for example, 10 different versions saved in the
backup-folder. If you get any problems whith opening a file you could
choose the last backup there.

Regards

Robert

#6

Hi,
This problem seems to have been observed not so long ago:
https://ask.libreoffice.org/en/question/63369/repair-corrupt-odb-file/
The fix that is mentioned in that post is there:
https://forum.openoffice.org/en/forum/viewtopic.php?f=83&t=17567
Not sure if the proposed solution will help, but it seems that this
type of corruption is not uncommon.
Rémy Gauthier.

#7

Hi Remy,

seems you haven't read the first mail of this thread:
"If I try opening it in a Zip file reader I'm told it's not a valid Zip
file."

The way to repair a *.odb-file is described in the Base-Handbook in
detail. But if you can't extract anything there you couldn't get data
out of a corrupted file.

Regards

Robert

#8

I think that the first thing to do is to work out if the corruption's
happening on loading or saving. It's easy to see what's happening as the
corrupted file is of a very different size, so I can see it in Explorer.
That at least will give me a handle on the problem. Then I can work out
whether to make a copy on loading - not much point if that's what does the
corruption.

#9

hi peter.
if you are sure that your file is corrupted, just right click on it
and find properties.
in the security tab, find and select previous versions.
then press okay button.
it restores previous version (that worked properly for you).
God bless you all.

#10

Thanks, but at the moment I'm making manual backups. Unfortunately (?) it
hasn't happened again. Very frustrating.

#11

Robert Großkopf wrote

You could use the macro for copying the file to the backup-folder of LO
when opening the file. It's published in the Base-Handbook. I could post
it here also.

That would be very useful Robert. I've found that the corruption is
happening when I close LO. So saving when I open, and also possibly before
closing might at least preserve the data.

I suspect that the best solution would be to install HSQLDB on my machine
and separate the database from the LO front-end. This sounds like a bit of a
pain, though.

#12

Hi Peter,

here the macro for saving data while opening or running Base:

#13

Thanks Robert, that's fantastic. I'll try it out later this week.

#14

Robert Großkopf wrote

here the macro for saving data while opening or running Base:

Thanks Robert, that's fantastic. I'll try it out later this week.