ObjectDB Database Search

. - the first app cannot add points anymore; it now reports zero entries - db is corrupted If it is an error

after the query is in trvr- corrupt .zip. As you can see the update completes Ok. We see the problem

out' while ObjectDB is running, the database is not expected to be corrupted . When the database is opened

file should not be corrupted . You can check your database file after such events by running

datastore file backup which guarantees the file will not be corrupted ? CBE CBE You should close

Clean and Build has not been corrupted . - No javaagent enhancement is used at any stage

to read could be read before without any issues so it seems that the database file gets corrupted

itself was not corrupted though, because when I tried to make a copy of it (I made it transient

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

for me. the png file is corrupted after upload (and download).       

of this specific database file. You can find a list of possible reasons for database corruption on the link

". So it does seem as a specific system issue rather than a bug in ObjectDB or a corrupted database file

  Here is a link for the corrupt database: https://www.dropbox.com/scl/fi/6ywgr9yx459c9tskv525t

again at our major Aerospace customer we are facing the situation that the database became useless 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

This was a critical bug that could corrupt databases when the total number of entity classes, indexes

. The new version fixes a critical bug that in some cases (rare but possible) may cause database corruption . support Support

. It seems that all entity managers become corrupted / broken. (see stack trace below) Should it be something in

Hello, corresponding to your suggestion I created a private ticket in reply to http://www.objectdb.com/database/forum/1109. Attached you will find my database file (I removed most of the content but one corrupt instance is still included). I error happens when reading the field "Event

that in some cases (rare but possible) may cause database corruption , so it is highly recommended to use the new build. support Support

bug that in some cases (rare but possible) may cause database corruption , so it is highly recommended to use the new build. support Support

Fixed a critical bug that may cause database corruption ( issue #1977 ). Improved error messages on entity operation exceptions. Fixed a NullPointerException  on cascading persist throw an unloaded collection ( issue #2049 ). Fixed the location of a temporary file for index update ( issue

it possible that the database is somehow corrupt (we did the last repair last ween with 2.7.4_02 Doctor)? In

) became non synchronized with the data or corrupted . This shouldn't happen of course as recovery

that the database will not become corrupted ). Which of this options seems to fit better to your needs? support