About Doctor

71-80 of 161Refresh
Result
1

ObjectDB version 2.4.4

Version 2.4.4 Improved memory management when handling very large transactions (issue #935). Improved the Doctor to handle additional situations. Added support in retrieving metamodel ... primary key fields in queries. Fixed a regression bug of duplicating new objects on merge. Fixed a Doctor bug that caused false alarms.
Result
1

ObjectDB version 2.5.0

a package level JDO sequence using getSequence (issue #1074). Fixed false Doctor warnings when updating the schema using external classes. Fixed Doctor's index rebuilding to use NULL values
Issue
1

com.objectdb.o.InternalException

Could you please check the database file for errors using the ObjectDB Doctor? Is this error consistent? i ... it in more detail. I'll then try "ObjectDB Doctor" first. You may close this issue for now. Thanks Leon   Aquarius
Forum
1

com.objectdb.o.NLV cannot be cast to com.objectdb.o.CMV

Doctor in repair mode. If you can upload the database (possibly in a private support ticket ... the indices with the Doctor tool and it did not help. Then we deleted the DB file, and re-created
Forum
1

errors on repair

we are using version 2.6.7. On running the doctor we have message like free page list broken ... unexpected total page count ... what could be the reason for this ?   Unfortunately these are critical ... ' occurs every time when we run the doctor after ending our application - we do not do any copy or
Forum
1

Exception when dataset bigger than treshold

- with 96MB can run this query in memory, so no temp files. Doctor works fine with low treshold values ... server is running as odb user and odb group. Doctor on the same database, which is quite big: -rw-r
Forum
1

Failed to read the value of field using reflection (error 363)

that you check the database file with the ObjectDB Doctor, and use it to fix the database, if necessary ... version (2.5.4_03)? In addition, please check the database with the ObjectDB Doctor and post
Forum
1

index - data rewrite

earlier versions new indexes had no effect until the database was rebuilt using the Doctor. What ObjectDB ... objects? fields related to the new index? Have you checked the database using the Doctor
Issue
1

InternalException

. Please run the Doctor to check the database file. Can you also upload a sample database? I've attached 3 affected databases and the doctor output which is similar for all of them. I still don't
Issue
1

InternalException

your database with the Doctor to verify that the database file is fine. If you could post a sample database with the query that causes this exception it may help. I stopped the DB and ran the Doctor