By: Quinn Wildman
Abstract: This error can occur on a read only database after many transactions
InterBase 6.0 introduced the concept of read only databases. Here is information on how to make a database read only from page 6-8 of the InterBase 7.0 Operations Guide manual:
To change the mode of a database between read-write and read-only, you must be
either its owner or SYSDBA and you must have exclusive access to a database.
From within InterBase, you can change a read-write database to read-only mode in
any of three ways:
gbak -create -mode read_only foo.ibk foo.ib
gfix -mode read_only foo.ib
It has recently been discovered that creating many transactions for one connection to a read only database can generate the error "internal gds software consistency check (cannot find tip page (165))" or "internal gds software consistency check (can't continue after bugcheck)". Under this condition the database is not corrupted.
Potential workarounds to this problem:
The error "internal gds software consistency check (cannot find tip page (165))" can also indicate a corrupted database. Under most conditions when this error occurs you cannot connect to the database using any tool. To attempt to resolve this problem first mend the database:
gfix -mend db_name
Next, make the database read only as shown above. Finally, backup and restore the database:
gbak db_name backup_name
gbak -c backup_name new_db_name
If these steps do not work your best option is to use your backup that was created before the database become corrupted. If you do not have a backup, Borland recommends Devrace to attempt to repair your database.
Could not retrieve comments. Please try again later.
Free Developer Edition!
Click here to download a free non-expiring Developer Edition or 30-day trial >
More InterBase Info
InterBase XE3 Product Info
Free Developer Edition download
InterBase on Google+
Follow @InterBase on Twitter
Server Response from: ETNASC01