- SnapCenter Plug-in for Oracle (SCO)
- Oracle Automatic Storage Management (ASM)
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= TID= 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)
Error SAL PID= TID= 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.