Kbase P9871: Does prostrct add interfer with .ai processing?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/01/2005 |
|
Status: Unverified
GOAL:
Does running prostrct add against the production and backup database interfer with .ai processing?
FIX:
1.) When adding a new ai extent, if the extents BETWEEN the (current) BUSY ai extent and the (newly added) Empty extent has (UN-available) FULL extents in-between before restarting the database and re-suming operations, we fail to roll-over by 'jumping' the FULL extent into the newly-added EMPTY extent.
We don't, because the ai extent switches have to be linear (?) from (say) the busy extent:
> > 3 -> 4 -> 5 -> 1 -> 2
2.) If while adding extents, you accidentally rollforward a BUSY extent on the target database, this proceeds w/o failure, but prevents further roll forward on the target database.