Restart / Warm starts the serverdb; i.e., switches the serverdb into WARM mode.
In the event of a system crash, Restart / Warm ensures that all committed transactions are redone and that all uncommitted transactions are rolled back.
The function can be executed in COLD or OFFLINE operating mode. In OFFLINE operating mode, CONTROL first switches the serverdb into COLD mode.
If the serverdb belongs to a distributed database, Restart / Warm is performed in two phases. In the first phase, all committed transactions are redone and all uncommitted transactions are rolled back, and EXCLUSIVE locks are set for all "pending" transactions. "local restart: ready" displayed in OPMSG2/3 (DIAGFILE) indicates successful termination of the first phase.
In the second RESTART phase, a connection is established to the network specified by the serverdb entries contained in the system catalog. Depending on whether the starting serverdb or the network represents the majority of replicated objects, the corresponding log entries are copied from or to the other serverdbs and are redone. Moreover, pending transactions are resolved.
Although no connection to other serverdbs can be established, for example, because these have been disconnected from the network by DISCONNECT or SHUTDOWN, the distributed RESTART terminates successfully and the started serverdb is ready to receive.
"distributed restart: ready" displayed in OPMSG2/3 (DIAGFILE) indicates successful termination of the second phase.