Recovery for Interbase Frequently Asked Questions
If you have a problem that is not covered by this FAQ, do not hesitate to contact our technical support team.
Can Recovery for Interbase recover my InterBase/Firebird database(s)?
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 Download Demo page to get a free copy of the demo.
Product specifications with lists of items recovered and not recovered is available at the Product Information page.
Always backup your original corrupted InterBase/Firebird database before proceeding with any recovery activity!
I have tried the demo. How do I decide whether to purchase the full version of Recovery for Interbase?
You can decide this by evaluating the results of demo recovery. The demo version recovers a limited number of rows in each table of the recovered InterBase/Firebird 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.
For more information see the Recovery for Interbase online help.
What is the difference between Standard License and Enterprise License?
The license type refers to the number of copies to be used simultaneously. Standard license is intended for small business and individual use. One license allows one installation of Recovery for Interbase and servicing an internal domain up to 50 computers. Primary user of the computer where the Recovery for Interbase is installed may have another copy on their portable computer for exclusive usage.
Enterprise license gives the right to install two copies of Recovery for Interbase and servicing an internal domain of 250 computers total.
Both types of license do not have any limitations on the number, size and authorship of the InterBase/Firebird databases to be recovered.
Please, note that to use Recovery for Interbase in data recovery service you have to obtain the annually renewed Franchise license!
See License Information page for full disclosure and assistance.
Why do recovered files contain less data than the original InterBase/Firebird database?
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 InterBase/Firebird database are not supported and therefore appropriate data is absent from the resulting files.
Demo-recovered files mostly consist of demo placeholders than actual data from the original InterBase/Firebird database.
I'm getting an Internal Program Error while using Recovery for Interbase. What can be done?
Please, 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 or selecting the Recover: item in the main menu. You can also press CTRL+SHIFT+R after launching the program.
I'm getting an error message that there's not enough free space. Is there a workaround for this?
Yes, if there is other drive with free space available (2-3 times of the original InterBase/Firebird 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.
Is there any way to run Recovery for Interbase from command line (through Windows Start -> Run menu)?
Yes, you can easily run Recovery for Interbase from command line and use it in your batch sceneries. The format for this 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).
After running Recovery for Interbase on the corrupted InterBase/Firebird database, a folder with sql script(s) and batch file has been created. How could these files be transfigured into a new InterBase/Firebird database? To recreate InterBase/Firebird database, process resulting sql scripts starting with schema.sql and following by dataNNNN.sql. The InterBase/Firebird 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).
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?
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.
|
