7 | Unexpected exception (Error 990) execution. It is recommended to use the ObjectDB Doctor to check the integrity of this specific database ... above. You can also use the Doctor to try the fix the database. If you get this error with several independent database |
7 | Occasionally slow requests in load testing to run the doctor after that? Thanks, Natalia. natmaclin Natalia Levine The way resizing works ... the Doctor. Internally, ObjectDB fills the new allocated pages with zeros and that requires extensive I/O |
7 | Shrinking Database Files would be with Database Doctor. Is there a way to reclaim database file space? Is it worth trying to reclaim ... the ObjectDB doctor in repair mode (i.e. building a new database file from an existing database). support Support |
7 | com.objectdb.o.NLV cannot be cast to com.objectdb.o.CMV details, if any. You may try repairing indexes by running the ObjectDB Doctor in repair mode ... the indices with the Doctor tool and it did not help. Then we deleted the DB file, and re-created the Db from |
7 | possible index required for improving query performance the DB, run the Doctor in repair mode and start the DB with the repaired file before accessing ... the class again with ObjectDB. Running the Doctor will reclaim the space that the index takes |
1 | ObjectDB 2.2.8 online backup with no arguments. Added option for running the Doctor without activating disabled indexes. Fixed a Doctor bug in fixing old (< 2.0) database files. Fixed a temporary file creation problem |
1 | InternalException. You should check your database with the Doctor to verify that the database file is fine. If you could post ... the DB and ran the Doctor over it and it found no errors, however, when I started the DB |
1 | ObjectDB 2.5.0 level JDO sequence using getSequence (issue #1074). Fixed false Doctor warnings when updating the schema using external classes. Fixed Doctor's index rebuilding to use NULL values for missing values |
1 | java.lang.ClassCastException: com.objectdb.o.SCU cannot be cast to com.objectdb.o.PRU with "doctor" jastorga Juan Thank you for this report and for the update. You closed the issue, as the the database was fixed with the Doctor, but if you have more information about the cause |
1 | Server crash - Mismatch client-server protocol prefix here, but just verify by running the Doctor that it is healthy. A thread dump of the server ... with a particular index, which was also flagged when I ran the database doctor on a backup |
