Automatically Starting Server Applications in Secondary Systems

When a secondary database server is stopped or it crashes when transactions are in progress and it is subsequently restarted, the server remains in a ‘recovery required’ state until all interrupted transactions have been resolved.

Interrupted transactions are resolved when the commit or abort audit records are eventually replayed. While interrupted transactions exist, read-access to the secondary database is not permitted.

In a secondary JADE system, the automatic initiation of server applications specified in the ServerApplication parameter in the [JadeAppServer] section and the ServerApplication parameter in the [JadeServer] section of the JADE initialization file is delayed until read access to the secondary database has been granted. This occurs when:

The ReadAccessDisabled parameter in the [SyncDbService] section of the JADE initialization file is set to false.
Journal replay has resolved all interrupted transactions.

Server applications specified in the ServerApplication parameter in the [JadeAppServer] section and the ServerApplication parameter in the [JadeServer] section of the JADE initialization file that are terminated in a forced takeover operation are not automatically restarted.

See also "Detecting SDS Role Changes", earlier in this chapter.