ObjectDB Database Search

51-71 of 71 results


	SelfTest and com.objectdb.Doctor errors we would like to repair the database and/or inform the customer. So it would be very helpful
	Problem witch CriteriaBuilder isMember(..) .6.4_08 Arne Arne Stocker Unfortunately the repair of build 2.6.4_08 was bad. Build 2.6.4_09
	Problem with distinct select, order by and equivalent alias/attribute path these queries? It would probably be better to repair that library to generate valid JPQL queries
	@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
	500Mb ObjectDb database opening issue it doesn't happen on our computers (otherwise we could locate the issue and repair
	Vacuum - Reclaiming Unused Space In Odb the Doctor in repair mode . The new generated database is expected to be compacted. Currently
	Shrinking Database Files smaller is to run the ObjectDB doctor in repair mode (i.e. building a new database file from an existing database). support Support
	ObjectDB's Database Doctor Incorrect Error Report Diagnose and Doctor Repair is attached. So are the two databases and screenshots of Explorer
	Corrupted Database or error in ObjectDBExplorer? EmbeddedSystems Please try build 2.6.9_07 that includes an attempt to repair the schema evolution issue
	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
	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
	drop a column from table commit the transaction. Alternatively, you run the Doctor in repair mode to create a new database
	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
	ObjectDB size not reducing corrupt I will run it like I'm repairing the DB and generate the new file, then replace the current DB
	massive performance issues you may try: (1) Repairing the database with the Doctor - that will rebuild all indexes offline. (2
	DISTINCT key causing internal exception on 2.6.4.b10 an incomplete repair of another issue in build 2.6.4_09. Version 2.6.5 should work well. support Support
	InternalException in Database Doctor Database Doctor has thrown an InternalException right after starting to diagnose or repair my DB file. The version of the Doctor used was 2.6.9_06. The stacktrace below: Scanning the database file... .Exception in thread "ODB IndexActivation" [ObjectDB 2.6.9_06] Unexpected exception (Error
	Errors after unexpected server shutdown you should be able to repair the entire database by running the Doctor. We will also check why you got the error in
	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
	each 1-2 days objects on some objectdb level lock/block each other less what we have here) - the database and all the file system is on an ultra fast SD drive - we did do a Doctor repair , not any
	2.9.x query issue with @Unique constraint . Maybe the index is broken. Try to fix the database by running the Doctor and check if the repaired