Configuring scheduled jobs following a clone

[adamski]

We are doing an on-premise clone. The instructions include running a script clone_snc_db.sh that runs a statement:

$MYSQL -e "update $DBNAME.sys_trigger set system_id = NULL where system_id is not null;"

This removes the node from the scheduled jobs which run on a specific node.

After cloning, is it necessary to re-schedule the jobs to run on the nodes in the new environment? In the cloned ServiceNow we don't see the   application server nodes in the System Id LoV of the scheduled job page. How can this be rectified?

[shivanipatel]

Adam,

We are glad you took advantage of the ServiceNow Community to learn more and to get your questions answered. The Customer Experience Team is working hard to ensure that the Community experience is most optimal for our customers.

If you were not able to receive the answer you hoped for but you do believe that you received clarity in terms of how to proceed, we would greatly appreciate if you could mark the appropriate thread as "Correct Answer". This improves the ServiceNow Community experience.

If you are viewing this from the Community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thanks!

Shivani Patel