220 likes | 317 Views
Recovery Expert V2 Sample User scenario. Scenario 1: Simple recovery to a point-in-time (PIT) Recovery Expert Point-in-time (PIT) recovery scenario. It's Monday morning. A DBA gets a call from an application programmer:
E N D
Scenario 1: Simple recovery to a point-in-time (PIT) Recovery Expert Point-in-time (PIT) recovery scenario It's Monday morning. A DBA gets a call from an application programmer: "I accidently updated the Department table and need to recover it to a point in time before the Oregon updates. Can you help me out?"
The DBA must perform a simple recovery to a specified point-in-time (PIT) • t0 (time zero): The table before any updates. Note that: • All seven locations are 'CA‘ (the DBA wants to restore to the OR updates) • Point-in-time to restore to is 2004/09/15 09:52:34 • A full offline database backup is required
After the first recovery (the table status is time = 0, or t0) • The first set of updates are completed (t0). • Next step (time=1, or t1): Update the 4 department location columns with 'HI‘, restoring to a PIT of 2004/09/15 09:57:39
Performing another simple recovery to a specified point-in-time (PIT) • t2: The second set of required updates is to correct the table entries previously made in error • The task is to update 3 more department location columns that currently contain CA with OR, restoring to a PIT of 2004/09/15 10:00:22
The backup: Recover a table to a selected point in time t1 t2 t3 t0 Resulting table (after recovery) SQL Initial table transactions (CA entries) set 2 - OR SQL transactions set 1 - HI t3: The restored table. The goal is to restore to a point just before t2, where the mistakes occurred.
Recovery Expert Log Analysis Transaction record: Running the Log Analysis Transaction report after the recovery has completed will show you information such as the Unit of Recovery ID (URID) number, the date and time of the recovery, and the table name that was recovered.
Log Analysis Transaction detail, continued View the details of a specific Log Analysis backup transaction by highlighting and double-clicking that backup. A second window opens showing details, such as the action that was taken and the status of that row. A second tab will show the Undo SQL.
RE displays possible recovery paths
Click the ellipse (...) button to see the details of the recovery
Compare the details with the other recovery path option details
Output example: The 'OR' Locations are no longer there
Scenario solution • The logs were “mined” to identify transactions • SQL that was required to back out the logs was automatically generated, then executed. • The changes were only applied to affected tables, not all of the tables in the table space.