Bug 45906 - Database destroyed
Summary: Database destroyed
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Base (show other bugs)
Version:
(earliest affected)
3.4.5 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-10 09:31 UTC by MESSIN
Modified: 2012-09-15 16:21 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Database after change (1.50 MB, application/vnd.sun.xml.base)
2012-02-10 09:31 UTC, MESSIN
Details
o_lvj.odb (2.07 MB, application/vnd.sun.xml.base)
2012-03-05 08:12 UTC, MESSIN
Details
d_lvj.odb (1.50 MB, application/vnd.sun.xml.base)
2012-03-05 08:12 UTC, MESSIN
Details
lvj.odb (1.87 MB, application/vnd.sun.xml.base)
2012-03-05 08:12 UTC, MESSIN
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MESSIN 2012-02-10 09:31:25 UTC
Created attachment 56878 [details]
Database after change

Windows XP falmillial

My database is an old one and I was madifying a form, including  a new subform.
I closed my job and eared abig HDD activity before closing the window acordingto these task.
When I tried to open my database, i a windows opened asking me to choice a filter.
My database was destroyed. 

It's the first time  I try to repport that, but it happened too many times.

You can contact me on ++33(6) 32 46 20 90 in frecnh if possible
Thanks
Gérard Messin
lvj.odb is the  file after change
Comment 1 Julien Nabet 2012-02-12 04:01:40 UTC
Several questions :
- is the problem on several databases ?
- have you got any backup of the database attached ?
- with which version of Libreoffice did you create this database ?

(en français)
Plusieurs questions :
- Est ce que le problème se produit sur plusieurs fichiers Base ?
- Avez vous au moins 1 sauvegarde du fichier Base que vous avez joint à ce problème ?
- Avec quelle version de Libreoffice avec vous créé cette base de données ?
Comment 2 Alex Thurgood 2012-02-23 22:51:56 UTC
Created attachment 58028 [details]
o_lvj.odb

(In reply to comment #0)


Hi Gérard,
Thanks for your report.

We also need a copy of the original ODB file to be able to compare.

Additionally, please tell us how to reproduce the problem, i.e. exactly, step by step, the operations that cause the problem to occur. Without this, it is unlikely that any of us will be able to help you, simply because we will be unable to reproduce as near as possible the conditions in which you were working when the incident occurred. If you can not do this, then we will have to mark the bug as invalid.

Database corruption with an integrated HSQLDB db is not a new phenomena (check out the various OOo forum postings where this is mentioned), and often stems from a RAM memory overload at closure of the ODB database file, since this is when the contents and any changes are actually written to the underlying db file on disk.

I can only recommend in the meantime that you take the precautions given to OOo users with regard to HSQLDB ODB files, and which can be found on the various OOo forums. It is unlikely that we will have a solution for your problem, even if it can be reproduced, in the foreseeable future. However, it would help us a lot if we had a reproducible description of how to make the bug occur.


Alex
Comment 3 MESSIN 2012-03-05 08:12:13 UTC
Le 24/02/2012 07:51, bugzilla-daemon@freedesktop.org a écrit :
> https://bugs.freedesktop.org/show_bug.cgi?id=45906
>
> --- Comment #2 from Alex Thurgood<iplaw67@yahoo.co.uk>  2012-02-23 22:51:56 PST ---
> (In reply to comment #0)
>
>
> Hi Gérard,
> Thanks for your report.
>
> We also need a copy of the original ODB file to be able to compare.
>
> Additionally, please tell us how to reproduce the problem, i.e. exactly, step
> by step, the operations that cause the problem to occur. Without this, it is
> unlikely that any of us will be able to help you, simply because we will be
> unable to reproduce as near as possible the conditions in which you were
> working when the incident occurred. If you can not do this, then we will have
> to mark the bug as invalid.
>
> Database corruption with an integrated HSQLDB db is not a new phenomena (check
> out the various OOo forum postings where this is mentioned), and often stems
> from a RAM memory overload at closure of the ODB database file, since this is
> when the contents and any changes are actually written to the underlying db
> file on disk.
>
> I can only recommend in the meantime that you take the precautions given to OOo
> users with regard to HSQLDB ODB files, and which can be found on the various
> OOo forums. It is unlikely that we will have a solution for your problem, even
> if it can be reproduced, in the foreseeable future. However, it would help us a
> lot if we had a reproducible description of how to make the bug occur.
>
>
> Alex
>
Hi Alex
Sorry, I wasn't at home...
Attached to this mail, you can find three files
=> o_lvj.odb which is a copy of the original file
=> lvj.odb which is my current file .
=> d_lvj.odb which is the destroyed data base

In my original file, i made a copy of F2011_adh, naming it F2011_adh_i,
I edited the F2011_adh_i form , adding the elements of sub-form (from 
T_PP table, colored blue in lvj.odb/F2011_adh_i)
After editing the last field, I tried to close the window by clicking on 
the upper right cross
This gave the detroyed file

Plus !
In lvj.odbI find another error; the form F2011_adh was amended 
incomprehensibly
As I use the new form, this is by controlling the shipment that I 
discovered this error
Comment 4 MESSIN 2012-03-05 08:12:17 UTC
Created attachment 58029 [details]
d_lvj.odb
Comment 5 MESSIN 2012-03-05 08:12:17 UTC
Created attachment 58030 [details]
lvj.odb
Comment 6 Jochen 2012-08-25 20:20:31 UTC
Hi Messin,

exits the bug still in the newest LO-version 3.6.1?
Comment 7 Alex Thurgood 2012-09-08 14:24:54 UTC
Hi Messin,
Please test with a more recent version of LO, but not the 3.6.0.4 version, as this is known to destroy database files too, and then report back.
Comment 8 Alex Thurgood 2012-09-08 14:30:49 UTC
Possibly linked to bug 52639, in which case it has been fixed in 3.6.1

Please test in that version and report back.

Alex
Comment 9 Jochen 2012-09-15 16:21:53 UTC
Reporter don´ t answer.
Changed status to "RESOLVED WORKSFORME"