 305 | . Recording is enabled by default and can be disabled in the configuration. The ObjectDB Replayer tool ... might be slow if the database is large. Running the ObjectDB Replayer The ObjectDB Replayer tool is bundled in ... .Replayer my.odb
If objectdb.jar is not in the current directory a path to it has to be specified |
40 | Describes the ObjectDB object database tools - the Explorer, the Server, the Enhancer, the Doctor and the Replayer. |
31 | ="all" />
Database engine operations can be recorded in files and later replayed using the ObjectDB Replayer ... a database that has not been closed properly by running the Replayer tool. Recording might also be useful |
29 | I'm getting replication errors and upon trying to play the replayer I get a NullPointerException ... .jar com.objectdb.Replayer db.odb
ObjectDB Replayer [version 2.4.2]
Copyright (c) 2012, ObjectDB ... )
at com.objectdb.o.RPM.t(RPM.java:223)
at com.objectdb.Replayer.main(Replayer.java:62) Any idea |
22 | . Automatically repairs damaged database files with minimum data loss (if any). Transaction Replayer |
22 | . Automatically repairs damaged database files with minimum data loss (if any). Transaction Replayer |
22 | damaged database files with minimum data loss (if any). Transaction Replayer Transactions |
5 | one. Yes, this is the expected behaviour. You may also find the Transaction Replayer useful in this scenario. Isn't the Transaction Replayer more like the opposite of this? The Transaction Replayer ... among a few restoration points from a backup. The Replayer can also be run up to a specified transaction, e.g |
3 | transactions). You can also restore the database explicitly by using the Replayer. Also notice ... exists with _nonclosed suffix. If not found - rebuild the database by using the Replayer. Ron Coleman |
2 | Version 2.0.1 Fixed a bug in lazy loading of instances of non enhanced classes. Fixed a bug in using the Replayer with no updates to the database. Fixed an activation bug. |