Kbase P21224: SonicMQ: How can we decrease the size of the Recovery Logs
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Unverified
GOAL:
How can we decrease the size of the Recovery Logs
FACT(s) (Environment):
SonicMQ 4.x
FIX:
The two recovery log files, recoverylog1.bin
and recoverylog2.bin, help ensure that when a SonicMQ broker is restarted, it is restored to exactly the same state as it was when it was shut down. These files
reside in the directory indicated by the broker.ini property LOG_PATH.
The maximum size to which these files may grow is set with the
broker.ini property MAX_LOG_FILE_SIZE.
While the value of MAX_LOG_FILE can always be increased, if
you wish to reduce this value after the broker has already written
past the new, lower value of this parameter, you must reinitialize
your database and recovery log files with the dbtool script.
Please be aware that reinitializing your database and recovery log files
is causing all information stored in the database like persistent
messages as well as additional
configuration information like queue, durable subscription, security,
DRA settings etc. to be removed
and you need to move that information out of the database (e.g. to files
or other Brokers) to be able to
restore them again later on. An example for getting out same
configuration information you will
find within <SonicMQ installdir>/samples/BrokerManager/ShowSetup.