Internal Website Search

When enabled, a recovery file is created by ObjectDB when a database is opened and deleted by ObjectDB when the database is closed. The name of the recovery file is based on the name of the database file, with $ added at the end. Every transaction commit is first written to the recovery file

Hello, I have question regarding objectdb recovery when objectdb is not finished correctly (power ... recovered corretly after unexpected finish. When are the transactions physically written to recovery file (disk)? Can setting sync=true (for recovery ) help with this issue, how will be the performance

up, these errors started: ObjectDB 2.3.1_03] javax.persistence.PersistenceException Recovery file ... , which has been fixed in version 2.4.0. Please check if the recovery file ( odb$ ) is empty, and if it is - just ... your server. support Support recovery files aren't completely empty (though are tiny, around 306

over FTP in ASCII mode (BINARY mode should be used). Deleting an ObjectDB database recovery file or ... without its recovery file or recording directory. Power failure when the database is being updated - if the recovery file is disabled. Using the database file simultaneously by two instances

Recovery from failure by using a  recovery file and double writing. Additional recovery layer

Running in embedded mode, configuration specifies " ".  Still, tablename.odb$ files get created, and if still present after an abrupt stop, the application will not restart properly.   What do we need to do to not utilize recovery files (not have orphan tablename.odb$ files)? CAPdev CAP

Hi, I'm trying to come up with the best approach for supporting some kind of hot standby for my master DB. Basically, I have the master DB running with recording and recovery enabled and have a number of applications connecting to it. I realize that I'm able to stand up read only replications

Replicated cluster recovery

Recovery + recording

is useful for two different purposes: It enables recovery from a database failure by replaying

ObjectDB supports master-slave replication (cluster). When replication (or clustering) is used, the same database is managed on multiple machines (nodes), possibly in different geographic locations. This could help in achieving high availability, fault tolerance and prompt disaster recovery . In

