7 | ObjectDB doctor commandHi, I would like to run the Doctor in repair mode with the source file = target file but I get the following error: java -cp ../../lib/objectdb.jar com.objectdb.Doctor myDB.odb myDB.odb com.objectdb.o.UserException: Attempt to open a non existing file 'myDB.odb' at com.objectdb.o.MSG.d(MSG.java |
7 | Extending model by "common entity" the schema change again to a database that was used only with the old schema. If you must repair |
7 | Shrinking Database Files the ObjectDB doctor in repair mode (i.e. building a new database file from an existing database). support Support |
7 | ObjectDB's Database Doctor Incorrect Error Report Repair is attached. So are the two databases and screenshots of Explorer showing the reference |
7 | Object Relations Error after Schema Change running the Doctor in repair mode. If this doesn't help and you can upload the database (possibly |
7 | Deploying objectdb.jar to karaf 4.0.7 seems to fail how to repair our build process. support Support Hello, done. My jar (attached) works. 2016-12-02 13:07 |
7 | NegativeArraySizeException on commiting a transactionHi, we started to get a java.lang.NegativeArraySizeException from ObjectDB upon changing an object in the DB and committing the transaction. I tried to repair the DB file with Database Doctor, but the same error is happening also on the fixed DB file. Btw. during fixing the DB file an Internal |
1 | each 1-2 days objects on some objectdb level lock/block each other and all the file system is on an ultra fast SD drive - we did do a Doctor repair, not any error shown - ojectdb |
1 | merger missing in logwe have the following entries in our objectdb log (system continues to work normally, database was repaired before switching to version 2.7.5): [2018-05-14 15:00:48 #1 store] Database 'F:\Hummingbird\Objectdb\db\coresystemdb.odb' has been recovered (tr. 68624050-68626451) [2018-05-14 15:00:52 #2 |
1 | Errors after unexpected server shutdown which that index is defined. Alternatively you should be able to repair the entire database by running |
