Subject | gfix commands always result in "database PATH shutdown" |
---|---|
Author | echawkes |
Post date | 2007-01-18T02:09:58Z |
Hi,
I have a customer using Firebird 1.5.3 on linux.
He has all the default settings in the config file,
and connections are made via TCP/IP. Connections
are only made on localhost - different processes
on the same server read and write, but no other
servers connect.
He is having trouble accessing his database.
He can attach to it, and sometimes write new
records, but sometimes not. In some cases, he
gets this error when attempting to write:
internal gds software consistency check (can't continue after bugcheck)
I've been assuming that there could be corruption,
so I've been trying to use gfix to validate and repair
the database. Unfortunately, all of the gfix
commands give this result:
"database FULL_PATH_TO_DB shutdown"
I've tried (for example)
gfix -online
gfix -validate -full
gfix -mend -full
Any thoughts on what could be causing gfix to act like this?
Thanks
I have a customer using Firebird 1.5.3 on linux.
He has all the default settings in the config file,
and connections are made via TCP/IP. Connections
are only made on localhost - different processes
on the same server read and write, but no other
servers connect.
He is having trouble accessing his database.
He can attach to it, and sometimes write new
records, but sometimes not. In some cases, he
gets this error when attempting to write:
internal gds software consistency check (can't continue after bugcheck)
I've been assuming that there could be corruption,
so I've been trying to use gfix to validate and repair
the database. Unfortunately, all of the gfix
commands give this result:
"database FULL_PATH_TO_DB shutdown"
I've tried (for example)
gfix -online
gfix -validate -full
gfix -mend -full
Any thoughts on what could be causing gfix to act like this?
Thanks