Loop detected in next() for table jm_sched_keys in destination after peer deletion
Applies to
- ONTAP 9.10.1 and above
- SVM DR
- Cluster peer relationship(s) have been deleted
Issue
- After deleting cluster peer relationship(s,)
job schedule croncommands fail
Examples:
- While trying to list the cron schedules a error is displayed:
Cluster01::> job schedule cron show
Cluster Vserver Name Description
--------------------------------- --------- ----- -----------------
xxxxx-1b64-11e7-bfb4-00a098afae5f vserver01 daily Mon-Sat@23:55
Error: show failed: Loop detected in next() for table jm_sched_keys. Next on
"b9a68f9a-1b64-11e7-bfb4-00a098afae5f vserver01 daily" returned " vserver01 hourly".
Alternate error:
Error: show failed on cluster "cluster1" vserver "cluster1" name "weekly_snap1": Loop detected in
next() for table jm_sched_keys. Next on "cluster1 cluster1 weekly_snap1" returned "
daily_snap2".
- Trying to delete the job schedule fails with the following errors:
Cluster01::> job schedule cron delete -cluster xxxxx-1b64-11e7-bfb4-00a098afae5f -vserver vserver01 -name daily
Error: "xxxxx-1b64-11e7-bfb4-00a098afae5f" is an invalid value for field "-cluster <cluster_name>"
Valid choices in this command's context: Cluster01
Cluster01::> job schedule cron delete -cluster Cluster01 -vserver vserver01 -name daily
Error: There are no entries matching your query.
- Rather than displaying the cluster name in columns or fields where the cluster name normally appears, the cluster serial number is displayed, instead.
-OR-
- Both the local cluster name as well as the recently deleted peer cluster name appear in columns or fields that normally contain the cluster name, and the peer cluster name is associated with duplicate schedule names.
