Internal Website Search

Hi, I am unable to repair a database by Doctor. Getting following error. com.objectdb.o.UserException: Failed to locate field field com.apps.test.ContactTab.col8 using reflection at com.objectdb.o.MSG.a(MSG.java:26) at com.objectdb.o.UMR.s(UMR.java:665) at com.objectdb.o.UMR$b.y(UMR.java:1095

Hello, it is possible to recover an entity that has been removed automatically by CascadeType.Remove. After cascade remove the removed entity will be persisted with the identical primary key. Are all broken references in other entities on this removed/persisted entity repaired again? best regards

, and if the file is not valid (it is corrupted), produces a detailed diagnosis report of all the errors. Repair of a corrupted ObjectDB database file Repairs a corrupted ObjectDB database file by creating a new ... . Running ObjectDB Doctor Repair Running the ObjectDB Doctor in repair mode requires specifying two command

errors on repair

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

to this incident would help. If you need to repair the database (i.e. it is not a test database but contains ... Zwicker OK. If fixing still fails please share the database and we will try to repair it as soon as ... be to repair the database so that system could work again. support Support doctor is running

the Doctor in repair mode and switching to the new created database should solve the issue ... successfully with no evidence for data loss, I assume you use the repaired database now ... to share or if this issue happens again. support Support we are using the repaired database

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 index the database has to be rebuilt by running the Doctor in repair mode. After fixing the index ... process spawn) to to repair .  I got the following log when using doctor 11-Sep 14:55:33 ... unexpectable for our software release. Please find the database file after repair binitbhaskar Binit

. Please give us some advice how to repair the damaged file and how to recognize this kind of mistakes ... repair mode (even if errors are not found) and then, maybe the result database would work ... keep investigating with the broken DB and we'll try the repair mode. I am not sure if we would be able

references with null values) in an existing database file you can run the Doctor in repair mode. This cannot replace fixing the application but it is an easy way to repair a specific database. support Support great thanks, I'll run in diagnostic mode, see what I get, then run in repair mode

] Unexpected total page count: 512 (expected 449). On repair the db some of query are not working ... Manoj Kumar Maharana  On repair the db some of query are not working. Have you run the Doctor in repair mode? Which queries don't work? Please provide more details. support Support I have attached

may be to run the Doctor in repair mode and check whether you still have the errors with the new generated ... you for the update, and regarding the Doctor errors, consider: (a) repairing the database and switching ... to repair the database file using the Doctor and then switch to the new created database file

? Can you reproduce the exception by following specific actions? support Support I repaired the db file with the dbdoctor. But the issue does also occur with the repaired db. The issue is not

details, if any. You may try repairing indexes by running the ObjectDB Doctor in repair mode

and then inserted that value again and saved the database. Repairing the database didn’t help, Attached are a db repair log and a screenshot of queries and results. We will upload the DB through private

I understand, we'd need to stop the DB, run the Doctor in repair mode and start the DB with the repaired file before accessing it with the code containing new indexes. Will this procedure

Hi, I need to change field type in our model from long to String. After changing filed type in our model and repairing database with doctor, most of our entities is gone. Doctor puts some errors ... ) and there was no schema in the left panel. After repairing from this state with doctor, almost 53k records

errors we would like to repair the database and/or inform the customer. So it would be very helpful

these queries? It would probably be better to repair that library to generate valid JPQL queries

the Doctor in repair mode . The new generated database is expected to be compacted. Currently

running the Doctor in repair mode will create a smaller database without the old entities. support Support

the ObjectDB Doctor of version 2.2 in repair mode on existing database files, and to switch to the new

smaller is to run the ObjectDB doctor in repair mode (i.e. building a new database file from an existing database). support Support

