ObjectDB Database Search

that running DB Doctor on it shows the following issues: root@localhost totalrecall]# ./dbDoctor.sh db/SystemDB.odb db/SystemDB.odb.rpmnew ObjectDB Doctor [version 2.6.3] Copyright (c) 2015, ObjectDB Software ... the Doctor , unfortunately this database file is corrupted, so the error message that you got

instances normally (all fields on their place). ObjectDB Doctor did not find on them any mistake. Then I ... via the toString() method). The DB Doctor finds then errors like this in the file: ObjectDB Doctor [version ... to fix the DB file, the Doctor deleted all listed instances of TC. Could u please help me clarify

_file, new_db_file}; com.objectdb. Doctor .main(args); 2.a is very expensive which means it takes a lot ... (defining indexes on the owner fields can help). Regarding the Doctor , although it is not intended ... will require your database to be offline. The last build, 2.8.9_06 adds a better way to run the Doctor from

after a server shutdown. Attached the log of the doctor run, any idea how such massive problems can occur hgzpincher Hans-Georg Zwicker The Doctor output indicates index corruption, i.e. index ... shutdown) hgzpincher Hans-Georg Zwicker by the way, are the indexes updated/rebuilt by the doctor ? in

Doctor , and if necessary use the Doctor to repair the database. support Support Hi, I already used the objectdb doctor tool but the issue remains (I analysed and repaired). The entity which fails ... the database and possibly repair it (by finding why the Doctor doesn't repair it and improving the Doctor

the database file with the ObjectDB Doctor and look for exceptions in the log file. support Support ... ; ObjectDB Doctor  on the old file and post the output? I don't think that switching from client ... , running the doctor , shows this: Missing Objects (Broken References

Support Something is really wrong with new build. First, every time I run Doctor or server, ODB ... ) Database is repaired with Doctor , now errors have been found. lwalkowski Lukasz Walkowski Please try ... .4.3_06. It looks like everything works fine with latest build. However message from doctor : Global

index you will have to rebuild it , currently using the Doctor . Before running the Doctor make sure ... index definition (either annotation in class or xml), or run the Doctor with this available in ... with Doctor . Thank you or answering the question i failed to formulate properly. lo Hoel

it has been before, do the references from other objects survive this (assuming that no Doctor is done in ... is there an option to run Doctor without cleaning the orphane objects ? hgzwicker Hans-Georg Zwicker Currently ... reference cleaning. Run the Doctor with this java -Dobjectdb.temp.no-broken-ref-fix=true Doctor support Support Perfect, thanks hgzwicker Hans-Georg Zwicker

Doctor to handle additional issues. Improved query execution planner. Improved cleanup and reusing space ... the ObjectDB Doctor of version 2.2 in repair mode on existing database files, and to switch to the new database files that are generated by the Doctor when moving to version 2.2. support Support

- please switch to build 2.3.6_14. You may have to fix your database file by running the ObjectDB Doctor ... by Doctor . codefad FrankChu Maybe the Doctor cannot fix this specific issue. Try to use 2.3.6_14

with the ObjectDB Doctor and post the output? In addition, you can try migrating the data to a new database automatically by running the Doctor in repair mode. If this doesn't help and you can upload the database ... . support Support Hi,  we tried reparing the database with Doctor , tried changing the names

with doctor ", have you an other manner to check without doctor ( work bad with my database ) ? 4 ... and a bad optimization causes this in a specified case. 2- Using the Doctor . You can also run it in

Ralph Moser Looks like very ordinary code. Could you check the database with the ObjectDB Doctor ... with ObjectDB Doctor , could you please check these queries outside of your application (e.g. in ... checked the DB two times and installed the copy generated by the Doctor . It found no errors. We use

commit the transaction. Alternatively, you run the Doctor in repair mode to create a new database file. The schema change must be available to the Doctor , so you must open the database after the schema change in your application to register the change, or run the Doctor with a classpath that contains your entity classes. support Support

). Could you please check the database file using the ObjectDB Doctor ? support Support Unfortunately I ... more felixobjectdb Richard Szurgot It could be either insertion or retrieval problem. The Doctor output

I understand, we'd need to stop the DB, run the Doctor in repair mode and start the DB ... the index from your source code and use the class again with ObjectDB. Running the Doctor will reclaim

it have any ill effects? Do we need to run the doctor after that? Thanks, Natalia. natmaclin Natalia Levine ... ill effects and no need to run the Doctor . Internally, ObjectDB fills the new allocated pages

the Doctor on it I get this exception: Caused by: com.objectdb.o.UserException: Failed to generate dynamic ... your application (not in the Explorer / Doctor ) with the new classes and with some changes to myclass1

class in the classpath in order to update the schema. Run the ObjectDB Doctor (in repair mode) to build the new index. Step 2 may be skipped if you run the Doctor (step 3) with your up to date classes in the classpath. support Support

. It is also recommended that you check the database file with the ObjectDB Doctor , and use ... )? In addition, please check the database with the ObjectDB Doctor and post the results. support Support

details, if any. You may try repairing indexes by running the ObjectDB Doctor in repair mode ... for mapFormCli. We tried fixing the indices with the Doctor tool and it did not help. Then we deleted the DB

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 ?   hgzwicker Hans-Georg ... our application - error : 'free page list is broken at page #0' occurs every time when we run the doctor

the Doctor . What ObjectDB version are you using? Because automatic activation of new indexes is a new ... to the new index? Have you checked the database using the Doctor ? Are there any errors? support Support

would be with Database Doctor . Is there a way to reclaim database file space? Is it worth trying ... smaller is to run the ObjectDB doctor in repair mode (i.e. building a new database file from an existing database). support Support

