I have a set of DB where AI files are continuously updated with AI roll forward, and a wrong command line has been executed (proutil idxactivate) on those DBs. It took 5 minutes to understand why the command line failed (wrong set of DB !), and in the mean time a new set of AI files was roll forwarded. I thought it would fail on all DBs, but in fact it only failed (as expected) on the DB which had active transactions. The low-volume DB where there were no active transactions had the latest AI files successfully applied.
I was under the impression that starting the DB would break AI roll forward, but it seems that it's not always the case. Is it safe to continue the roll forward on the DB where proutil idxactivate didn't break anything ? Or would it be safer to just restore every DB from backup and roll forward every AI file ?
Can dbrestrict be used to keep out other processes such as _progress and prowin.exe?
Thanks your feedback and for the dbrestrict tip, I'll try that. I've usually been using a rename of the .db to protect the DB from unwanted startups, but that wasn't the case for this customer... Dbrestrict could simplify the RF script !
Excellent, thank you !