Skinner, John (GE Healthcare) wrote:
-----Original Message-----
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf
Of Sergiu Dumitriu
Sent: Tuesday, September 02, 2008 4:49 PM
To: XWiki Users
Subject: Re: [xwiki-users] - trouble restarting xwiki
John V. Skinner wrote:
Ah, but i found
webapps/xwiki/WEB-INF/hibernate.cfg.hsql.xml also.
In this file the connection.url was jdbc:hsqldb:file:db/xwiki_db
There is also 2 very large files,
xwiki_db.log.delete,
xwiki_db.script.delete
Are these roll-back files of some kind?
I don't find the xwiki_db file at all. Don't know why not.
Your setup looks really weird. There shouldn't be any .delete files. The
hibernate.cfg.hsql.xml file shouldn't be used unless you configured
something in xwiki.cfg.
When did this error start to happen? Did you do something on the server?
We had to shutdown systems over the weekend, and it didn't restart for
me today.
Nothing at all that I can think of.
As a general tip, the provided hsql database is not supposed to be used
in large wikis, and not in production. I guess we should emphasize this
in the download and installation notes.
Well, I admit to knowing this was beta.
If I can recover the database through these .delete files, that would be
good.
I find all the text in there.
It includes text like:
INSERT INTO XWIKIDOC VALUES(-1324373334, 'Main.sometitle',
'stuff','','','en',0,'2008-05-05 14:58:17.00',
(and a fair amount of
text)
For a start, you should:
1. Make a backup of those files. They are important.
2. Try to rename them to xwiki_db.log and xwiki_db.script (just delete
the .delete extension)
3. If it doesn't work, then check the access rights. By default, HSQL
should not throw an error, but create a new database if it doesn't find
its files.
4. If it still doesn't work, if you know SQL, or somebody else that
knows SQL, check the file to see if it is corrupted. Remove the broken
lines and try again.
For the moment, this is all I can suggest.
After you manage to recover the database, you should seriously consider
an update, and switching to mysql or another dbms that supports heavy load.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/