Guided Recovery post-clone operations
Perform the following after the cloning operation has completed:
On Windows systems, if the cloning operation fails, use the dbca utility to delete the database. dbca sometimes removes directories, so verify before retrying the operation.
On UNIX systems, update the
oratabfile with the appropriate instance information.On UNIX systems, if the cloning operation fails, do the following cleanup:
If the database is active, shut down the database.
Remove init<SID>.ora, spfile<SID>.ora, and any other files that are associated with the SID being used, from the <$ORACLE_HOME>/DBS directory.
Remove all data files.
If a cloned Oracle database contains read-only tablespaces or data files, you must make them read-write before RMAN backs them up, or RMAN cannot restore them. After the backup (cloning operation), you can return the items to read-only.
The following shows an example of the sequence of steps in the process:
Back up Oracle database A which contains read-only tablespace TABLE1.
Clone database A to database B.
Use the Oracle alter tablespace command to make tablespace TABLE1 read-write. You may revert to read-only if you want.
Back up database B.
Use RMAN to restore database B.