12 | Unexpected exeption 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 always reproducible. Sometimes the use |
12 | 500Mb ObjectDb database opening issue, and then, if it is an issue with ObjectDB we will probably can repair it. Try to isolate the issue from ... the issue and repair it already). Therefore, we have no way to proceed without your help. You tested |
12 | com.objectdb.o.NLV cannot be cast to com.objectdb.o.CMV details, if any. You may try repairing indexes by running the ObjectDB Doctor in repair mode |
12 | 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 |
12 | possible index required for improving query performance the DB, run the Doctor in repair mode and start the DB with the repaired file before accessing |
2 | Server crash - Mismatch client-server protocol prefix of the production database. I will be taking the production site offline tonight so I can run a repair ... may be related. Please report again after repairing the index and increasing the heap size (-Xmx1024m |
2 | Errors in log to repprtWe have since a while these entries in the log, please inform if this needs a repair (doctor): ------------------------------------------------------------------------------------------------------------------------ [2019 ... .lang.Thread.run(Unknown Source) hgzwicker Hans-Georg Zwicker It seems that a repair is needed |
2 | Best practise loading big data your code but StepBlock is not defined. Could you please repair the code? You mentioned commit as ... for posting questionable code snippets. I have repaired it. In this scenario the data is only read |
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? bensteele Ben Steele The database record history |
2 | log entry and massive performance issues that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor)? In addition ... was found. You may want to try repairing the database with the Doctor to see if it solves the new |
