Internal Website Search

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

. It is also recommended that you check the database file with the ObjectDB Doctor , and use ... )? In addition, please check the database with the ObjectDB Doctor and post the results. support Support

it have any ill effects? Do we need to run the doctor after that? Thanks, Natalia. natmaclin Natalia Levine ... ill effects and no need to run the Doctor . Internally, ObjectDB fills the new allocated pages

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

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

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

the ObjectDB Doctor . Regarding data lose, recovery returns your database to the most recent stable state

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

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

Explorer doesn't open file...see attached error message and odb.  Explorer doesn't cleanly close the connection either (due to error I presume). Many thanks Russ russ0ne Russell Martin Should add that Doctor doesn't find any issues and file works fine programmatically. russ0ne Russell Martin

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

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

ObjectDB version 2.8.7. checking the database files using the ObjectDB Doctor (you can try both 2.7

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

running the Doctor in repair mode will create a smaller database without the old entities. support Support

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

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

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

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

and you are using a version of ObjectDB before 2.6.6, you have to rebuild the database with the Doctor in

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

with the deactivated query cache works. But the question is now why? The DB Doctor does not show errors

. Currently, the way to reduce the size of a database is to use the Doctor utility, creating a new (smaller

(since  Unique is implemented as an index), and therefore requires index rebuilding  (currently using the ObjectDB Doctor ). support Support

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

. The objectdb doctor states "No errors have been found". Is there any other way to resolve this schema

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

problem of course. Please run the Doctor to check the database file. Can you also upload a sample database? support Support I've attached 3 affected databases and the doctor output which is similar

the ObjectDB Doctor ? Is this error consistent? i.e. do you get the same exception every time ... "ObjectDB Doctor " first. You may close this issue for now. Thanks Leon   Aquarius Leon Eisenberg

Improved memory management when handling very large transactions ( issue #935 ). Improved the Doctor to handle additional situations. Added support in retrieving metamodel without connection ... fields in queries. Fixed a regression bug of duplicating new objects on merge. Fixed a Doctor bug that caused false alarms.

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

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

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

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

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

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

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

we have in our db these objects, how can we remove them (we did already a -cp Doctor ):     hgzwicker Hans-Georg Zwicker More information is needed about this NULL reference. Can we have access to the database? What happens when you try to access the containing entity object? How many

Added initial support of Record entities. Implemented a new query method:  containsAnyKey . Improved field type error and internal error messages. Improved the Doctor output. Fixed a bug in using inner classes for query results. Fixed an error due to to an unused type referencing a deleted

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

you should be able to repair the entire database by running the Doctor . We will also check why you got the error in

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

less what we have here) - the database and all the file system is on an ultra fast SD drive - we did do a Doctor repair, not any

with the ObjectDB Doctor to be on the safe side). The exception is thrown by the ObjectDB server

. Fixed a  NullPointerException  in running the Doctor when new indexes have to be built

these lines? In addition, please check your database with the ObjectDB Doctor , and post the result report. support Support

with the Doctor for errors? It is unclear how and if this could be related to switching a language. support

)? 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