(the default is 10 and you are using 400). Different values for  recovery = max (try smaller ... only for the odb file and another dedicated disk only for the recovery file. Using fast SSD disks. Once in a while the recovery file is emptied and that may consume I/O operations. Maybe smaller max recovery

I've had this exception on the recovery of a database: [2011-11-06 04:33:41 #19 store] Exception during recovery of 'F:\calculationservice\objectdb\dbs\admin\WorkflowHistoryArchive.odb': java.lang ... Richard Szurgot This may reflect a normal situation in which the last record in the recovery file

I'm trying to enable replication on master server that was running with " recovery " enabled ... have a recovery file (ended with $) with the master server. This procedure is required ... ) I changed my local ODB conf ( recovery =false, recording=true), restarted and opened it with explorer

ObjectDB 1.x version because the recovery file name has a different format in ObjectDB 2.x. The configuration file in your post is relevant only for ObjectDB 2.x anyway. In ObjectDB 1.x the recovery ... .objectdb. recovery .path");     if (dirPath == null) {      

Hi.  According the docs, "Every transaction commit is first written to the recovery file and then to the database".  During my testing, every time I make a transaction the recovery file ... to the odb file in order to improve the performance. As long as the data is written to the recovery

get corrupted database files in any possible case. I found " recovery " and "recording" in the objectdb.conf ... 2 separate mechanisms for recovery from failure: Recording (transaction log). Recovery (double ... and in other cases recovery is faster. Only one of the two has to be enabled in order to have a safe

. This is the recovery file and you can disable recovery if you want, although not recommended, and then you will not have this file at all. The recovery file is removed when the EntityManagerFactory is closed

or copying a database file when it is in use (the copy may be corrupted), disabling recovery , or discarding the recovery file when exists (e.g. by moving the database file without its associated recovery file). support Support to detail the situation a bit more: - as you can see from

; sjzlondon Steve Zara ObjectDB has two different mechanisms that should enable fully automatic recovery on power failure:  Recovery File and  Recording . If you try a 'kick the plug

It looks like there may be an issue with the DB files created with DB Doctor in recovery mode. This is the scenario that results in the OutOfMemory exception problem (using Object DB 2.5.4_04): 1 ... when searching and updating. 3. We run DB Doctor in recovery mode to generate a recovered DB file. No schema

. This feature, which is called auto recovery , is not supported by the free edition of ObjectDB. To ensure ... file and the recovery temporary file. Consult your operating system documentation for instructions

J visual vm is complaining of deadlock since upgrading to the 2.4.4_16 from _06 and using setting -Dobjectdb.temp.no-resize-clear=true The only other change is that we no longer create recovery or replay files as we were not using these. i have attached our full server strack trace

of the $ file check the recovery max setting. support Support thanks, that helps hgzpincher Hans-Georg Zwicker

of ObjectDB. Note that some operations are more difficult in Java than in other platforms, and recovery from

Hello!  I have a few questions! I have followed the instructions on replication and I can see that is helps with: Prompt disaster recovery - because if master goes down I can switch the slave into master, or copy the slave data to another master and resume. But how does it help with: high

. This could be caused, for example, if the database is stopped (abnormally) during a writing action, and recovery

recovery file. However, it is also possible (although extremely rare) that the specific activity in

after index deletion. Changed default configuration (enabled recovery , disabled recording). Fixed

. support Support Contents of the objectdb.conf file (also attached). I think I have disabled recovery

Hello, why delete from ... doesnt modify size of odb? Even in in embedded mode, and in server mode i use recovery , not recording mode. mastervoland Vladimir Sadovnikov When objects are deleted from the database their space is marked as unused and becomes available for future objects. The size

When the Doctor completes please post its output. Exploring the cause of the recovery failure ... . Actually this is the first report of such a failure after recovery . Probably you do not have a copy of the database and the recovery file (odb$) after shutdown and before the server

database termination followed by opening the database with no recovery (e.g. if the database file was moved or copied to another location without the recovery file). support Support Hello, thats what I ... . However, if recovery is enabled then the database should be repaired automatically when it is opened

file over FTP in ASCII mode (BINARY mode should be used). Deleting an ObjectDB database recovery file ... without its recovery file or recording directory. Power failure when the database is being updated - if recovery file is disabled. Using the database file simultaneously by two instances of the ObjectDB

before this happened? Did you have a database recovery before this happened ... been moved or copied 4) No recovery - the database is new & empty upon startup 5) No but I'll switch

log so that the repaired database has not any data lost? btc_es BTC EmbeddedSystems If recovery ... . But the recovery file (ended with $) must be available when the database is opened after a failure. support Support

 LockModeType.NONE. Fixed a bug in recovery from an exception during inverse (mapped-by) retrieval. Improved recovery from partial deletion of class hierarchy in the Explorer.

, but then there should be a recovery file that should be used to fix the database automatically. Did you get this error after a process kill? Do you have a recovery file that you can upload? Unfortunately, assuming you were using build

queries. Fixed recovery from failure when the recovery file is empty ( issue #695 ). Removed

Improved recovery from failure when recovery is enabled with no sync  ( issue #2293 ). Added support of using JDO listeners with JPA EntityManager. Added debug logging got persist cascading ( issue #2299 ). Fixed a bug in restricting server access to a range of IPs ( issue #2292 ). Fixed

.g. temporary files, recovery file) to other disks. using replication with multiple servers

that has to be addressed. If you uploaded the odb file but there was also a recovery odb$ flle

Apparently there was a problem when a recovery file exists but it is empty. Build 2.3.7_09 should fix

cleanup and reusing space after index deletion. Changed default configuration (enabled recovery

_and_potential_data_loss itsme Martin Petzold Please check the recovery setting in your ObjectDB

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

) is:          It should force physically writing to the recovery file

a bug in the new log based (recording) recovery from failure mechanism. Fixed a bug in finding

? lorenz2304 Benjamin Lorenz The $ file is the recovery file . support Support

An ObjectDB database file can be backed up simply by copying the file (with the associated recovery file if exists). This should only be done when the database is closed. Online backup will enable backup also when the database is open and in use. support Support Online backup  is now implemented in ObjectDB 2.1. support Support