Skip to main content
NetApp Knowledge Base

SnapManager for Oracle or SAP fail to clone database resources to another host: snapshot on volume not found

Last Updated:

Applies to

  • SnapManager for Oracle (SMO) 3.4.x
  • SnapDrive for Unix (SDU) 5.3.x
  • Database Cloning to alternate host


When SMO or SMSAP are used to clone a database to another host, SDU comes back with the following consecutive errors:

SD-00027: Error connecting filesystem(s) [<MOUNT_POINT>]  from snapshot <SNAP_NAME>:
SD-10016: Error executing snapdrive command "/usr/sbin/snapdrive snap connect -fs <MOUNTPOINT> ...:
0001-089 Command error: snapshot <SNAP_NAME> doesn't exist on a storage system volume <SVM_NAME>:/vol/<VOLUME>

Despite a check on the SVM's volume, showing that exact snapshot exists.


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.