About Doctor

forum_thread

Objectdb recovery

Hello, I have question regarding objectdb recovery when objectdb is not finished correctly (power outage). We are using following configuration: <recovery enabled="true" sync="false" path="." max="128mb"/> <recording enabled="false" sync="false" path="." mode="write"/> Is there any possibility of data loss when power outage? ... database file after such events by running the ObjectDB Doctor. Regarding data lose, recovery returns your database to the most ...

 
forum_thread

Replication Error

Hello! I try to get a replication setup working on two test servers. So i copied my test database to one of them, enabled recording and started odb. The dbname.odr folder got created so i think everything is ok. Afterwards i added the replication tag to the configuration of the second server and started it. The second server starts complaining instantly with the following Exception: ... seconds. I already tried to fix the db with the doctor. No error is found. I use the latest version of ObjectDB. ...

 
forum_thread

Remove not working

Hello! We have a strange problem. ... Newest version of ObjectDB. No errors if I run the doctor. I've reduced my testcase to this: @ Test @ ...

 
forum_thread

JDO @Index in JPA?

Hi! I have a project which has all entities as JPA entities. I would like to make use of indexing, which I know that it's not available in JPA, but ObjectDB works with JDO as well. Question1: will adding JDO @Index in a JPA entity have any effect or I have to switch that entity to JDO? Question2: switching entities from JPA to JDO can happen when there is already data in the database? Or do I have to delete the previous data and start with a fresh db? Thank you. ... has non indexed instances stored in the database - use the Doctor to rebuild the index  in a new copy of your database. ...

 
issue

[Explorer] Running Tools

The new Explorer of ObjectDB 2 does not support running tools from within the Explorer. The Explorer should support running ObjectDB tools, such as ObjectDB Server, ObjectDB Doctor, etc. from within the Explorer, visually. 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.... ObjectDB tools (such as ObjectDB Server and ObjectDB Doctor) visually within the Explorer. This is one of the features that ...

 
issue

NULL reference, how to remove

we have in our db these objects, how can we remove them (we did already a -cp Doctor):     ... objects, how can we remove them (we did already a -cp Doctor):     ...

 
forum_thread

A few entities loss after update to 2.3.7_08!

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. ... 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 ...

 
forum_thread

ClassCastException on closing PersistenceManager

Hi, I am using ObjectDB 2.6.3.b03 via JDO. Today I got the following exception while closing the PersistenceManager after reading the DB: ... the DB. I replaced the non-working DB file (although the Doctor was saying the Db file has no errors) with an older backup and the code ...

 
forum_thread

Connection performace after upgrade to objectdb 2

Hi, I have a problem with objectdb 2 when I tried to get the PersistenceManagerFactory and PersistenceManager : In objectdb 1 : PersistenceManagerFactory pmf = JDOHelper.getPersistenceManagerFactory(getProperties(physicalPath, objectName), JDOHelper.class.getClassLoader()); takes only 3ms PersistenceManager pm = pmf.getPersistenceManager(); takes 40ms However, with objectdb 2, the same instructions take respectively : 257ms and 238ms which is very expensive. ... two odb file for version 1 and 2. ps. I run the doctor this odb file, indexes seems to be fine Regards,   ...

 
issue

Can't open DB-file with explorer, but from within my code it works

Hi, The problem occured since an update from my old-version (2.4.7_08) to the new version(2.4.7_18): 1) my recent db-file, created with the old-version, has been copied to the local db-folder of the new version automatically 2) But I can't open the db-file with the objectDB explorer, neither with the old-version, nor with the new version. The error message shown in a message-box is: ... (from within my code) without any errors 4) the db doctor ends without error messages Scanning the database file... 0MB ...