ObjectDB ObjectDB

Internal Website Search

11-20 of 69 resultsRefresh

Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x

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 ERROR ... for our software release. Please find the database file after repair binitbhaskar Binit Bhaskar In

InternalException when reading a HashMap

. Please give us some advice how to repair the damaged file and how to recognize this kind of mistakes earlier ... and also fix the database. Another thing that you can try is running the Doctor in repair mode ... DB and we'll try the repair mode. I am not sure if we would be able to provide the database

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

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

Failed to resize file - file system limitation error

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

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

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

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

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

Deleting a broken reference that was fixed to null in the Explorer

Using version 2.7.4_01, we did a repair. After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support