A database created with PROCOPY, immediately disables After-imaging on the restored database. As such the
expected AI Sequence cannot be updated to match the (last switched)
current AI sequence number of the source database. The differences between the
current and
expected AI sequence numbers is described in Article
The first thing to understand about using a PROCOPY methodology for hotspare baselines, is that the first AI file to be rolled forward against the hotspare created in this way, must be the very first ai file after after-imaging was first enabled. Otherwise, the roll forward operation will fail with:
"Expected ai file number 1 but file specified is (n+1) in sequence. (8019)"
To create a hotspare database for roll forward with PROCOPY
1. Shutdown the source database
$ proshut dbname -by -shutdownTimeout immed
2a. If After-imaging has not been enabled yet, add AI extents to the database if needed, then proceed to Step 4 below.
$ prostrct add dbname addai.st
2b. If After-imaging is currently enabled, copy all non-EMPTY AI extents to be used for roll forward against previous baselines when needed.
The following steps will result in the AI notes contained in non-EMPTY extents being no longer available.
3. Disable After-imaging
$ rfutil dbname -C aimage end
4. Enable After-imaging
$ rfutil dbname -C mark backedup
$ rfutil dbname -C aimage begin
5. PROCOPY the source database to the hotspare destination
$ procopy dbname //hotspare/hot-dbname
- Ensure a full-path .st file is in the directory where the //hotspare/hot-dbname.db file will be created.
- Ensure that nothing else touches the source database while PROCOPY is taking place.
6. Once the PROCOPY has completed creating the hotspare database, the source database can be restarted.
7. The first ai file used to roll forward against the hotspare cannot be an unused EMPTY or a BUSY extent. Once the first source AI extent (Sequence 1) has filled/switched it can then be rolled forward against the hotspare database followed by subsequent AI extents.
$ rfutil hot-dbname -C roll forward -a <path>/aiextents/dbname.a1
Alternative methods of hotspare for 'roll forward' database creation
Other hotspare methodologies are outlined in the Articles below, in summary these are:
- PROBKUP/PROREST, which does not necessarily need the source database to be shutdown as an online probkup and even incremental probkups can be used to create the hotspare baseline. After-Imaging does not need to be re-set each time, the current AI extent at the time of the PROBKUP which is automatically switched, is the first to be rolled forward against the hotspare.
- OS COPY, which can be undertaken either offline or online with an Enterprise Database license after a PROQUIET point has been established. After-Imaging does not have to be re-set each time, but care needs to be taken to manually switch and use the current AI extent for the OS copy as the first to be rolled forward against the hotspare
