If an upgrade is not possible the following corrective method will be necessary in order to be able to use ai files for roll forward:
Re-enable the after image on the source database in order to reset the sequence number.
A new backup (online or offline) from the source database can then be restored to the hotspare database (target), where roll forward then begins again at sequence 1.
In future, parse or monitor the database log file for messages nearing:
This is after-image file number 65535 since the last AIMAGE BEGIN (3778)
Once the ai sequence has hit the limit, after-imaging will need to be re-set again.
This is after-image file number 65536 since the last AIMAGE BEGIN (3778)
Depending on the environment, depends how 'quickly' these sequences are used up.
For example,
- ai switch every 5 minutes in a 24x7 environment, would mean every 227 days (excluding switches associated with probkup, proquiet)
- ai switch every 10 minutes in a 24x7 environment, would mean every 455 days (excluding switches associated with probkup, proquiet)
- ai switch every 25MB fixed ai extent, would mean every 1600 GB worth of ai notes (excluding switches associated with probkup, proquiet)
Consider decreasing the frequency at which the ai extents are switched on the production environment in order to prolong the need to reset the AI sequence in a given environment.
