Internal Website Search

for errors using the ObjectDB Doctor, and if necessary use the Doctor to repair the database. repaired). The entity which fails to read could be read before without any issues ... and possibly repair it (by finding why the Doctor doesn't repair it and improving the Doctor

">Doctor in repair mode. After fixing the index in that database (by running ... Doctor (using process spawn) to to repair.  I got the following log when using doctor repair binitbhaskar Binit

.7.0, but that did not make any change. Please give us some advice how to repair ... the Doctor in repair mode (even if errors are not found) and then, maybe the result database would work ... with the broken DB and we'll try the repair mode. I am not sure if we would be able to provide the database

class="code">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. then run in repair mode, and see how the application behaves, ie: handles nulls

When am diagnosis my db it gave following report Global Value Errors ------------------- [1] Unexpected total page count: 512 (expected 449). On repair the db ... ;On repair the db some of query are not working. Have you run the Doctor in repair mode

you, Clinton CAPdev CAP Dev The next step may be to run the Doctor in repair ... CAP Dev Thank you for the update, and regarding the Doctor errors, consider: (a) repairing ... already, try to repair the database file using the Doctor and then switch to the new created database

the "objectdb statistics" query. Please discard or repair using the Doctor any databases ... faster now. support Support done Doctor repair now ... again on the repaired database. If it is not a production database and you can go back to the last backup

) and either start with a clean database or fix this database by running the Doctor in repair mode ... the exception below. I've tried repairing the database with Doctor but the new file produced seems to contain ... could fix the corrupted database files by running the Doctor in repair mode (with 2 arguments):

your database with the Doctor. If the error repeats, try to fix the database by running the Doctor in repair ... repair mode. But after many experiments I found out that the Query works, if I add ... > The database itself cannot be affected by the bug (so no need to repair it with the Doctor) but various

> However it is very easy to fix the index by running the Doctor in repair mode: repairing the database with the doctor in repair mode