About repair

21-30 of 63Refresh
Forum
2

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

Please provide relevant details, if any. You may try repairing indexes by running the ObjectDB Doctor in repair mode. If you can upload the database (possibly in a private support ticket
Issue
2

Indexes broken after schema update

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? The database record history may help. You are right
Forum
2

possible index required for improving query performance

about adding new indexes. 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 accessing it with the code containing new indexes
Forum
2

Schema migration - long to String

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 ... get screenshot) and there was no schema in the left panel. After repairing from this state with doctor
Issue
2

Server crash - Mismatch client-server protocol prefix

will be taking the production site offline tonight so I can run a repair on that issue. I'm attaching all server logs since the upgrade. All these errors may be related. Please report again after repairing
Forum
2

wrong query result

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
Issue
2

Deleting a broken reference that was fixed to null in the Explorer

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   Thank you for this report. Build 2.7.4_02 fixes the issue. hgzwicker
Issue
2

log entry and massive performance issues

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

Best practise loading big data

is not defined. Could you please repair the code? You mentioned commit as a workaround. It is unclear ... String stringValue; } Hello, sorry for posting questionable code snippets. I have repaired it. In
Forum
1

@Unique added afterward is not taken into account

rebuilding the database by using the Doctor in repair mode (a better support for adding a new index is expected to be released soon). OK perfect, thank you.. lo