ObjectDB ObjectDB

Internal Website Search

21-30 of 74 resultsRefresh
14

errors on repair

Unfortunately these are critical errors that indicate a corrupted database file. Please provide more information. Can you reproduce the problem? The common causes of corrupting database are moving or copying a database file when it is in use (the copy may be corrupted), disabling recovery, or discarding
14

InternalException when reading a HashMap

, but also on the first access of some objects from the corrupted file: java.lang.InstantiationError: eu.extech.quant ... indicates an error while reading the hash map, if some objects in the database are corrupted ... are also corrupt. thamal Tomas Hamal > Is this wanted behaviour? Indeed it seems restrictive. We plan
14

Online backup with JDO

. I've read at the Database Doctor that copying the db file while it is online may cause corrupted DB file. Does this mean that the copy can be corrupted or even the source file ? My second question ... can be corrupted or even the source file ? Probably just the new copy. > But how do I start it if I am using
14

Failover from Master to Slave

corrupt the databases? Let's take the following scenario: DB A is master, DB B is A's slave 3 application ... will always connect just to the one that represents the Master, avoiding data corruption. Does it make sense ... to A. Well there you go .. you have a high probability of database corruption. I would suggest going
12

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

, so creating a new database removes this problem. ie: somehow the database became corrupted, leading ... indicates that the database is not corrupted. The two missing objects are probably the result of deleting
12

Incremental online backup

up incrementally twice a day, and one day we realize that the database has been corrupted (by which i mean the data ... is corrupted as well, so we need to go back to the previous one. The way this would work
12

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
2

java.lang.ClassCastException: com.objectdb.o.SCU cannot be cast to com.objectdb.o.PRU

There is a corruption into index when I tried to obtain an object that non exist into database. This was soluted ... of the index corruption we will be happy to explore this issue further, especially if it happens again. Of course, if you find a way to reproduce index corruption it may be of a great help. support Support
2

Exception makes the system unusable for several minutes

traces and your answers, that these exceptions are thrown due to 4 corrupted objects ... ?), which may cause a general slowness. support Support the problem is that these objects are not corrupt ... , and indeed, if the access issue is temporary then it seems that the objects are not corrupted
2

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

includes the fix. This bug 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

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support