Internal Website Search

Explorer). DB was used by ver 2.6.9_09. I tried to fix it with ObjectDB Doctor (from ver.  ... .Doctor.main(Doctor.java:22) [ObjectDB 2.6.9_09] null How can I fix my DB? Andrzej

Using version 2.7.4_01, we did a repair. After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer   hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support

during a write to the database, the recovery file can be used to fix the database. Recovery from ... to automatically fix a database that has not been closed properly by running the

can be represented internally by their names. In that case, the names must be fixed, since changing

> Fixed a critical bug in handling a very large number of entity classes (issue #672). Fixed LockModeType.OPTIMISTIC ( Fixed a bug in optimistic locking on find by using

. Fixed a bug in the results of IS [NOT] NULL queries. Fixed a bug in ObjectDB Doctor. Fixed persistence.xml C/S connection property to "javax.persistence.jdbc.user". Fixed a bug in the new log based (recording) recovery from failure

Zwicker Hopefully you will be able to fix the database with the Doctor before restarting ... corruption) in the next days. Meanwhile, have you fixed the database using the Doctor ... of, not connected in general to the database corruption. For this we probably have meanwhile a fix

> Fixed a bug in handling remove and persist of the same object in one transaction (issue #2027). Fixed objectdb.jar to include META-INF/MANIFEST.MF as the first entry (required by Apache Karaf). Fixed a cache bug in

> Changed fetch of collection elements. Fixed a bug in query plans that use an inherited index. Fixed an ArrayIndexOutOfBoundsException bug in using nested embedded objects. (issue #415). Fixed

is not allocated yet. Such an object ID is fixed on commit(). For example: fixed to delete these objects before they become unreachable. JDO portable applications