About corrupted

21-30 of 61Refresh
Forum
2

500Mb ObjectDb database opening issue

500Mb ObjectDb database opening issue
Forum
2

Failed to commit transaction: Attempt to commit a rollback only transaction

became corrupted, leading to the above problem.   note: I have 2 processes hitting the same database ... that the database is not corrupted. The two missing objects are probably the result of deleting objects
Forum
2

Incremental online backup

that the database has been corrupted (by which i mean the data is wrong, not the underlying files) and we need to retrieve a backup. However the last backup is corrupted as well, so we need
Issue
2

javax.jdo.JDONullIdentityException: The identity must not be null.

.close(OMF.java:867)         ... 67 more   After this crash, the database seems to be corrupted, I ... #2 reflects a locked database file (due to a failure during close) and not a corrupted database
Issue
2

NullPointer on query

is corrupted. A post mortem analysis reveals that the last change to the only ObjectDbMessagePayload ... during normal running I'm afraid. Based on your description it's possible that the db file corruption
Forum
2

ODB should auto-restart if it detects it's necessary

. Moreover, this would considerably reduce the chances of corrupting the database. (A problem that I've suddenly encountered in ... . Therefore, I would really appreciate this new feature in ObjectDB, which would definitely avoid corruption
Forum
2

pm.newObjectIdInstance returns null

I am on an emergency upgrade mission. Our production odb file (version 1.0.4) currently corrupts when written to. Importing to 2.6.8. has seemed to fix the corruption problem. So....I am in the middle of testing a 2.6.8 upgrade from 104se_2522. It was plugged in to the existing legacy code (2005
Issue
2

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

is now marked as critical since it can corrupt database files. However, at least in my tests - no data was lost and I could fix the corrupted database files by running the Doctor in repair mode (with 2
Forum
2

Reading 1.x odb files in ObjectDB 2.x without upgrading

was trying to convert one odb file. The new odb file is corrupted. I am attaching both new and old odb file ... [] {oldOdbFileName, newOdbFileName}); I always gets corrupted database.  I am doing coversion of 6 odbfile files
Forum
2

Recommendation - concurrent access multiple class v

that it might get corrupted because the manual says that we must not access ObjectDB with different versions ... system. Question/problem: would that not corrupt the DB? Would ObjectDB support this scenario