Troubleshooting clone issues

Contributors akseldavis Download PDF of this page

You can find information about that might occur during clone operations and how you can resolve them.

Symptom Explanation Workaround

The clone operation fails when the archive destination is set to USE_DB_RECOVERY_FILE_DEST.

When the archive destination is referring to USE_DB_RECOVERY_FILE_DEST, Flash recovery area (FRA) actively manages the archive log. SnapManager does not use the FRA location during clone or restore operations and thus the operations fail.

Change the archive destination to actual archive log location instead of the FRA location.

The clone operation fails with the following error message: Cannot perform operation: Clone Create. Root cause: ORACLE-00001: Error executing SQL: [ALTER DATABASE OPEN RESETLOGS;]. The command returned: ORA-01195: online backup of file 1 needs more recovery to be consistent.

This issue occurs if Oracle listener fails to connect to the database.

If you are using SnapManager GUI to clone a backup, perform the following actions:

  1. From the Repository tree, click Repository > Host > Profile to display the backups.

  2. Right-click the backup that you want to clone and select Clone.

  3. On the Clone Initialization page, enter the mandatory values and select the clone specification method.

  4. On the Clone Specification page, select Parameters.

  5. Click the +Parameter tab.

  6. In the Parameter Name field, enter the name as local_listener and click OK.

  7. Select the Override Default check box for the local_listener row.

  8. Click any parameter, then double-click the local_listener parameter, and enter the following value:(ADDRESS=(PROTOCOL=TCP)(HOST=<your_host_name>)(PORT=<port#>))

  9. Click Save To File.

  10. Click Next and continue with the clone create wizard.

If you are using CLI to clone a backup, you must include the following information in the <parameters> tag of the clone specification file:


The clone operation fails with an error message saying that the mountpoint you are using is already in use.

SnapManager does not let you mount a clone over an existing mountpoint. So an incomplete clone did not remove the mountpoint.

Specify a different mountpoint to be used by the clone, or unmount the problematic mountpoint.

The clone operation fails with an error message about data files not having a .dbf extension.

Some versions of the Oracle NID utility do not work with data files unless the files use a .dbf extension.

  • Rename the data file to give it a .dbf extension.

  • Repeat the backup operation.

  • Clone the new backup.

The clone operation fails due to unmet requirements.

You are attempting to create a clone; however, some of the prerequisites have not been met.

Proceed as described in Creating a clone to meet the prerequisites.

SnapManager fails to generate a new profile after the clone split operation and the user does not know if the new profile is created.

SnapManager fails to prompt if a new profile is not created after the clone split operation. Because the prompt is not displayed, you might assume that the profile is created.

From the SnapManager command-line interface (CLI), enter the clone split-result command to view the detailed result of the clone split operation.

SnapManager for Oracle fails to clone Oracle 10gR2 ( physical Oracle Data Guard Standby databases.

SnapManager for Oracle does not disable the managed recovery mode while performing an offline backup of the Oracle 10gR2 ( physical standby databases created using Oracle Data Guard services. Due to this issue, the offline backup taken is inconsistent. When SnapManager for Oracle tries to clone the offline backup, it does not even try to perform any recovery on the cloned database. Because the backup is inconsistent, the cloned database requires recovery, and thus Oracle fails to create the clone successfully.

Upgrade the Oracle database to the Oracle 11gR1 ( patch).

Cloning a backup to a remote host fails with the following error message Error: Access is denied.

While mounting, if the IP address of the host is provided to the snap mount command, the cloning operation might fail. This issue occurs if the host on which the database resides is in workgroup while the remote host is in domain, or vice-versa.

You must ensure that both remote host and the host on which the database resides are in the domain and not in the workgroup.