Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.
Internal Website Search1-10 of 200 resultsRefresh
). DB was used by ver 2.6.9_09. I tried to fix it with ObjectDB Doctor (from ver. ver 2.6.9_09 ... How can I fix my DB? Andrzej Andrzej Domaradzki Build 2.8.6_04 includes a new version of the Doctor that can handle this specific issue. support Support
Explains how to use the ObjectDB object database Doctor tool to diagnose and repair database files and damaged Java/JPA/JDO objects.
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
, the recovery file can be used to fix the database. Recovery from failure is automatically applied by ObjectDB ... . When recording is enabled and recovery is disabled, recorded operations are used to automatically fix
must be fixed, since changing a name can cause data loss in existing databases. The @Enumerated
to null (rather thanempty collections). Fixed a critical bug in handling a very large number of entity classes (issue #672). Fixed LockModeType.OPTIMISTIC (READ) by handling it as OPTIMISTIC_FORCE_INCREMENT. Fixed a bug in optimistic locking on find by using LockModeType.WRITE. Fixed exception
and method finding problems. 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 mechanism. Fixed a bug in finding
Zwicker Hopefully you will be able to fix the database with the Doctor before restarting the server ... . Meanwhile, have you fixed the database using the Doctor and started the system again successfully? support ... corruption. For this we probably have meanwhile a fix. As regards the query, we'll try to find
. 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 a JMX Remote - ObjectDB Enhancer Agent conflict. Fixed a ClassCastException bug in complex JOIN queries
is not allocated yet. Such an object ID is fixed on commit(). For example: pm.currentTransaction ... can be fixed to delete these objects before they become unreachable. JDO portable applications should not use