Skip to main content
NetApp Knowledge Base

SCSQL cloned database name conflicts with another database on same instance

  1. Last updated
  2. Save as PDF
Views:
232
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for Microsoft SQL Server (SCSQL)

Issue

Cannot clone SQL database using the same clone suffix as a previoulsy deleted clone. 
The following error messages can be seen.
 
  • Resource Group Clone Lifecycle Management window in SC UI:

Cannot clone database. Either the cloned database name <Database_Clone_Name> conflicts with another database on same instance or the same resource is registered by another user during discovery.

 
  • SnapManagerWeb_<Job_Id>.log:
DEBUG SnapManagerWeb_<Job_Id> PID=[1476] TID=[72] Checking for guid <Database_Clone_Name>
WARN  SnapManagerWeb_<Job_Id> PID=[1476] TID=[72] Database <Database_Clone_Name> is existing on <SQL_Server_Name> cannot create another database with same name
ERROR SnapManagerWeb_<Job_Id> PID=[1476] TID=[72] System.Exception: Cannot clone database. Either the cloned database name <Database_Clone_Name> conflicts with another database on same instance or the same resource is registered by an other user during discovery.

 

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.