Table Of Contents |
 |
|
Questions And Answers
| Q: |
Can Recovery for Interbase repair my Interbase / Firebird database? |
| A: |
The effective way to find out if a Interbase / Firebird database is recoverable is to try the demo version of Recovery for Interbase on it. Visit the Demo page for a free copy of the demo.
Product specifications with lists of items recovered and not recovered is available at the Product Information page.
Note: Always backup your original corrupted Interbase / Firebird database before proceeding with any recovery activity! |
| Q: |
What limitations does the demo version of Recovery for Interbase have? |
| A: |
The demo version recovers a limited number of rows in each table of the recovered database. The remaining rows will contain "demo" in text fields and null values in other types of fields.
No additional records or tables will be recovered by commercial version of Recovery for Interbase if not present in demo output. |
| Q: |
I have tried the demo. How do I decide whether to purchase the full version of Recovery for Interbase? |
| A: |
Evaluating the results of demo recovery can help in making the decision. |
| Q: |
What are the differences between product licenses? |
| A: |
Details of current licensing scheme are described at the Licensing page. |
| Q: |
Why do results of recovery contain less data than the original Interbase / Firebird database? |
| A: |
This is normal. The damaged parts of your Interbase / Firebird database will convert to zero size on output. The other common reason of file size decrease is when some of features of the original database are not supported and therefore absent from the recovered database.
Demo-recovered database is smaller because it mostly consists of demo placeholders than actual data. |
| Q: |
Running Recovery for Interbase from command line (through Windows Start -> Run menu). |
| A: |
If your license type is Enterprise or Service, you can run Recovery for Interbase from command line and use these calls in your batch files. Standard version does not support command line. The format for command line call is:
ibr.exe <original filename with path> "<path to directory to store the recovered file(s)>"
(without angle brackets).
Please note that the directory for recovered file(s) should be created before starting the recovery.
Command line mode supports patterns '*' (replaces group of symbols) and '?' (replaces one symbol).
|
| Q: |
After running Recovery for Interbase on the corrupted database, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new database? |
| A: |
To recreate database, process resulting sql scripts starting with schema.sql and following by dataNNNN.sql. The database will be recreated from scratch. To make the import procedure more convenient for the end-user an appropriate batch file is automatically created and put in the same folder as sql script(s). |
| Q: |
Processing of sql scripts created by Recovery for Interbase does not rebuild the database and/or produce any error messages. What is the problem with? |
| A: |
In addition to script(s) the assisting batch file runme.bat is created to automate database rebuilding procedure. Please, run this batch file passing a path to isql.exe utility as a command-line argument (e.g. runme.bat c:\Interbase\bin\).
Also note that a database administrator password is required to rebuild database. By default, it is set to "masterkey" in all SQL-scripts created during recovery process.
To start database rebuild procedure one of three possible alternatives is possible:
- Replace manually the default Database Administrator (SYSDBA) password "masterkey" with the password required. The password should be replaced in every single script created during database recovery;
- Change temporarily Database Administrator's password to "masterkey" and after database recreation is complete change it back to the previous value;
- Input the desired password in the Password field while selecting database to be recovered.
|
Recovery for Interbase Error Messages
| Q: |
Recovery for Interbase Error: Internal Program Error message. |
| A: |
Run Recovery for Interbase in a logged mode and contact our support team with detailed description of the problem and the log file.
To create log file, please hold the SHIFT key while clicking the Recover button on the toolbar of Recovery for Interbase or selecting the Recover: item in the main menu. You can also press CTRL+SHIFT+R after launching Recovery for Interbase. |
| Q: |
Recovery for Interbase Error: Not enough disk space. |
| A: |
To fix this problem you need to set temporary directory to the drive with free space available (2-3 times of the original database size). Fix the Windows environment variable to use it. Do the following:
- Open System in Control Panel.
- On the Advanced tab, click Environment Variables, then click the name of the user variable (TEMP or TMP) you want to change.
- Click Edit to change value.
- Set path to the location where temporary data should be stored (e.g., e:\).
- Restart computer for changes to take in effect.
- Run the software again.
You can also use the special environment variable called OFFICERECOVERY_TMP to set the directory where Recovery for Interbase should store its temporary files. Use the method shown above to add/edit environment variable. |
Interbase / Firebird Error Messages
|
|
Product Guide |
|
|
|
