Manually recovering a database after V2P
This page describes how to manually recover a database after the V2P process.
While running V2P from CLI, you can set
recoverDatabase=false
andopenDatabase=false
.While running V2P from UI, you can select not to openDatabase.
If
recoverDatabase=false
is set, run bothrecover-vdb.sh
andopen-vdb.sh
.If the V2P was performed with
recoverDatabase=true
andopenDatabase=false
, only runopen-vdb.sh
.
Procedure
-
In the V2P target environment, navigate to the scripts directory for the exported database instance. You can find the scripts in a sub-directory named for that specific database instance. For Oracle databases, the path is
<target_directory>/script/<instance name>
. For SQL Server databases, the path is<target_directory>\<db_name>\scripts
. -
For Oracle databases, locate the
recover-vdb.sh
andopen-vdb.sh
scripts, then run the required script(s) as described above (assh ./recover-vdb.sh
andsh ./open-vdb.sh
).
For SQL server databases, locate the scriptProvision.ps1
and run it. -
For Oracle databases, add the recovered database to /etc/oratab and Refresh the target environment for it to discover the recovered database. For SQL server databases, when the script completes, Refresh the target environment for it to discover the recovered database.