Reconfiguring the Transaction Database at a Satellite

It is possible to recover a corrupt transaction database at a satellite by reconfiguring it. This is more complicated than reconfiguring it at the Hub, because the TO NEW command cannot be used at a satellite.

The procedure is as follows:

1. In the ADMIN Module at the satellite, reconfigure FROM the corrupt transaction database TO files.

2. Renew the transaction database by one of the methods described in Renewing the Transaction Database.

3. Stop the daemon at the satellite (if this has not already been done).

4. In the ADMIN Module at the satellite, reconfigure FROM the files created above TO the transaction database.

   After reconfiguring, copy the location’s transaction database to all secondary locations (such as the Hub), using the RECOVER command. This will prevent reverse propagation when the database is synchronised at a secondary location.

It is essential when reconfiguring the transaction dB that the SAMEREF option be used. Transaction dBs from other locations have references direct into a local transaction dB, and failure to do so will result in the references changing.