Skip to main content
NetApp Knowledgebase

SCO doesn't clean up database clones created for cataloging, when the storage cloning fails

Views:
24
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

  • SnapCenter Plug-in for Oracle (SCO)
  • Oracle Automatic Storage Management (ASM)

Issue

When setting up database and archive log clones for cataloging, ONTAP cloning of a database or archive log file system fails with an HTTP(S) timeout:

Critical SAL PID=[12468] TID=[8524] The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop:
        Connection to <SVM_FQDN> on port 443 for protocol HTTPS timed out.
       at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
       at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

Error SAL PID=[12468] TID=[8524] Failed to create volume clone

This leaves the cloned volume (and contained LUNs) behind unmapped, since they are not cleaned up in the failed cataloging process.

Additionally, any extra LUN based database or archive log clone that was successful before the failure, as part of the same operation, would remain mapped with devices labeled with the existing already ASM disk group on the backup host, which can cause further disk/ASM conflicts on the next backups.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support