Guided Recovery cloning pre-operation checks
Check the following items before you begin the cloning process:
Ensure that the source and the destination systems and the source and the destination databases are compatible. Examples are Solaris 9 to Solaris 10 and Oracle 11 to Oracle 11.
The cloning operation does not support offline tablespaces or raw tablespaces.
The cloning operation does not support Oracle Automatic Storage Management (ASM).
To use a different user or a different group for the clone, change the permissions of the backup image at backup time. Add the 'BKUP_IMAGE_PERM=ANY' to the send commands during the backup of the source database.
See About the environment variables set by NetBackup for Oracle.
If the destination client is different than the source client, perform an alternate restore procedure.
On Windows systems, if the NetBackup Legacy Network Service runs as the Oracle user, that user needs the right to "Replace a process level token".
On Oracle 9 for Windows, run the Oracle service under the Oracle user account. By default, it runs under the local system. On Oracle 10G systems and later, you can run under the local system.
On Windows systems, if you clone to the same system, shut down the source database to successfully complete the operation. Otherwise, an error indicating the database cannot be mounted in exclusive mode appears.
On UNIX and Linux systems, if the cloning user shares an existing Oracle home, the user must have write access to some directories such as
DBS.On UNIX and Linux systems, shut down the source database before you clone in the following situation: You clone to the same system and you either use the same user or use the same home as the source database.