15 | NullPointerException in ENH.g(ENH.java:401) using the ObjectDB Doctor, and if necessary use the Doctor to repair the database. support Support Hi, I already used the objectdb doctor tool but the issue remains (I analysed and repaired). The entity ... We can check the database and possibly repair it (by finding why the Doctor doesn't repair |
13 | getting "Unexpected total page count" error when diagnosis mu db by ObjectDB doctor.When am diagnosis my db it gave following report Global Value Errors ------------------- [1] Unexpected total page count: 512 (expected 449). On repair the db some of query are not working ... Maharana > On repair the db some of query are not working. Have you run the Doctor in repair mode |
13 | Objectdb Doctor with null values) in an existing database file you can run the Doctor in repair mode. This cannot replace fixing the application but it is an easy way to repair a specific database. support Support great thanks, I'll run in diagnostic mode, see what I get, then run in repair mode |
10 | 500Mb ObjectDb database opening issue, and then, if it is an issue with ObjectDB we will probably can repair it. Try to isolate the issue from ... the issue and repair it already). Therefore, we have no way to proceed without your help. You tested |
3 | ObjectDB 2.7.2_x Doctor Yields "Index Requires Rebuild" Always ObjectDB 2.7.2 (or later or earlier) Doctor with repair and create repaired.odb. repaired.odb will still show indexing errors when ObjectDB 2.7.2 (or later) Doctor is run on the "repaired" database |
2 | combined index not used better. There was a critical bug in running the "objectdb statistics" query. Please discard or repair ... whether or not the new build runs queries faster now. support Support done Doctor repair now ... statistics. You have to run the statistics query again on the repaired database. If it is not |
2 | Querying error - java.lang.ClassCastException: com.objectdb.o.STV database or fix this database by running the Doctor in repair mode (and then verify the fix by using ... . support Support Build 2.1.1_08 produces the exception below. I've tried repairing the database ... the Doctor in repair mode (with 2 arguments): > java -cp objectdb.jar com.objectdb.Doctor old.odb new |
2 | Internal Exception and Index Problems. However it is very easy to fix the index by running the Doctor in repair mode: > java com.objectdb.Doctor error ... and after that repairing the database with the doctor in repair mode. The main issue |
2 | InternalException when using MEMBER OF on a large list in a query with the Doctor. If the error repeats, try to fix the database by running the Doctor in repair mode ... the exception by execute the Query in the explorer. Also with the outcome of the Doctor in repair mode ... to repair it with the Doctor) but various queries can fail with versions of ObjectDB before the new build |
2 | log entry and massive performance issues that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor)? In addition ... was found. You may want to try repairing the database with the Doctor to see if it solves the new |
