Issue 111624 - OOo crashes with invalid SET TABLE INDEX statement in script file
Summary: OOo crashes with invalid SET TABLE INDEX statement in script file
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOO320m12
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: OOo 3.3
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2010-05-15 12:42 UTC by toa7d9
Modified: 2017-05-20 10:22 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
OOo 3.2.0 crashes with this odb file (78.63 KB, application/vnd.sun.xml.base)
2010-05-15 12:44 UTC, toa7d9
no flags Details
forerunner of Bandfinanzen.05.defekt.odb (92.07 KB, application/vnd.sun.xml.base)
2010-05-17 22:19 UTC, toa7d9
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description toa7d9 2010-05-15 12:42:48 UTC
- OOo version is 3.2.0 (german), Java Version is jre-6u20-windows-i586-s
- Opening the file "Bandfinanzen.05.defekt.odb"
- Click on "Tables" view
--> OOo crashes
Comment 1 toa7d9 2010-05-15 12:44:18 UTC
Created attachment 69463 [details]
OOo 3.2.0 crashes with this odb file
Comment 2 r4zoli 2010-05-16 20:00:21 UTC
The crash happens when click into table area.
Need more details about your file.
How did you created this file?
It created in OOo 2.x versions?
This file worked in earlier versions of OOo?
You opened in mixed versions 2.x and 3.x?
You copied data from other file?
Comment 3 toa7d9 2010-05-16 23:44:51 UTC
I tried unzipping the file today and got an CRC error from my ZIP software???

- The File was originally created 2008-12-11 with an older version of OOo (I
think it was 3.0) but recently I added some Tables/Views with version 3.2.0.
- I think I never opened it with OOo 2.x but I am not sure about that.
- Earlier modifications of this file did not cause any trouble.
- I did not copy data from other file; all content was created in direct
interaction with OOo Base and some SQL statements.
Comment 4 toa7d9 2010-05-17 00:34:05 UTC
Another thing that may relate here: I remember that I manipulated the embedded
HSQLD database through SQL statements before (CREATE VIEW, for instance) so I
*knew* the file had to be saved. But the OOo "Save" button stayed disabled. So
maybe I finally got an insane/incosonsistent file, which caused the app the
crash when opened next time.
Comment 5 r4zoli 2010-05-17 09:32:47 UTC
I can open with zipper and found that database/data file not contain real
database data, and it cause crash.
data file content:
/*C1*/SET WRITE_DELAY 0
SET AUTOCOMMIT FALSE
SET AUTOCOMMIT TRUE

What you did last time with this file, I see no problem in database/script with
Views.
May be you deleted your data with some SQL script. 
Comment 6 toa7d9 2010-05-17 10:49:05 UTC
> May be you deleted your data with some SQL script.

No I didnt. Would it be okay for OOo to crash if I did?

Last steps I did before was 
- opening the previous modification of this file (which I still have and which 
also causes OOo to crash when clicking into "table" area)
- NOT click into "table" area
- click on "Save as..." because my hope was that this operation would somehow 
stabilize/cleanup the odb file content.

I think the problem has two parts and maybe we need two issues here.
(a) Why did OOo Base produce invalid/inconsistent odb file content?
   (which could be the topic of a new issue)
(b) Why did OOo Base crash on opening this invalid odb file content instead of 
reporting an "invalid data error" or similar?
  (which is my issue here)
Comment 7 drewjensen.inbox 2010-05-17 20:07:50 UTC
OO.o crashes when during initialization of the HSQL engine an invalid ALTER
TABLE INDEX statement is executed. 

The command that causes the crash is embedded in the attached test document.
In the embedded script file, within the ODB file is this line:

SET TABLE "Transactions" INDEX'87920 90456 86704 89512 43'

Which brings the question; What sequence of steps causes that invalid line to
end up in the script file? 
Comment 8 toa7d9 2010-05-17 22:19:06 UTC
Created attachment 69487 [details]
forerunner of Bandfinanzen.05.defekt.odb
Comment 9 toa7d9 2010-05-17 22:24:10 UTC
toa7d9->atjensen:
'Bandfinanzen.05.defekt.odb' is actually the result of executing 'Save as...' on
the opened document 'Bandfinanzen.04.defekt.odb' which also causes OOo to crash
when clicking into the 'tables' area. Maybe the comparison of the two files may
help you with your question. If I can be of further assistance let me know.
 
Comment 10 ocke.janssen 2010-07-08 15:13:22 UTC
Fixed in cws dba33g.

I don't know why hsqldb ask to read in the stream for a length of -4. 

Now we throw an IOException but hsqldb seems to fine with that.
Comment 11 ocke.janssen 2010-07-08 15:15:02 UTC
Forgot to set target
Comment 12 ocke.janssen 2010-07-14 11:52:45 UTC
Please verify. Thanks.

- open attached 05
- click on tables
=> crash
Comment 13 marc.neumann 2010-07-20 09:23:24 UTC
verified in CWS dba33g

find more information about this CWS, like when it is available in the master
builds, in EIS, the Environment Information System:
http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba33g