Authorization to Alter DB2 UDB Crash Recovery

The IBM DB2 Universal Database (UDB) has, in all versions, a process called ‘Crash Recovery’. This process is the mechanism
by which DB2 UDB is able to restore the database and all of its data to a point of physical and logical consistency.

This process is initiated upon the activation or restart of, or first connection to the database if a flag is not set showing that the
database is currently in a consistent state. In this process, DB2 UDB attempts to roll forward all transactions that were open, or
have been opened, since a known point in the transaction logs. All transactions that were committed before the database came
offline are committed. Any transactions that were not committed at the time the database came offline are rolled back. Thus,
physical and logical consistency of the database and its data are maintained.

Situations occur that prevent ‘Crash Recovery’ from successfully completing. Examples of these situations include software
defects, data corruption, and hardware problems. If this process fails, the DB2 UDB database will not come online in order to
ensure the integrity of the database. Generally in this situation, the only course of action is to restore from a backup of the
database.

Realizing that a restore is sometimes not possible, IBM DB2 UDB Support has developed tools which can modify or bypass
Crash Recovery. With these tools, IBM DB2 UDB Support can often bring the system on-line and make it accessible in a short
period of time, but this will come at a cost. By altering or bypassing the ‘Crash Recovery’ process, there will most likely be
some sort of corruption in the database server. Some examples of the corruption include, but are not limited to:

• Index corruption
• Data corruption
• Loss of data consistency

Recovery from this corruption can require extensive time and application knowledge. The damage may be such that the only
alternative is to do a full restore. If you require additional technical explanation, the engineer with whom you are working will
assist you.

Your Company has requested that IBM alter the Crash Recovery mechanism of your licensed DB2 UDB product. IBM is willing
to do so, as an accommodation and at no charge to you, with the understanding and on the terms specified in this Authorization
letter. IBM PROVIDES THIS SERVICE ON AN “AS IS” BASIS, WITHOUT WARRANTY, EXPRESS OR IMPLIED OF
ANY KIND, AND IBM HEREBY DISCLAIMS ALL WARRANTIES, INCLUDING ANY IMPLIED WARRANTIES OF
ANY KIND. IBM WILL NOT BE LIABLE FOR ANY LOSSES OR DAMAGES TO YOUR SYSTEMS, INCLUDING ANY
DIRECT, INDIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL OR ECONOMIC DAMAGES (INCLUDING, BUT
NOT LIMITED TO, LOST PROFITS, BUSINESS, REVENUE, GOODWILL, OR ANTICIPATED SAVINGS) OR LOSS OF,
OR DAMAGE TO, RECORDS OR DATA.

-------------------------------------------- cut and paste this section below into your reply email -------------------------------------------

Please cut and paste this section into a reply email and fill in the blanks below. By completing and emailing back this section,
your Company understands, agrees, and authorizes IBM’s DB2 UDB Support to alter the ‘Crash Recovery’ process of DB2 UDB.
It is understood that the ramifications include the possibility of various types of corruption, some of which may be readily
apparent, some of which may not be readily apparent. If there are any questions, please contact IBM DB2 UDB Support.

I warrant that I am a duly authorized representative of my Company with authority to make this request and authorize this service.

_____________________________ ______________________________
Print Name of person authorizing Name of machine (if applicable)

_____________________________ ______________________________
Email address of person authorizing Name of instance (if applicable)

_____________________________ _____________________________
Name of Company PMR or Case Number