After an unplanned outage, your goal is to get your system up and running again as quickly as possible. You want to get back to where you were before the outage occurred without having to manually re-enter transactions.
This may involve rebuilding some of your data. There are a few availability tools that you can use that will help you more quickly get back to where you were before the outage occurred.
Journal management prevents transactions from being lost if your system ends abnormally. When you journal an object, the system keeps a record of the changes you make to that object. For detailed information on how to plan for and use journaling, see Journal management.
Commitment control helps to provide data integrity on your server. It allows you to define and process a group of changes to resources, such as database files or tables, as a single transaction. Then, it ensures that either the entire group of individual changes occur or that none of the changes occur. For example, you lose power just as a series of updates are being made to your database. Without commitment control, you run the risk of having incomplete or corrupt data. With commitment control, the incomplete updates would be backed out of your database when you restart your server.
You can use commitment control to design an application so the system can restart the application if a job, an activation group within a job, or the system ends abnormally. With commitment control, you can have assurance that when the application starts again, no partial updates are in the database due to incomplete transactions from a prior failure.
For detailed information on how to plan for and use commitment control, see Commitment control.