Hi, I would like to run the Doctor in repair mode with the source file = target file but I get the following error: java -cp ../../lib/objectdb.jar com.objectdb.Doctor myDB.odb myDB.odb com.objectdb.o.UserException: Attempt to open a non existing file 'myDB.odb' at com.objectdb.o.MSG.d(MSG.java:61

commit the transaction. Alternatively, you run the Doctor in repair mode to create a new database

corrupt I will run it like I'm repairing the DB and generate the new file, then replace the current DB

it doesn't happen on our computers (otherwise we could locate the issue and repair

.6.4_08 Arne Arne Stocker Unfortunately the repair of build 2.6.4_08 was bad. Build 2.6.4_09

enough time to do a repair )   ... together, but we cannot be sure. Will you have a window anytime soon in which you may be able to repair the database with the Doctor? support Support We will be able to repair monday to tuesday night

to repair the database the query runs in the Explorer with no errors. The errors may indicate abnormal ... did already. But after adding new ChangeSet instances it gets corrupted all the time. So I repair , run for like 10min and then I have to repair again. There seems to be a bug which corrupts

we cannot share the database file. Is there any possibility to repair the database? btc_es BTC EmbeddedSystems Have you tried repairing the file with the Doctor? support Support Yes, the db doctor could repair the database. I still have another question to the corrupted database page. When a page

and will be examined further. Repairing the database with the Doctor should hopefully keep only the new version and remove the old version with missing parts. Please run the above query on the repaired database ... program and repairing it. The problem was in cleaning continuing sections of large objects ( 1980 bytes

errors. Run ObjectDB 2.7.2 (or later or earlier) Doctor with repair and create repaired .odb.  repaired .odb will still show indexing errors when ObjectDB 2.7.2 (or later) Doctor is run on the " repaired " database. Automatic index rebuilding (" ") does not correct the database. So, in summary, I

" 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 ... . You have to run the statistics query again on the repaired database. If it is not a production

) and either start with a clean database or fix this database by running the Doctor in repair mode ... of the property at #3. support Support Build 2.1.1_08 produces the exception below. I've tried repairing ... database files by running the Doctor in repair mode (with 2 arguments): java -cp objectdb.jar com

in repair mode (even if no errors are found by the Doctor). You may also disable an optimization ... . Also with the outcome of the Doctor in repair mode. But after many experiments I found out that the Query works ... itself cannot be affected by the bug (so no need to repair it with the Doctor) but various queries

the index by running the Doctor in repair mode: java com.objectdb.Doctor error.odb error2.odb ... model (e.g. adding a new entry in the database) so the database gets corrupted and after that repairing the database with the doctor in repair mode. The main issue we have is that we don't get any

Using version 2.7.4_01, we did a repair . After repair a former link to a missing reference was converted to null. This cannot be deleted using explorer   hgzwicker Hans-Georg Zwicker Thank you for this report. Build 2.7.4_02 fixes the issue. support Support

a repair on that issue. I'm attaching all server logs since the upgrade. FastModel Ben Schreiber All these errors may be related. Please report again after repairing the index and increasing the heap

We have since a while these entries in the log, please inform if this needs a repair (doctor):   ... :555) at java.lang.Thread.run(Unknown Source) hgzwicker Hans-Georg Zwicker It seems that a repair

. Could you please repair the code? You mentioned commit as a workaround. It is unclear if this operation includes ... for posting questionable code snippets. I have repaired it. In this scenario the data is only read

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

it possible that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor)? In ... nothing that can explain the reported issues was found. You may want to try repairing the database with the Doctor

Hello, we ran the db doctor on a database. What does the following errors mean? Do we have to repair the database? BTree Value Errors ------------------ [1] com.btc.ep.architecture.bl.internal.dmos ... 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

an incomplete repair of another issue in build 2.6.4_09. Version 2.6.5 should work well. support Support

Database Doctor has thrown an InternalException right after starting to diagnose or repair my DB file. The version of the Doctor used was 2.6.9_06. The stacktrace below:   Scanning the database file... .Exception in thread "ODB IndexActivation" [ObjectDB 2.6.9_06] Unexpected exception (Error

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

you should be able to repair the entire database by running the Doctor. We will also check why you got the error in

less what we have here) - the database and all the file system is on an ultra fast SD drive - we did do a Doctor repair , not any