ObjectDB Database Search

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

'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

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

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