Internal Website Search

1-23 of 23 results

Database Doctor

The ObjectDB Doctor tool provides two related services: Diagnosis and validation of an ObjectDB ... , and if the file is not valid (it is corrupted), produces a detailed diagnosis report of all the errors. Repair ... running ObjectDB Doctor's diagnosis regularly in order to identify potential problems early

getting "Unexpected total page count" error when diagnosis mu db by ObjectDB doctor.

When am diagnosis my db it gave following report Global Value Errors ------------------- [1] Unexpected total page count: 512 (expected 449). On repair the db some of query are not working. can you please tell me what does the above error mean and how can i resolve this? Thanks   Manoj

ObjectDB Object Database Features

- supports full transaction recording and replaying . Automatic diagnosis and repair of corrupted

Mismatch client-server protocol prefix

configuration and see if it makes a difference (for diagnosis ): ... .. Check also the possibility ... performance a bit or may not, but if it eliminates the issue it will help for diagnosis . It is definitely

Objectdb Doctor

can help in this context in two ways: Running the Doctor in diagnosis mode once in awhile

Join query problem with new statetment

the database - the old embeddable objects and the new entity objects. For more precise diagnosis - please post

General Performance Issues Illustrated with a Specific Method

and post the results:     support Support In addition, you should try (for diagnosis ): The same

virtual servers and one file

the hardware. If you can publish diagnosis info of the slow activity it might help. support Support Thank

Memory Leak in EntityManagerFactory ?

it. Anyway, if this diagnosis is correct then a possible solution on your side may be to check and commit

Queries are slow on a large database

, all the objects have to be retrieved. For diagnosis please try the same query without the ORDER BY clause

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

the database (when running in diagnosis mode) but currently inactive indexes are not detected

ObjectDB Unable to process 1.6 L records.

Hi  I have a db of around 1.6 lakh records. But now am getting some unexpected error when accessing some of the entities. And when am fetching all the records using objectdb explorer its showing exception. I have diagnosis the db with objectdb doctor but not find any error. Please check

Indexes broken after schema update

for there to be no errors found in the diagnosis yet the repair still fixes a problem? As I saw no problems when running the Doctor diagnosis hence I didn't run a repair, did you see the same? bensteele Ben Steele The database record history may help. You are right about running the Doctor diagnosis

Unexpected not reproducable exception during commit

information to the log when this exception is thrown, for further diagnosis . support Support Hello ... when this exception is thrown, for further diagnosis , if it happens again. support Support Build 2.7.6_02

InternalException in Database Doctor

when the database is opened by the Doctor during diagnosis . This is disabled now in build 2.6.9_08

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

(and then verify the fix by using the Doctor in diagnosis mode). Check if your application can bring

[ObjectDB 2.3.7_25] Unexpected exception (Error 990)

only diagnosis mode and a new fix (in build 2.4.0_03) should also handle repair mode

database corrupt

, we can try working with you on diagnosis of this issue, but we will need more information. For example, does

Errors in log to repprt

is needed. If you want to be sure you can run the Doctor in diagnosis mode first (possibly

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

) btc_es BTC EmbeddedSystems Build 2.6.7_02 adds some diagnosis checks in order to produce a better

Error on commit

and that problem may be solved by running the Doctor in fix mode, but not by running it in diagnosis mode

Corrupt database page

corruption. Can you share the database file for further diagnosis ? support Support Unfortunately

ObjectDB 2.6.7

Added an option to write javaagent enhanced classes to file ( for diagnosis ). Extended temporary files support to update queries ( issue #1658 ). Improved performance of handling multi activations configuration. Fixed a synchronization bug in using temporary files in large transactions. Fixed