We are consolidating some Firebird 1.5 databases that have been running for
many years without issue, and have moved them to a CentOS 5 64 bit server, away
from their original CentOS 32 bit server. Everything appeared to be fine
following migration - these are web applications so we tested them
We have a database with about 500 stored procedures in it, and I'm finding a
number have queries that are executing with non-indexed searches. As the user
community on this application is increasing, this is becoming harder for the
users to deal with. This is a legacy application in FB 1.5 so
We have a Firebird 1.5 Super Server database on Linux running that decided last
week to stop successfully completing a backup with GBAK.
After running for about an hour, it fails with the following error:
gbak: ERROR: database file appears corrupt ()
gbak: ERROR: wrong page type
gbak: ERROR:
