ObjectDB ObjectDB

Internal Website Search

41-50 of 182 resultsRefresh
13

com.objectdb.o.UserException: Failed to generate dynamic type

the Dr to see and I got the following error: java -cp objectdb.jar com.objectdb.Doctor ../db/DB_1.odb ObjectDB Doctor [version 2.6.1_05] Copyright (c) 2015, ObjectDB Software. All rights reserved ... .objectdb.o.DMR.D(DMR.java:253) at com.objectdb.o.DMR.B(DMR.java:164) at com.objectdb.Doctor.main
13

ArrayIndexOutOfBoundsException

. If restarting the ObjectDB server doesn't help, try to use the ObjectDB Doctor, first to check the database ... to run the Doctor and it found some indices it needed to rebuild and after they were rebuilt using the doctor the same behavior was experienced. I then tried to delete the DB and create it from
13

Database corrupted after schema change

{ ... } with this code the app was reading TC instances normally (all fields on their place). ObjectDB Doctor did not ... (probably via the toString() method). The DB Doctor finds then errors like this in the file: ObjectDB Doctor [version 2.8.3_05] Copyright (c) 2021, ObjectDB Software. All rights reserved. Scanning
13

Queries are slow on a large database

. If you add a new index to an existing database use the Doctor to create a new database in which the index ... )results[1]; Long countId = (Long)results[2]; Now I want to use the doctor to rebuild a database ... and my old database in the same folder. Then I executed the doctor as such: java -cp objectdb.jar com
13

Date field Index is corrupted due to time change

started happening without any obvious reason. I should mention that running DB Doctor on it shows ... ObjectDB Doctor [version 2.6.3] Copyright (c) 2015, ObjectDB Software. All rights reserved ... prolancer Emil Andonov As reported by the Doctor, unfortunately this database file is corrupted
11

Error using query with MAX() function

yet. After the failure the database fails Doctor check ObjectDB Doctor [version 2.2.3_03] Copyright (c ... the entire Doctor report (in the support ticket) it might help in understanding the problem. support Support ... about the Doctor errors than the query exception. Please keep running the Doctor frequently to verify
2

Indexes broken after schema update

Could you please check the database with the Doctor? support Support > java -cp objectdb.jar com.objectdb.Doctor ../../db/user.odb ObjectDB Doctor [version 2.4.2_02] Copyright (c) 2012, ObjectDB Software ... Steele I can see in the new database that the indexes are broken. Fixing the database with the Doctor
2

Internal Exception and Index Problems

Dear Support Team, we have an urgent issue in a productive database. The objectdb doctor finds ... how this happened, and unfortunately the Doctor doesn't include checks to identify this mismatch. However it is very easy to fix the index by running the Doctor in repair mode: > java com.objectdb.Doctor error
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 (even if no errors are found by the Doctor). You may also disable an optimization that may be related ... . support Support At first, I checked the database with the Doctor. -> no Problem. I reproduced
2

database corrupt

manage the production. we have the following state of the system: - Doctor around 2 monthes ago - run our application from the 20200429, suddenly entries as it can be seen from #2559 appear - Doctor ... the database using the Doctor to get the system back in operation. In the long term, we can try working

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