Such a message can occur because of database corruption. This can happen with the stand-alone default installation or with the network Firebird Server configuration. It is usually casued when the database file is directly accessed when something else is already supposed to be the only thing to access it. For example, corruption may occur if using stand-along installation of AyaNova if you copy the AyaNova database while you are presently logged into the program Or another example, if you are using the netowrk Firebird Server configuration, is that you directly copy the AyaNova database while the Firebird Server is supposed to be the only one ever accessing it.
A possible way to fix this is that you need to perform a Firebird backup and a Firebird restore, and the restored database may have the corruption repaired. If you are using a stand-alone default installation of AyaNova, send the following to support@ayanova.com if you do not have the Firebird Server 1.5 installed and running: - identify the error message you receive, and exactly what you are doing that results in this message. For example, if you receive this error trying to delete a client, tell us that plus the name of the actual client you trying to delete.
- zip up your AYANOVA.FDB database file using WinZip and attach to your email
- include in your email the AyaNova Administrator username and password
- also zip up the ayalog.txt file using WinZip and attach as well
Otherwise, if you do have the Firebird Server 1.5 installed and running (or Firebird 2 if using AyaNova 4): 1. First, run a gfix against the database to confirm it shows errors (similar to below, but enter your own path and your own user and password for Firebird) gfix -v -full C:\AyaNovaData\AYANOVA.FDB -user SYSDBA -password masterkey If there are errors, they will show such as Summary of validation errors
Number of record level errors : 1
Number of database page errors : 49 If there are not errors, than you know the database is not corrupted. 2. If the database shows errors and is corrupted, perform a backup of the AYANOVA.FDB database (refer to the AyaNova v3 Manual section "Backing up using the network Firebird server" page 587 or the AyaNova 4 Help section if using AyaNova 4) 3. Then perform a restore of the database. (refer to the AyaNova v3 Manual section "Restore the database with a network Firebird server" page 590 or the AyaNova 4 Help section if using AyaNova 4) 4. Now run the gfix as outlined above again. If errors no longer show, than the database corruption has been fixed. If errors continue to show, backup and restore again. If errors continue to show, than the database is not recoverable and you will need to restore from your backup from before the corruption occurred.
- AyaNova Sales & Technical Support
- http://www.ayanova.com
|
Posted 10/28/2007 9:12:42 AM