your database with the Doctor . If the error repeats, try to fix the database by running the Doctor in repair mode (even if no errors are found by the Doctor ). You may also disable an optimization ... with the Doctor . - no Problem. I reproduced the exception by execute the Query in the explorer

" query. Please discard or repair using the Doctor any databases on which this query was run to avoid ... done Doctor repair now we have an 'Unexpected internal exception' cause 'java.lang ... (without loosing data) - it would be better. support Support we did run the Doctor + the statistics query

the database is corrupted. Checking it with the ObjectDB Doctor produces errors. After using the Doctor ... Markus Ritter Did this happen again after already fixing the database with the ObjectDB Doctor ? support Support Hello, yes. I repaired the database using the Doctor . Then running the application for like 5

. Best wishes, The BTC-ES team   ObjectDB Doctor [version 2.7.1_03] Copyright (c) 2017, ObjectDB ... EmbeddedSystems Have you tried repairing the file with the Doctor ? support Support Yes, the db doctor ... system after closing the database and the db doctor is able to repair the corrupted page by the db

manage the production. we have the following state of the system: - Doctor around 2 monthes ago - run ... - Doctor today (part of the results in the attached log) how this is possible (we run into sever problems ... to fix the database using the Doctor to get the system back in operation. In the long term

the database file with the Doctor and post the result report? support Support The cause of the original ... embedded mode. The result of the Doctor check is: % java -cp bin/objectdb.jar com.objectdb. Doctor db/firstinsurance.odb_corrupt db/firstinsurance.odb_corrupt2 ObjectDB Doctor [version 2.5.4_01

, we had to stop and run the Doctor . Find attached the latest log   hgzwicker Hans-Georg Zwicker When the Doctor completes please post its output. Exploring the cause of the recovery failure is still in progress. support Support we upload currently the database before Doctor to our extranet

ObjectDB Doctor . Fixed persistence.xml C/S connection property to "javax.persistence.jdbc.user". Fixed ... . Fixed ObjectDB Doctor to activate and rebuild also inactive (new) indexes. Improved ... /Explorer class loading bug (after schema change). Fixed a bug in the ObjectDB Doctor Tool.

. During development and testing it is recommended to use the ObjectDB Doctor to verify ... integrity can be checked by the ObjectDB Doctor (offline). Eventually standard reference integrity ... references (and that can be checked with the Doctor ), avoiding reference integrity checks

to run your DB Doctor . It doesn't help. Please contact me if you need more informations. Regards ... look as the same exception. At least this one seems to be related to broken references. The Doctor ... to take effect: DELETE FROM Position p WHERE p.unit IS NULL You first have to run the Doctor in fix mode

on Doctor run that removes an empty index. Fixed Doctor false alert after changing field type . Fixed an "Unexpected database state" exception when the Doctor builds a new index. Fixed a bug in

: Can you reproduce this specific exception? Please check the database with the ObjectDB Doctor ... Support We are not able to reproduce the problem. Result from ObjectDB Doctor check is attached ... of running. Maruta M Sedlakova The Database Doctor output indicates that the database is healthy

. Doctor said Db is fine (see below) I notice that 1048565 objects + 4 entities + 4 ID indexes + 4 ... limitation. Regards   Doctor output: ObjectDB Doctor [version 2.5.2_05] Copyright (c) 2013, ObjectDB

on Sunday night.  I re-ran the database doctor on Monday evening PDT (circa 9/10 @02:40 UTC).   ... ObjectDB 2.3.x to 2.5.2. Corruption of the database that cannot be fixed by the Doctor (due to the  ... in the log after that restart, so hopefully the Doctor fixed these index issues. In that case

time, I've also tried to run the DB doctor with the following result: heintz@heintzmbp /usr/local/objectdb-2.5.6_02/bin java -cp objectdb.jar com.objectdb. Doctor ../db/my_database_file.odb ObjectDB Doctor [version 2.5.6_02] Copyright (c) 2014, ObjectDB Software. All rights reserved. Scanning

Hello, we ran the db doctor on a database. What does the following errors mean ... of these classes, as shown on the Doctor report (as actual), then you may ignore these errors. Theoretically ... it is probably not an issue. Alternatively, to be on the safe side, you may want to use the Doctor to repair the database file. support Support

the Doctor report for this database? The exception is thrown during refresh, can you check ... , we can see that always the same objects (around 4) are in charge. A doctor we cannot do currently ... then it seems that the objects are not corrupted, although it could be helpful to verify this by running the Doctor

online backup with no arguments . Added option for running the Doctor without activating disabled indexes. Fixed a Doctor  bug in fixing old (

problem of course. Please run the Doctor to check the database file. Can you also upload a sample database? support Support I've attached 3 affected databases and the doctor output which is similar

Fixed a bug of  duplicating new objects during merge . Fixed a username/password issue in using EntityManagerFactory 's getMetamodel . Fixed a bug in detachment of hollow objects on close ( issue #799 ). Fixed a Doctor exception ( issue #796 ). Fixed a Doctor bug in checking byte[] arrays

reason is unknown. You should check your database with the Doctor to verify that the database file ... . support Support I stopped the DB and ran the Doctor over it and it found no errors, however, when I

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

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 for missing values

by running the Doctor that it is healthy. A thread dump of the server could be useful ... ) and some issues with a particular index, which was also flagged when I ran the database doctor on a backup

the ObjectDB Doctor ? Is this error consistent? i.e. do you get the same exception every time ... "ObjectDB Doctor " first. You may close this issue for now. Thanks Leon   Aquarius Leon Eisenberg