Recovering recent changes after an unplanned outage
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 reenter the transactions.
This might involve rebuilding some of your data. There are a few availability tools that you can use that help you get back to where you were before the outage more quickly.
Journaling
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.
Commitment control
Commitment control helps to provide data integrity on your system. With commitment control, you can define and process a group of changes to resources, such as database files or tables, as a single transaction. It ensures that either the entire group of individual changes occurs or that none of the changes occurs. 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 corrupted data. With commitment control, the incomplete updates are backed out of your database when you restart your system.
You can use commitment control to design an application, so that 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 because of incomplete transactions from a prior failure.
Parent topic:
Shortening unplanned outages