15 | Safe Settings get corrupted database files in any possible case. I found "recovery" and "recording" in the objectdb.conf file ... 2 separate mechanisms for recovery from failure: Recording (transaction log). Recovery (double ... and in other cases recovery is faster. Only one of the two has to be enabled in order to have a safe |
13 | Filename.odb$ Persisting Issue to me) and doesn't always get removed when the application is terminated. This is the recovery file and you can disable recovery if you want, although not recommended, and then you will not have this file at all. The recovery file is removed when the EntityManagerFactory is closed, but apparently |
13 | errors on repair copying a database file when it is in use (the copy may be corrupted), disabling recovery, or discarding the recovery file when exists (e.g. by moving the database file without its associated recovery file |
11 | ObjectDB stability after power failure has two different mechanisms that should enable fully automatic recovery on power failure: Recovery File |
11 | virtual servers and one file> <size initial="16mb" resize="16mb" page="2kb" /> <recovery enabled="true" sync="true" path="." max ... > <database> <size initial="16mb" resize="16mb" page="2kb" /> <recovery enabled="true" sync="true" path |
11 | OutOfMemoryError on search after update on DB created with DB DoctorIt looks like there may be an issue with the DB files created with DB Doctor in recovery mode. This is the scenario that results in the OutOfMemory exception problem (using Object DB 2.5.4_04): 1 ... DB Doctor in recovery mode to generate a recovered DB file. No schema (and index) changes - just |
11 | OutofMemory error with Object DB 2.0 Contents of the objectdb.conf file (also attached). I think I have disabled recovery ... " /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery enabled="false |
11 | 500Mb ObjectDb database opening issue500Mb ObjectDb database opening issue |
2 | database corrupt="*" level="info" /> </general> <database> <size initial="256kb" resize="256kb" page="2kb" /> <recovery ... The one setting that might make the difference (hopefully) is: <recovery enabled="true" sync="true" path="." max="96mb" /> It should force physically writing to the recovery file before starting to write |
2 | ArrayIndexOutOfBoundsException on flush recovery before this happened? Do you have the full transaction history (recording) in an odr ... by objectdb (i.e. on a clean file system). It hasn't been moved or copied 4) No recovery |
