The second step in copying a partition is to apply after-image files to your temporary database.
After restoring your production database backup to a temporary database, if you use after-imaging, you need to apply all the after-image files from the production database that have been created since the backup was created, up to the point just prior to when the accidental deletion occurred. If you don't use after-imaging, proceed to Step 3: Moving data with PROUTIL PARTITIONMANAGE COPY .
To expedite the process of rolling forward multiple after-image extents, RFUTIL ROLL FORWARD accepts a file containing a list of after-image files as input. The syntax of ROLL FORWARD with a list of extents is:
rfutil db-name -C roll forward -ailist listfile
The listfile file, containing a list of AI area files, must be structured as follows:
Specify one AI file per line
AI file names must have a fully specified absolute file name or a relative file name, relative to the working directory where RFUTIL is executed
Lines that begin with a colon (:), hash mark (#), or asterisk (*) are treated as comments and skipped over for parsing
If a file in the list is not an after-image file, ROLL FORWARD issues a warning and the file is skipped.
The following example demonstrates applying the after image files from a database named production_db to a database named temporary_db.
To apply after-image files from a list:
1. Create a list of after-image files from production_db:
Notice that the files are sorted using an alphabetical sort. ROLL FORWARD sorts the files into the proper sequence order before applying them to the target database.
2. Apply the source after-image files to the target, temporary_db, as shown:
proenv>rfutil temporary_db -C roll forward -ailist
production_ai_files.lst
ROLL FORWARD sorts and applies the after-image files, reporting the progress of each file as it is applied to both the screen and the database log file.
Specify one AI file per line