#FAQ: 10019-EN, Date: 2/16/2001

When I use GDS 2000 PRO, I receive read or write errors or errors indicating the database is corrupt.


The information in this article applies to :
GDS 2000 PRO (English)
GDS 2000 PRO (French)


Description
Error messages examples:
- "I/O error for file ..."
- "Error while trying to read from file ..."
- "Database file appears corrupt"
- "Database corrupted"


When using GDS 2000 PRO in day-to-day operation, the database is sometimes subjected to events that pose minor problems to database structures. These events include:

- Abnormal termination of GDS 2000 PRO or INTERBASE application.

- Write errors in the operating system or hardware.

- Hardware failures.


Solution
If GDS 2000 PRO's database become corrupted or damaged, here are the steps to follow to fix it. For more detailled information about correcting database errors, refer to the "Operations Guide" manual in the INTERBASE documentation (downloadable separately from the web site of INTERBASE at http://www.borland.com/interbase ).

If INTERBASE is installed on a LINUX server, you need to have the "Super Server" version of INTERBASE installed on your LINUX server to be able to use the "IBConsole" utility mentionned in the procedure bellow. If you have the "Classic Server" version of INTERBASE installed on your LINUX server, refer to the "Operations Guide" manual in the INTERBASE documentation to use the "gbak" command line utility instead of "IBConsole"

Before beginning, be sure that nobody access the damaged database or use GDS 2000 PRO.

1- Execute the "IBConsole" utility included with GDS 2000 PRO.

2- Double-click on the server where the damaged database is located. (If the database is on your local computer, select "Local Server"). Type "SYSDBA" in the field "User Name" and "masterkey" in the field "Password" and click on the "Login" button. (If you have changed the password for the "SYSDBA" INTERBASE user, type the new password in the "Password" field instead of "masterkey").

3- Select the damaged database. Don't connect to this database, just select it by clicking once on the icon.

Notes:
For steps 2 and 3 above, if it is the first time you use the "IBConlole" utility and your server or your database is not listed, refer to the "Operations Guide" manual in the INTERBASE documentation to know how to register a server and/or a database in the "IBConsole" utility.

4- From the menu, select "Database", "Maintenance" and "Validation"

5- From the validation dialog box, click the "OK" button to start the database validation.

6- If your database is damaged, you will get an error message looking like the following one:

"Database file appears corrupt ()"
"bad checksum"
"checksum error on database page 212"


7- Click the "OK" button, to close the dialog box. Start back the validation indicated in the step 4, but this time by setting the "Ignore Checksum Errors" parameter to "True".

8- You should get an error message looking like the following one:

"Summary of validation errors"

"Number of data page errors : 1"
"Number of database page errors : 1"

"Check the InterBase.Log file for additional information"


9- In this dialog box, set the "Ignore Checksum Errors" parameter value to "True" and click the "Repair" button to correct the database.

10- After the database validation is completed, you should get the following message:

"Database validation complete"


11- Click the "OK" button to close this dialog box.

12- To verify the database was corrected, you can do the validation indicated in the step 4 again, and this time you should get the message indicating "No database validation errors were found".

13- Quit the "IBConsole" utility.

13- You can now use GDS 2000 PRO.


Status

Information

See also FAQ 10026-EN and FAQ 10027-EN



© 1996-2008 OroLogic Inc.