Internal Website Search

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 which fails ... the database and possibly repair it (by finding why the Doctor doesn't repair it and improving the Doctor

the index the database has to be rebuilt by running the Doctor in repair mode. After fixing the index ... process spawn) to to repair .  I got the following log when using doctor 11-Sep 14:55:33 ... unexpectable for our software release. Please find the database file after repair binitbhaskar Binit

. Please give us some advice how to repair the damaged file and how to recognize this kind of mistakes ... repair mode (even if errors are not found) and then, maybe the result database would work ... keep investigating with the broken DB and we'll try the repair mode. I am not sure if we would be able

references 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

] Unexpected total page count: 512 (expected 449). On repair the db some of query are not working ... Manoj Kumar Maharana  On repair the db some of query are not working. Have you run the Doctor in repair mode? Which queries don't work? Please provide more details. support Support I have attached

in repair mode and check whether you still have the errors with the new generated (fixed) database ... , and regarding the Doctor errors, consider: (a) repairing the database and switching to the new generated ... .concurrent-file-read=true) . If set to true , try false . If not tried already, try to repair

errors. Run 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. Automatic index rebuilding (" ") does not correct the database. So, in summary, I

" query. Please discard or repair using the Doctor any databases on which this query was run to avoid ... done Doctor repair now we have an 'Unexpected internal exception' cause 'java.lang ... . You have to run the statistics query again on the repaired database. If it is not a production

) and either start with a clean database or fix this database by running the Doctor in repair mode ... of the property at #3. support Support Build 2.1.1_08 produces the exception below. I've tried repairing ... database files by running the Doctor in repair mode (with 2 arguments): java -cp objectdb.jar com

in repair mode (even if no errors are found by the Doctor). You may also disable an optimization ... . Also with the outcome of the Doctor in repair mode. But after many experiments I found out that the Query works ... itself cannot be affected by the bug (so no need to repair it with the Doctor) but various queries