ObjectDB ObjectDB

Internal Website Search

21-30 of 182 resultsRefresh
106

DB Doctor sets type to "unknown" for new fields

Hi, we are using ObjectDB 2.5.4_04 on Linux. We added two new Boolean fields to a persistable type and run DB Doctor on the exiting DB file in order to update the schema. The fields are added ... DB file is what was produced by DB Doctor after adding the emergency and broadcast fields. If you run
106

DB Doctor with Recording enabled and using Database replication

When we need to run doctor on some DB file, which is used on ObjectDB master server. I suppose, that we need in that case delete recording data, and copy fixed file manually also to all slaves? Or is there any simpler way? thamal Tomas Hamal Yes, if you run the Doctor to fix a database, i.e. create
103

Deadlock in Doctor

Hi, Doctor from latest build has some kind of deadlock when writing new version of database file: [378554] pl.hplxtool.model.Product(6):8936610 Referenced by:   - pl.hplxtool.model.Offer(46):8936608 [378555] pl.hplxtool.model.Product(6):8936616 Referenced by:   - pl.hplxtool.model.Offer(46
22

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 in that database (by running the Doctor) the query runs fast. support Support Thanks. i will check ... commandLine = java -cp objectdb.jar com.objectdb.Doctor old.odb new.odb As i am doing this inside
16

Schema migration - long to String

our model and repairing database with doctor, most of our entities is gone. Doctor puts some errors ... . Actually such schema changes are not related to the Doctor, and usually you don't have to run the Doctor after the schema change (you may need to run the Doctor if the field is indexed). Every old
15

ObjectDB Object Database Features

. Automatic diagnosis and repair of corrupted database files (the ObjectDB Doctor). Standard Persistence ... Doctor Diagnoses if a database file is healthy and identifies possible problems. Automatically repairs
10

ObjectDB 2.8 Developer's Guide

ObjectDB Tools: the Explorer, the Enhancer, the Doctor, etc. Describes the ObjectDB configuration
3

[ObjectDB 2.3.7_25] Unexpected exception (Error 990)

java -cp objectdb.jar com.objectdb.Doctor ~/athene.odb.old ~/new.old [...] Creating a database copy ... ) at com.objectdb.Doctor.main(Doctor.java:22) [ObjectDB 2.3.7_25] null lorenz2304 Benjamin Lorenz ... . It will be easy to generate a new ObjectDB build in which the Doctor will report the problems
3

again merger missing logs + objectdb exception

Zwicker Hopefully you will be able to fix the database with the Doctor before restarting the server ... . Meanwhile, have you fixed the database using the Doctor and started the system again successfully? support ... . The Doctor also lists many broken references. Broken references could be application issue
3

Querying error - java.lang.ClassCastException: com.objectdb.o.STV

is updated and become larger / smaller. As a first step - could you please run the ObjectDB Doctor ... Doctor is below. I'll try your other suggestions later this morning. ObjectDB Doctor [version 2.0.5 ... database or fix this database by running the Doctor in repair mode (and then verify the fix by using

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