Internal Website Search

51-68 of 68 results


	Wrong @Id type / To repair IDs that have already changed their types you will have to 'touch' the objects and store
	ODB should auto-restart if it detects it's necessary of it until we repaired and created a new db with ObjectDB Doctor. Therefore, I would really appreciate this new feature
	Consequence of lost ODB$ Files? their healthy with the ObjectDB Doctor , and if necessary, use the Doctor to repair any corrupted database files. support Support
	Exceeding max connections and crashing errors. Try to repair these 2 issues on your side, and if you still see the problem please report
	Corrupted Database or error in ObjectDBExplorer? EmbeddedSystems Please try build 2.6.9_07 that includes an attempt to repair the schema evolution issue
	ObjectDB's Database Doctor Incorrect Error Report Diagnose and Doctor Repair is attached. So are the two databases and screenshots of Explorer
	Out of memory ) Database is repaired with Doctor, now errors have been found. lwalkowski Lukasz Walkowski Please try
	Object Relations Error after Schema Change automatically by running the Doctor in repair mode. If this doesn't help and you can upload the database
	@Unique added afterward is not taken into account data requires rebuilding the database by using the Doctor in repair mode (a better support for adding
	Listing large number of complicated objects with paging. , but I can't repair this right now, so I'm stuck with such a model. I'm trying to fetch 50 records
	Nexus proxy repository with ObjectDB .sonatype.nexus.tasks.RepairIndexTask - Scheduled task (RepairIndexTask) finished :: Repairing repository
	NegativeArraySizeException on commiting a transaction Hi, we started to get a java.lang.NegativeArraySizeException from ObjectDB upon changing an object in the DB and committing the transaction. I tried to repair the DB file with Database Doctor, but the same error is happening also on the fixed DB file. Btw. during fixing the DB file an Internal
	Left join fetch behaviour doesn't retrieve children? repair mode and then the index will be rebuilt cleanly. 3- You can try "SELECT e.indexedAttr, e.id FROM
	Deploying objectdb.jar to karaf 4.0.7 seems to fail well we will check how to repair our build process. support Support Hello, done. My jar (attached) works
	Extending model by "common entity" . If you must repair a database file that was already used with the new schema - open it once in embedded mode
	EOFException The database file that you uploaded is corrupted and you must repair it using the ObjectDB Doctor before
	merger missing in log we have the following entries in our objectdb log (system continues to work normally, database was repaired before switching to version 2.7.5): [2018-05-14 15:00:48 #1 store] Database 'F:\Hummingbird\Objectdb\db\coresystemdb.odb' has been recovered (tr. 68624050-68626451) [2018-05-14
	com.objectdb.o.InternalException: java.lang.ArrayIndexOutOfBoundsException: null ; ... } Fixed problem by database repair with doctor! Thanks! ego123 ego planet Thank