Support for high availability

Because Db2 provides support for high availability, frequently starting or stopping Db2 is not necessary.

You can run Db2 for several weeks without stopping and starting the subsystem. Some customers have managed to keep Db2 running continuously for several years. One key to achieving high availability is to use data sharing. Data sharing allows access to data even when one Db2 subsystem in a group is stopped. Another key to high availability is the ability to get the Db2 subsystem back up and running quickly after an unplanned outage.

• Some restart processing can occur concurrently with new work. Also, you can choose to postpone some processing.
• During a restart, Db2 applies data changes from the log. This technique ensures that data changes are not lost, even if some data was not written at the time of the failure. Some of the process of applying log changes can run in parallel
• You can register Db2 to the Automatic Restart Manager of z/OS®. This facility automatically restarts Db2 if it goes down as a result of a failure.