About Doctor

51-60 of 161Refresh
Issue
2

com.objectdb.o.InternalException: null

? Could you please check the database file with the Doctor and post the result report? The cause of the original ... embedded mode. The result of the Doctor check is: %> java -cp bin/objectdb.jar com.objectdb.Doctor db/firstinsurance.odb_corrupt db/firstinsurance.odb_corrupt2 ObjectDB Doctor [version 2.5.4_01
Forum
2

Failed to commit transaction: Attempt to commit a rollback only transaction

. Is that possible?   I don't know. Check the database file with the ObjectDB Doctor and look ... . Should ditch client/server mode and go back to embedded?   Could you run the ObjectDB Doctor ... to a production database.   secondly, running the doctor, shows this: Missing Objects (Broken
Forum
2

Out of memory

. Something is really wrong with new build. First, every time I run Doctor or server, ODB is creating ... .java:722) Database is repaired with Doctor, now errors have been found. Please try build 2.4.3_03 ... .3_06. It looks like everything works fine with latest build. However message from doctor: Global
Issue
2

cannot delete objects after crash (see issue 2283)

objectdb  meanwhile the database became completely unusable, we had to stop and run the Doctor. Find attached the latest log   When the Doctor completes please post its output. Exploring the cause of the recovery failure is still in progress. we upload currently the database before Doctor
Forum
2

Question: remove and recreate an object, do the references survive ?

it has been before, do the references from other objects survive this (assuming that no Doctor is done in between ... again. Better test before, of course. is there an option to run Doctor without cleaning the orphane objects ... . Build 2.7.5_06 adds an option to disable broken reference cleaning. Run the Doctor with this > java
Result
2

ObjectDB version 2.0.0

a bug in ObjectDB Doctor. Fixed persistence.xml C/S connection property to "javax.persistence.jdbc ... query execution. Fixed ObjectDB Doctor to activate and rebuild also inactive (new) indexes. Improved ... a Server/Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool.
Result
2

ObjectDB version 2.4.6

a NullPointerException on Doctor run that removes an empty index. Fixed Doctor false alert after changing field type. Fixed an "Unexpected database state" exception when the Doctor builds a new index. Fixed
Issue
2

Cannot insert more than about 2^20 objects

Hi I have a DB with 4 entities and a total of 4 index. Once I reach 1048565 total objects in the whole DB, i am unable to insert more object, although i get NO error message nor exceptions. Doctor ...   Doctor output: ObjectDB Doctor [version 2.5.2_05] Copyright (c) 2013, ObjectDB Software
Issue
2

ClassCastException thrown when running count query

also tried to run your DB Doctor. It doesn't help. Please contact me if you need more informations ... . At least this one seems to be related to broken references. The Doctor detects many broken references in this database ... the Doctor in fix mode and that will replace broken references with null values (because broken references are not null values). mosi0815
Forum
2

java.io.IOException: Illegal seek

file by running the ObjectDB Doctor. The problem still exists after updating to ObjectDB 2.3.6_14 and checking the db file by Doctor. Maybe the Doctor cannot fix this specific issue. Try to use 2.3.6_14