About diagnosis

11-18 of 18Refresh
Issue
2

Error on commit

running it in diagnosis mode. Anyway, since the problem is solved and there is no way to reproduce
Issue
2

InternalException in Database Doctor

when the database is opened by the Doctor during diagnosis. This is disabled now in build 2.6.9_08 so it should solve the exception. Thank you for your report. jakab
Forum
2

Join query problem with new statetment

objects and the new entity objects. For more precise diagnosis - please post a sample case that reproduces
Forum
2

Objectdb Doctor

: Running the Doctor in diagnosis mode once in awhile during development and testing can help in
Issue
2

Page cache File handling produced an java.io.IOException: Negative seek offset

.Thread.run(Thread.java:745) Build 2.6.7_02 adds some diagnosis checks in order to produce a better
Forum
2

Queries are slow on a large database

. For diagnosis please try the same query without the ORDER BY clause. A composite index in
Forum
2

Query becomes slower on moving from ObjectDB 1.x to ObjectDB 2.x

itself can diagnose problems in the database (when running in diagnosis mode) but currently inactive indexes
Issue
2

Querying error - java.lang.ClassCastException: com.objectdb.o.STV

the fix by using the Doctor in diagnosis mode). Check if your application can bring the database