ObjectDB Database Search

their healthy with the ObjectDB Doctor , and if necessary, use the Doctor to repair any corrupted database files. support Support

. More information is needed. Could you please check the database file with the ObjectDB Doctor for errors ... to the log file when the exceptions were thrown as well as the Doctor output? Is it an issue

during a query execution. It is recommended to use the ObjectDB Doctor to check the integrity ... above. You can also use the Doctor to try the fix the database. If you get this error

tried also the ODB doctor on that DB file, but it wrote nothing special: ObjectDB Doctor [version 2.8

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

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

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

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

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

file, e.g. by running the Doctor in fix mode, for this setting change to take effect. The optimal

integrity and it is the application responsibility to avoid such deletion. The ObjectDB Doctor

. They are replaced with null values when the database is fixed using the Doctor . In this specific

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

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

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

though) -Objectdb v2.4.0_03 -db was converted from 1.04 then fixed by the Doctor with no errors. -I

the server? You should also check the database by running the ObjectDB Doctor , since this exception

run the doctor this odb file, indexes seems to be fine Regards,     majid Mohamed El

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

the database with the ObjectDB Doctor . But please do that in a separate thread in the issue tracking.  

the database using the ObjectDB Doctor . If you post a test case that demonstrates the problem

, run the ObjectDB Doctor (in fix mode) to build the index (otherwise the index will not be used). By

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

with the Doctor tool and it did not help. We also deleted the DB file and re-created the DB from scratch

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

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

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

... all work fine.   DB Doctor does not fix the problem. We need guidance on how to debug

to protect your data. Finally, if everything goes wrong you can use the Doctor to fix the database. In

accessing the data. If you add a new index to an existing database use the Doctor to create a new database

. This was soluted with " doctor " jastorga Juan Thank you for this report and for the update. You closed the issue, as the the database was fixed with the Doctor , but if you have more information about the cause

it possible that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor )? In ... nothing that can explain the reported issues was found. You may want to try repairing the database with the Doctor

We have since a while these entries in the log, please inform if this needs a repair ( doctor ):   ... is needed. If you want to be sure you can run the Doctor in diagnosis mode first (possibly

when checked by the Doctor . support Support Yes, I still see that exception after restarting the server. However, the exceptions disappeared after I checked with the Doctor . Thanks!!  eko EKO FAJAR

have permission to write to that directory and whole application fails. Sometimes it helped to run a doctor ... yet what are the specifics of the issue. The issue for which Doctor did not fixed the issue produces only following Message

The Explorer should support running ObjectDB tools (such as ObjectDB Server and ObjectDB Doctor ) visually within the Explorer. This is one of the features that have been supported by the old Explorer of ObjectDB 1. It has been temporarily removed due to incompatibility with the new ObjectDB 2 code base. support Support

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

Added support for JTA and Java EE Containers ( issue #8 ). Fixed a bug in indexing entity objects. Fixed a bug in fixing broken references in ObjectDB Doctor . Fixed a bug in modifying enhanced detached embedded objects. Fixed a spring transformer (LoadTimeWeaver) problem. Fixed a class

Added full support of JPA 2 Criteria Queries API ( issue #10 ) Added full support of JPA 2 Metamodel API ( issue #9 ) Added non optional field validation (throwing an exception on null value). Improved ObjectDB Doctor to handle additional issues. Improved query execution planner. Improved

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

. Please check your database file using the ObjectDB Doctor . Build 2.2.9_11 includes an attempt

. Fixed a Doctor and Replication regression (Type session exceeds timeout). Removed  Conflicting modifiers  validation check and error message.

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

Unfortunately the database that you have uploaded is totally corrupted (as shown by running the Doctor

with the database? Can you check it with the Doctor ? support Support Ok, sounds reasonable

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

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

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

#978 ). Fixed a class loading issue during automatic class scanning. Fixed a Doctor deadlock . Fixed

-file programatically (from within my code) without any errors 4) the db doctor ends without error