PROBKUP - Creation date mismatch on AI files

PROBKUP fails with errors 9214 9212 9216 605

PROBKUP of a hotstandby roll forward database after after-imaging has been enabled fails.

The clues are in the dates:

 

(9212) Extent dbname.a1 has the wrong creation date Mon Apr 2 15:40:33 2012,

(9216) Control Area has a creation date of Fri Oct 8 13:03:50 2010

 

The Control Area (.db) timestamp is the initial hotspare creation/prorest date:

[2010/10/08@13:03:50] (451) prostrct create session begin

 

The .a1 timestamp matches the Last AIMAGE BEGIN Mon Apr 2 15:40:33 2012 when the current hotspare was last used as a source database.
 

Being a CREATION date mismatch, what's happened is that when AI was re-baselined (in April 2012)

The physical AI files from the source were ALSO copied to the hotspare.

0. Finish the roll forward against the current hotspare, including the last BUSY ai extent after the source has been shutdown and truncated, 

viz: that all open transactions are cleaned out and recorded in the ai notes if possible.

 

Then against HOTSPARE: remove the ai files and add them back again

 

If already at the point of having 'rfutil -C mark backedup; rfutil -C aimage begin', then begin with step 1 else skip to step 2:

 

1. Disable after-imaging:

 

2. Remove all the AI extents. The following command needs to be run for each AI extent until there are no ai extents remaining.

 

3.  Verify all ai extents have been removed by examining the resulting output from:

 

4. Add the required AI extents back as defined in the quoted .st file:

 

Example:  addai.st
 

 

5. Enable After-Imaging:

 

6.  Take an online or offline PROBKUP for the new hotspare creation.