Internal Website Search

The ObjectDB Doctor tool provides two related services: Diagnosis and validation of an ObjectDB ... running ObjectDB Doctor's diagnosis regularly in order to identify potential problems early on. Running ObjectDB Doctor Diagnosis The ObjectDB Doctor tool is bundled in the objectdb.jar file

Hi, Is it possible to reduce Doctor memory usage? Right now for recovering 67MB database, I need ... You may try decreasing the temporary file threshold . The Doctor will use less memory and more temporary ...  have at least 2GB RAM, I don't think that running the Doctor with 512MB max heap size

Hi, one of my DB files can not be open by neither DB explorer, nor the DB Doctor . Both are writing same mistake : ObjectDB Doctor [version 2.5.6_05] Copyright (c) 2014, ObjectDB Software. All rights ... . Doctor .main( Doctor .java:22) Caused by: java.lang.NoClassDefFoundError: quant/phdsc_new/model

It looks like there may be an issue with the DB files created with DB Doctor in recovery mode ... when searching and updating. 3. We run DB Doctor in recovery mode to generate a recovered DB file. No schema (and index) changes - just testing the use of DB Doctor to check DB files during package

We've got this exception, when running DB Doctor in parallel on multiple DB files. com.objectdb.o ... (DCM.java:183) at com.objectdb. Doctor .main( Doctor .java:22) Example command: tmpdir=$(mktemp -dp .) java -Xmx100G -Djava.io.tmpdir=$tmpdir -cp objectdb.jar com.objectdb. Doctor file1.odb fixed/file1.odb

). DB was used by ver 2.6.9_09. I tried to fix it with ObjectDB Doctor (from ver. ver 2.6.9_09, but also from newest version 2.8.6), but even Doctor fails: ObjectDB Doctor [version 2.6.9_09 ... .java:259) at com.objectdb.o.DMR.C(DMR.java:170) at com.objectdb. Doctor .main( Doctor .java:22) [ObjectDB

; trying to do a doctor on the customer system with around 40 GByte free RAM (database is around 37 ... pc, doing the doctor shows: Page Relation Errors -------------------- [1] Free page list is broken ... (which are application errors) the Doctor only reports a "Free page list is broken" error, which by

get an enormous exception. How does the ObjectDB Doctor help?   dmoshal David Moshal When objects ... , which are not stored but rather computed on the fly by executing automatic queries). ObjectDB Doctor can help in this context in two ways: Running the Doctor in diagnosis mode once in awhile

for an 'extra' feature. The class ' com.objectdb. Doctor ' enables a self-test for a given Database ... the application. best regards Arne Stocker (Advolux GmbH) Arne Arne Stocker You can run the Doctor from your application using:      Doctor .main(new String[] { ... }); Output will be written

Hi, I would like to run the Doctor in repair mode with the source file = target file but I get the following error: java -cp ../../lib/objectdb.jar com.objectdb. Doctor myDB.odb myDB.odb com.objectdb ... .objectdb.o.DMR.B(DMR.java:163) at com.objectdb. Doctor .main( Doctor .java:22) [ObjectDB 2.5.1_05

Hi, I am trying to fix database file with more than 1 million objects. The Doctor refused to finish fixing and complaining that the file exceeds evaluation limit. How to supply license to the Doctor ... ) at com.objectdb.o.DCM.j(DCM.java:183) at com.objectdb. Doctor .main( Doctor .java:22)   eko EKO FAJAR

Hi, I am unable to repair a database by Doctor . Getting following error. com.objectdb.o ... ) at com.objectdb.o.DCM.j(DCM.java:112) at com.objectdb. Doctor .main( Doctor .java:10) Caused by: java ... running the Doctor of version 2.8.9 (regardless of which version of ObjectDB you use), as

instances of these entities to database through explorer. I tried to run com.objectdb. Doctor ... explorer). Could it be possible to add that kind of feature in next relase ?   I run doctor by executing cmd like : java -cp bin\objectdb.jar;_my_model_.jar com.objectdb. Doctor old_db.db new_db

