Yes, if you have a recovery CATALOG or a control file, (snapshot, backup, or
online control file) then you attempt a restore to a new host.
see "How to Move/Restore DB to New Host and File System using RMAN (Doc ID
You’ll need the appropriate commvault params set within RMAN or commvault of
On 11 Jan 2022, at 6:36 am, Sandra Becker <sbecker6925@xxxxxxxxx> wrote:
Oracle Database & Grid: 188.8.131.52
We had some issues with a database server and the 9 databases stopped
working. The sys admins suggested a reboot, which we did. GRID/ASM would
not come back online after the reboot. It says it can't find the ASM disks,
but everything the sys admins look at say they are there and online.
We tried restoring the $GRID_HOME, but that didn't change anything. Our
Rimini support said a lot of libraries were missing from the $GRID_HOME, so
another DBA tried to getting the missing files. Still no luck. It's a
two-node RAC, but only one of the nodes was functional at the time we
rebooted the first node. The second has the same issues as the first, so we
can't bring anything online there either.
We tried setting up on another comparable cluster, but due to the way the
database configurations were done in CommVault for the "bad" server,
CommVault thinks they are single instance and won't let us restore to a RAC.
Ultimately, we want to move these databases to a non-ASM server in AWS. Any
suggestions as to what we can do? I was wondering if we could reinstall
GRID/ASM on the "bad" server and then use Commvault to do our restores. Is
that totally off base or a viable option?