Issue 107096

Summary:

In a macro, SQL order "Shutdown compact" fails

Product:

Base

Reporter:

dle <didier_lamare>

Component:

code

Assignee:

AOO issues mailing list <issues>

Status:

CONFIRMED ---

QA Contact:

Severity:

Trivial

Priority:

P5 (lowest)

CC:

issues

Version:

OOO320m5

Target Milestone:

---

Hardware:

All

OS:

All

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
Message from SQL order "Shutdown compact"	none
Sample of "Shutdown Compact" by clicking the button.	none

Description dle 2009-11-21 08:46:05 UTC

Hi, 

Since OOo 320, the SQL Order "SHUTDOWN COMPACT" inside a macro fails with a
message (see the attachment). 
If it is replaced by "Shutdown" or by "Shutdown Script", this is ok.
In case with "Shutdown Script" no problem on the next run.
The difference between "Script" and "Compact" is that in case of "Compact" the
tables are rebuilt immediatly. Maybe the problem is here?

Thanks in advance.

Comment 1 dle 2009-11-21 08:50:30 UTC

Created attachment 66218 [details]
Message from SQL order "Shutdown compact"

Comment 2 dle 2009-11-21 08:55:14 UTC

Created attachment 66219 [details]
Sample of "Shutdown Compact" by clicking the button.

Comment 3 py_samyn 2009-11-21 11:38:58 UTC

Hello

My environment : XP SP3 - 300m65(Build:9457)

I confirm...

But no problem if it is replaced by CHECKPOINT DEFRAG

Best regards

Comment 4 marc.neumann 2009-11-23 07:03:48 UTC

confirm and send to the right developer

Comment 5 ocke.janssen 2009-11-23 07:54:06 UTC

As work around you should use execute("SHUTDOWN COMPACT") in your macro and not
executeUpdate.

Comment 6 dle 2009-11-23 14:03:49 UTC

Thank you for the bypass.

Comment 7 Frank Schönheit 2010-11-24 10:51:38 UTC

Given the easy workaround, I don't think we'd (realistically) fix this in the
3.x time frame => retargeting

Comment 8 ocke.janssen 2011-02-03 09:48:45 UTC

Change prio.