SnapCenter SnapVault update job fails but replication succeeds to secondary storage
Applies to
SnapCenter Plugin for Oracle (SCO)
Issue
SnapVault replication fails with the following errors, even though snapshots are successfully replicating to storage:
Backup_123456_db_roadrunner_acme.com/spl_123456.2022-05-22.0_20220522_0925.log:2022-05-22T21:25:17.0000839-07:00 ERROR Execution Monitor Thread [su - oracle -c env] c.n.c.e.ShellResult - EXE-00003: Killing spawned process for command: su - oracle -c env
Backup_123456_db_roadrunner_acme.com/SMCore_123456_20220522_0925.log:2022-05-22T21:32:48.0693687-07:00 ERROR SMCore_323928 PID=[3384] TID=[76] ErrorCode (-1), ErrorMessage (You have selected a backup policy indicating that you want to backup to a secondary storage system. Some of the resources you want to backup are located on a storage system that does not have replication relationships set up. Establish your SnapVault or SnapMirror relationships before proceeding.)
Backup_123456_db_roadrunner_acme.com/SMCore_123456_20220522_0925.log:2022-05-22T21:32:53.8692848-07:00 ERROR SMCore_323928 PID=[3384] TID=[76] ErrorCode (109), ErrorMessage (The following activities failed:Replicating to Secondary,Backup datafiles and control files,Replicating to Secondary. Please check the activities for detailed error message.)