Am I reading this correctly?  It seems that Doctor is telling me that one of my objects ... though seems to show that the reference to the object is good and that the object does indeed exist.   Output from Doctor Diagnose and Doctor Repair is attached.  So are the two databases and screenshots of Explorer

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

Manoj Kumar Maharana  On repair the db some of query are not working. Have you run the Doctor in ... properly in development databases? Have you tried to fix the deployment database using the Doctor ? support Support

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

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

, the Enhancer, the Doctor , etc.             

database files (the ObjectDB Doctor ). Standard Persistence APIs ObjectDB is the only Object-Oriented

: SectionClassifier{2-merger[2699]-missing:1}     on running Doctor it hangs after reading in the database ... useful data) and the Doctor cannot help you may send it to us (in a private support ticket). This could also help us fixing the Doctor to handle this situation in the future. support Support we are using 2

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

Take a .odb created with ObjectDB 2.7.2 or later OR EARLIER.  Run ObjectDB 2.7.2 Doctor ... errors. Run ObjectDB 2.7.2 (or later or earlier) Doctor with repair and create repaired.odb.  repaired.odb will still show indexing errors when ObjectDB 2.7.2 (or later) Doctor is run

Hi, I have an issue with the ODB Doctor running endlessly on a 1.35GB ODB file.  It gets ... .  When I run the DB Doctor without a destination file (just to check the database) it quickly ... Doctor [version 2.6.1] Copyright (c) 2015, ObjectDB Software. All rights reserved. Scanning the database

very few entries have been posted to the database yet. But still the doctor reports a whole bunch of errors. My application seems to function properly though. I guess this is a bug in the doctor ? Using ... -INF/lib/objectdb-2.4.1.jar com.objectdb. Doctor /var/db/athene/athene.odb ObjectDB Doctor [version 2

Hello everyone ! I have just launched the ObjectDb Doctor for testing purposes. But while inspecting my base, the Doctor throws me a strange error : [ObjectDB 2.4.6] Invalid ID class com.test.Video ... $VideoId.sourceId using reflection) (error 316) It seems that the Doctor can't find the SourceId

Database Doctor has thrown an InternalException right after starting to diagnose or repair my DB file. The version of the Doctor used was 2.6.9_06. The stacktrace below:   Scanning the database ... .run(Thread.java:745)   jakab Gergely Jakab The execption is thrown when the Doctor is trying

.0_05, one after adding statistics and one after additional doctor , here are the results: Query ... : around 159 seconds database after additional Doctor : around 700 ms download links: https://www.dropbox.com ... , where better results are obtained with no statistics available (apparently the Doctor creates a new

/becomes unusable, see doctor report and current log, urgent help required, production of a 500 people manufacturing site shut down hgzpincher Hans-Georg Zwicker The Doctor report indicates indexes ... the Doctor in repair mode and switching to the new created database should solve the issue

Support I ran the Database Doctor and it ended up failing with the error below.  ... .objectdb.o.DCM.j(DCM.java:183) at com.objectdb. Doctor .main( Doctor .java:22) [ObjectDB 2.7.6] Failed ... may be to run the Doctor in repair mode and check whether you still have the errors with the new generated

our model and repairing database with doctor , most of our entities is gone. Doctor puts some errors ... specific action. 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

the Doctor in repair mode . The new generated database is expected to be compacted. Currently ... you for this information.  We have executed the doctor a couple times on some larger database we have.  The results were somewhat surprising.  Neither execution of Doctor found any errors

) at quant.phdsc_new.utility.Tool.deepCopy(Unknown Source)   The Doctor did not find any errors in ... earlier next time.   jakab Gergely Jakab Hi, Usually running the Doctor on every backup ... that is not detected by the Doctor , running your own tests in addition to running the Doctor

