Database Recovery for Universal Broker
Database Recovery for Universal Broker
Universal Broker uses databases to maintain component information, configuration information, and event data. A corrupted database will prevent the Broker from executing.
Database recovery procedures depend partly on the operating system on which the Broker is executing. This page describes the procedures for each operating system.
IBM i | The Universal Broker subsystem, UNVUBR510 (by default), must be down in order to perform database recovery. Use standard IBM i database recovery procedures and attempt to restart the Universal Broker subsystem. |
|---|---|
UNIX | The Broker daemon must be down to perform database recovery. A backup of either the database file being recovered or the entire directory should be created before recovery is attempted. |
Windows | The Broker service must be stopped to perform database recovery. A backup of either the database file being recovered or the entire directory should be created before recovery is attempted. |
z/OS | The Universal Broker started task must be down to perform database recovery. A backup of either the database file being recovered or the entire HFS or zFS data set should be created before recovery is attempted. |