Internal gds Software Consistency Check Errors
Tracy Jenkins
The following errors were found in the Interbase log file. Could someone
please
shed some light on what happened to our database? I cannot find any
references
on these error messages anywhere.
PLAS-CIMLINK (Server) Sun Sep 26 03:53:42 1999
Database: D:\SSWIN\DATA\SSWIN.GDB
internal gds software consistency check (error during savepoint backout
(290))
PLAS-CIMLINK (Server) Sun Sep 26 03:53:43 1999
INET/inet_error: read errno = 10054
PLAS-CIMLINK (Server) Sun Sep 26 03:53:44 1999
Database: D:\SSWIN\DATA\SSWIN.GDB
internal gds software consistency check (cannot find record fragment
(248))
PLAS-CIMLINK (Server) Sun Sep 26 03:53:48 1999
Database: D:\SSWIN\DATA\SSWIN.GDB
internal gds software consistency check (cannot find record back
version (291))
Thanks in advance!!!
Tracy Jenkins
Branden Technologies, Inc
Wilsonville, OR
Stefan Rosehr
in most cases consistency errors in a database accour if you update the
database structure (create/alter tables or indexes) while secondary
attachments are active. Or when your server crashes.
To fix the database go to Interbase Server Manager and perform the follwing
steps:
- connect to database
- shotdown to single user mode
- Validate database with option [x] Ignore Checksum and [x] Validate Record
fragments turned on
- backup database (with Interbase) with option "Disable Garbage collection"
and "Ignore Checksum" turned on
- rename your origin database file
- restore the backup to origin file.
The database should be free of errors now.
Stefan
Tracy Jenkins
have been running Ib5.5 for two weeks without problems and all of a sudden it
crashes. I need to know that it is not going to happen again, or I need to
figure out what is causing it and prevent it from happening again. I can pretty
much guarantee that nobody was updating the database structure at 3 am on Sunday
when the crash occurred.
Sergio Samayoa
databases.