using the Object Doctor (see also this feature request ). support Support Thanks for the comments ... and rebuilding DB by this command? java -cp objectdb.jar com.objectdb. Doctor old.odb new.odb" Thanks ... and rebuild the database using the Object Doctor   I'm not sure after index changing

instances normally (all fields on their place). ObjectDB Doctor did not find on them any mistake. Then I ... via the toString() method). The DB Doctor finds then errors like this in the file: ObjectDB Doctor [version ... to fix the DB file, the Doctor deleted all listed instances of TC. Could u please help me clarify

that running DB Doctor on it shows the following issues: root@localhost totalrecall]# ./dbDoctor.sh db/SystemDB.odb db/SystemDB.odb.rpmnew ObjectDB Doctor [version 2.6.3] Copyright (c) 2015, ObjectDB Software ... the Doctor , unfortunately this database file is corrupted, so the error message that you got

the ObjectDB server doesn't help, try to use the ObjectDB Doctor , first to check the database and then to fix ... the Doctor and it found some indices it needed to rebuild and after they were rebuilt using the doctor ... of the Doctor ? Are there any errors except indexes that have to rebuilt? Type version #4 in a new database

suddenly in the log (we always do a doctor in that case but just after some hours ... the Doctor after this happens (and share the errors if any) and whether just restart helps ... , etc. after this happens. support Support Find attached the log oft he last doctor , regarding

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

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 ... it would be a great help. The Doctor also lists many broken references. Broken references could be application

is updated and become larger / smaller. As a first step - could you please run the ObjectDB Doctor ... from ObjectDB Doctor is below. I'll try your other suggestions later this morning. ObjectDB Doctor ... ) and either start with a clean database or fix this database by running the Doctor in repair mode

the ObjectDB Doctor and report errors. support Support The keys are also Strings, but I believe ... Doctor says:   ObjectDB Doctor [version 2.4.7_16] Copyright (c) 2013, ObjectDB Software ... , will you get these Doctor errors again? Could you try running the Doctor on a database that you create with values

Please check the attached database file. When running the Doctor , I get   Global Value Errors ... extra bytes   Both errors are not fixable. When creating a new db file with the Doctor ... . It may be possible to improve the Doctor in a way that these two objects will be deleted (not fixed

, so if possible, is is recommended to try fixing the database by running the Doctor . A possible ... the database by running the Doctor . Running DBDoctor from 2.8.1 shows no issues: ObjectDB Doctor ... enhanced. [2021-03-31 15:19:55 #2 tool. doctor ] com.objectdb.o.UserException: Failed to locate set method

) jastorga Juan Thank you for this report. Could you please check the database file with the ObjectDB Doctor ... . an empty database or a database that has no errors in the Doctor check). support Support In DEV after the Doctor and using the new file, I have no problem (i can't reproduce error in DEV). I think

". Check the database in the Doctor , if it is already corrupted then first fix it using the Doctor . support Support Can data in ObjectDB be lost in case of power loss or arbitrary system failure ... Doctor to see if the database is corrupted.   support Support I still get this NPE

the ObjectDB Doctor to check the database and post the report. support Support It repeats the following ... .objectdb.o.DMR.D(DMR.java:251) at com.objectdb.o.DMR.B(DMR.java:163) at com.objectdb. Doctor .main( Doctor ... (DMR.java:251) at com.objectdb.o.DMR.B(DMR.java:163) at com.objectdb. Doctor .main( Doctor .java:22

" query. Please discard or repair using the Doctor any databases on which this query was run to avoid ... done Doctor repair now we have an 'Unexpected internal exception' cause 'java.lang ... (without loosing data) - it would be better. support Support we did run the Doctor + the statistics query

) bensteele Ben Steele 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 ... are broken. Fixing the database with the Doctor solves the problem (by rebuilding the indexes

your database 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 ... with the Doctor . - no Problem. I reproduced the exception by execute the Query in the explorer