SnapCenter Oracle ASM PITR Clone Fails with duplicate key
Applies to
- NetApp SnapCenter Server (SCS) 6.2.2
- SnapCenter Plug-in for Oracle (SCO)
- Oracle databases on ASM storage
- Environments using Point-in-Time Recovery (PITR) cloning
Issue
PITR Clone Fails with Duplicate Key Error
- SnapCenter Oracle ASM PITR clone jobs intermittently fail with the error:
An item with the same key has already been added. Key: ndbaora70-cluster_UATCDB_Oracle_Database_log_Full_Scheduled_<timestamp>_1 - Job logs show:
- EligibleLogBackupIDs contains duplicate values
- isMissingSCNs=True
- Number of ALM log backups to be cloned is greater than expected
- The deduplication step (GetOptimalLogBackupsForRecovery) does not run, leading to duplicate backup IDs being processed
- Example from SnapManagerWeb log:
Activity 'Cloning log backup ...' failed with error: An item with the same key has already been added. Key: ...
- SnapCenter Oracle ASM PITR clone jobs intermittently fail with the error:
Clone Deletion after REST Timeout
- Long-running clone or restore jobs are deleted by SnapCenter after a fixed REST timeout (default 3 hours, configurable).
- The ApplicationClone REST call remains open even after all sub-steps complete successfully; after the timeout window (e.g., 9 hours), SnapCenter assumes failure and tears down the clone.
- This results in abrupt deletion of a successfully created clone, sometimes without a graceful Oracle shutdown.
