ObjectDB Database Search

about this specific file it may help. You should be able to fix indexes by running the ObjectDB Doctor . support Support

'demo.odb' null").  Note: I'm using Windows 7 64 bits. jdk1.6.0_27. ObjectDB doctor did not

Hi  I have a db of around 1.6 lakh records. But now am getting some unexpected error when accessing some of the entities. And when am fetching all the records using objectdb explorer its showing exception. I have diagnosis the db with objectdb doctor but not find any error. Please check

of it until we repaired and created a new db with ObjectDB Doctor . Therefore, I would really appreciate this new feature

the indices from single index to multiple indices. Running the database doctor will then remove

(although the Doctor was saying the Db file has no errors) with an older backup and the code was running

Hello, we have problems when we open our Database file with the ObjectDB-Explorer (2.6.8_b8). Can you analyze the problem and tell us if its a problem of the explorer or a real problem in the Database-File? An analysis with the DB- Doctor found no problems.   We observe the error if we try

, with new empty db it works correctly. The objectdb doctor analysis has not found an error. Clearing

The old database is created by 2.3.6. And recreate the database by doctor is useless. But the other version such as 2.3.7 works fine. So we believe 2.3.7_08 has a bug. codefad FrankChu More details are required in order to understand the problem. support Support

the db with the doctor . No error is found. I use the latest version of ObjectDB. (2.3.6_16) Do i miss

an index currently requires running the ObjectDB Doctor , which is run from the command line. ObjectDB 1

data requires rebuilding the database by using the Doctor in repair mode (a better support for adding

This happens after recreating all 3 databases with Doctor as well. It's quite strange and problematic

just running objectdb we run into a crash situation as described in the attached log. What can be the reason for such a behaviour ? Objectdb doctor just hanging completely without message after reading the database file   File:  

. The ObjectDB Doctor  reports broken references so it could be very helpful during testing and debugging

Hi, I would like to try the Online Backup tool as I am making backups up to now with the not encouraged file-copying method while the database is online. So my first question is to this file-copying. I've read at the Database Doctor that copying the db file while it is online may cause

in order to understand the problem. Please check the database with the ObjectDB Doctor . Check

; this.all = all;     } } I did run Doctor before test, after changing odb version.  

entity class that already has non indexed instances stored in the database - use the Doctor to rebuild

Hi, we started to get a java.lang.NegativeArraySizeException from ObjectDB upon changing an object in the DB and committing the transaction. I tried to repair the DB file with Database Doctor , but the same error is happening also on the fixed DB file. Btw. during fixing the DB file an Internal

. Currently the only way to activate the index is to use ObjectDB Doctor to rebuild the entire database

. Please check the database with the ObjectDB Doctor to detect errors in the database file. support Support

explorer or doctor . lwalkowski Lukasz Walkowski This schema change should be handled by ObjectDB

of ObjectDB. No errors if I run the doctor . I've reduced my testcase to this: @Test   

)? Do you still get the exception after restarting the server? Can you check the database with the Doctor

that these log entries are not created during normal use of ObjectDB but when the Doctor is run

Added support of an option to disable broken reference cleaning in the Doctor ( feature request #2341 ). Added support of cascading delete using JDO ( feature request #2329 ). Added logging for "Failed to read from file" error ( issue #2322 ). Added an option for eager background purge of weak

persistence and run the Doctor ?  Ignore it and try again?  The product will be used in

The database file that you uploaded is corrupted and you must repair it using the ObjectDB Doctor before

with the primary data. As a workaround, you can currently use the ObjectDB Doctor to build a new database file

and then start it again, do you still have the problem? Check the database file using the Doctor

Added a new Doctor .run(srcPath, dstPath) static method. Added an option to exclude inherited @Id fields in embeddable classes. Added support for manual starting of online backup threads ( feature request #2855 ). Added support for distinct mapped-by (inverse) fields. Improved query plan

the database (attached) through objectdb doctor showed broken references. I'm not sure of the exact

Improved the Doctor (see issue #2691 ).

. Maybe the index is broken. Try to fix the database by running the Doctor and check if the repaired

an Explorer bug in adding objects to collections ( issue #2078 ). Fixed a Doctor error message

. Even the Doctor does not run anymore using this index definition. We use the latest ObjectDB version 2.7

please check the database using the Doctor and report any errors. support Support

Added an option to slow backup (see  feature request #2681 ). Added an option to view old type versions in the Explorer (-Dobjectdb.ui.debug=true) Improved the Doctor (see  issue #2691 ). Improved performance following a large eager fetch ( issue #2694 ). Restricted waiting time

Added a new Doctor .run(srcPath, dstPath) static method.

objects. Removed false alarms by the  Doctor . Fixed a deadlock ( issue #2512 ) on closing

is actually on writting the objects to the db. Running the database through Database Doctor reported

Added support of deleting classes in the Explorer. Improved memory cleaning when entity objects with embeddable elements are detached. Improved handling query results that include managed hollow objects. Removed false alarms by the  Doctor . Fixed a deadlock ( issue #2512 ) on closing

; ... } Fixed problem by database repair with doctor ! Thanks! ego123 ego planet Thank

. It is also recommended to check the database using the ObjectDB Doctor .   support Support Thanks

.java:679) I'll send you my database via a support ticket. Database Doctor find's no errors. So the DB

- we restarted to try to use 2.8.1 instead of 2.7.6 - we did a doctor on the database that you can download from www.hummingbird-systems.com, login/pw your database name, main menu objectdb - we did not do any statistics generate, just tried to use the new version - our reference query that takes