#FAQ: 10169-EN, Date: 07/21/2011
When I'm using OroTimesheet 7, I receive read or write errors or errors indicating that the database is corrupt.
| The information in this article applies to : |
OroTimesheet 7.x (French)
Error messages examples:
- "I/O error for file ..."
- "Error while trying to read from file ..."
- "Database file appears corrupt"
- "Database corrupted"
When using OroTimesheet, it can happen that the database become corrupted in situations such as:
- The Firebird database server did not stop correctly, for example, following a problem with the server where the database is located.
- Write errors on the hard drive by the operating system.
- Hardware failures.
If the OroTimesheet database becomes corrupted or damaged, here are steps to follow to fix it. For more detailled information about correcting Firebird database errors, refer to the Firebird documentation.
Before beginning, be sure that nobody is accessing the damaged database or are using OroTimesheet.
It is strongly recommended to keep a copy of the OroTimesheet 7 database file (usually named ot.fdb) before trying to repair it.
1- Run the Database utility included with OroTimesheet 7 by double-clicking on the file FBTOOLS.EXE located in the OroTimesheet 7 installation folder (usually C:\Program Files\OroLogic\OroTimesheet7).
2- Select the Validation tab.
3- Enter the connection information of the database to repair.
4- Type the password of the SYSDBA Firebird user into the Password field. (If you did not changed the password of the Firebird SYSDBA user, the default password is masterkey in lowercase).
5- Check the following 3 options:
Validate record fragments
Mark corrupt records
Ignore checksums errors
Do not check any other options.
6- Click the Start validation button and answer Yes to the confirmation.
7- After the validation process is finished, you should get the Validation completed message. Click the OK button. A summary of the validation process is displayed on screen and can have the following format:
Summary of validation errors
Number of data page errors : 1
Number of database page errors : 2
Close this window by clicking the X button at the top right.
8- To complete the database repair process, a backup and a restore of the database must be done.
9- Select the Backup tab.
10- Verify the database file name as well as the backup file name.
11- Check the following 3 options:
Ignore transactions in limbo
Disable garbage collection
Do not check any other option.
12- Click the Start Backup button and answer Yes to the confirmation.
13- When the backup process is finished, the Backup successfully completed message is displayed. Click the OK button.
14- Select the Restore tab.
15- Verify the database file name as well as the backup file name.
16- Do not check any option.
17- Click the Start Restore button and answer Yes to the confirmation.
18- When the restore process is finished, the Restore successfully completed message is displayed. Click the OK button.
19- Quit the Database utility.
20- The database shoule now be repaired. You can run back OroTimesheet 7.
© 1996-2012 OroLogic Inc.