Idea ID 2797912
The Internal Database restore should be one single job to run.
Benefits / Value
It is actually documented that after the online restore, there is another task to be executed: running the omnidbrestore.pl script. If the administrator is not aware of that, he will be left with a cell which is not accessible. An IDB restore is not a trivial task but ideally the product is helping to make it a simple task. The cell should be up and running and accessible after the online restore has finished. Clear and straight-forward: a valid IDB backup is available, so it can be restored with one simple restore session. That is what makes the product attractive.
The omnidbrestore.pl script is already doing a good job. But the administrator does not always realize it is still needed after the restore session. Hence it would be better to have all the tasks which are executed in the script, included in the restore session. The exact implementation method is not really important. If it is technically difficult to include these tasks in the same session then I'm sure a kind of post-exec session could be started automatically after the restore session. After all, the cell is not accessible before these tasks are executed, so there's no reason for 'not' executing them right away.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.