About Doctor

issue

Server crash - Mismatch client-server protocol prefix

We've been having a problem where our ObjectDB server goes unresponsive every 2 days or so.  I've reviewed the server-side logs, and there are no events logged shortly before the crash.  Once the server gets in this state, it is unresponsive to bin/server.sh restart; I have had to reboot the entire server on which it's running.  The only recorded symptom is a client-side error (which fortunately gets auto-mailed to me): ... file will not help here, but just verify by running the Doctor that it is healthy. A thread dump of the server could be useful ... index, which was also flagged when I ran the database doctor on a backup of the production database.  I will be taking the ...

 
release

2.2.7

... on null value). Improved ObjectDB Doctor to handle additional issues. Improved query execution ... Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced  detached ...

 
forum_thread

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

We are using ObjectDB 2.5.1_04. The following JPQL query causes an internal exception: SELECT COUNT(r) FROM RecordingMetaData AS r WHERE ((r.mapFromCli LIKE '192.168.10.13%' ESCAPE '\')) The exception: ... You may try repairing indexes by running the ObjectDB Doctor in repair mode. If you can upload the database (possibly in a ... mapFormCli. We tried fixing the indices with the Doctor tool and it did not help. Then we deleted the DB file, and re-created ...

 
manual

ObjectDB 2.6 Developer's Guide

... Presents ObjectDB Tools: the Explorer, the Enhancer, the Doctor, etc. Chapter 6 - Configuration Describes ...

 
forum_thread

Occasionally slow requests in load testing

We are running load testing against objectdb version 2.3.7_18. The performance is generally OK, however there are quite a few "spikes" in the performance where we are getting a lot of very slow response times from the DB, around 10 - 15 seconds. Looking at the DB server process with AppDynamics we can see that most of the requests get stuck in one of 2 places: com.objectdb.o.PGC:w: line number 232 com.objectdb.o.LFL:U: line number 1068 Please see the attached callgraph examples for full stack trace examples. ... changing it have any ill effects? Do we need to run the doctor after that? Thanks, Natalia. ... with no expected ill effects and no need to run the Doctor. Internally, ObjectDB fills the new allocated pages with zeros ...

 
issue

InternalException

I'm getting a new InternalException (see below). No repeatable example as yet but will work on that and let you know as soon as we have one. If there's anything in the exception which could help us narrow down the problem please let me know. ... a schema change problem of course. 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. ...

 
forum_thread

Exception when dataset bigger than treshold

I was working on reporting service for my application and found a problem with datasets bigger than treshold set in objectdb.conf.   ... can run this query in memory, so no temp files. Doctor works fine with low treshold values and can create files in tmp for each ... ODB server is running as odb user and odb group. Doctor on the same database, which is quite big: -rw-r--r-- 1 odb ...

 
release

2.2.5

... on null value). Improved ObjectDB Doctor to handle additional issues. Improved query execution ... Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced  detached ...

 
release

2.2.6

... on null value). Improved ObjectDB Doctor to handle additional issues. Improved query execution ... Fixed a bug in fixing broken references in ObjectDB Doctor. Fixed a bug in modifying enhanced  detached ...

 
forum_thread

possible index required for improving query performance

Hi,   I have the following entity class:   @Entity @Table @Indices({ @Index(members={"relationshipType", "party"}), @Index(members={"relationshipType", "otherParty"}),     @Index(members={"relationshipType"}) }) @XmlRootElement public class Relationship implements Comparable<Relationship> { ... As I understand, we'd need to stop the DB, run the Doctor in repair mode and start the DB with the repaired file before ... code and use the class again with ObjectDB. Running the Doctor will reclaim the space that the index takes, but it is only required ...