Scheduled jobs running after cloning

[puchu]

HI Folks,

i am facing one issue where after the instance cloning, the scheduled jobs which are on non production environment and which are inactive, but still they are running.

Due to this, the production may have severe impact.

Please suggest what needs to be checked in such situation.

Thanks in advance.

[puchu]

Still it is not working,

I tried the same thing on persoanl instance, there also the same issue is occuring

[Gowrisankar Sat]

Can you confirm if they are active/inactive, because a few scheduled jobs will be made inactive in non production instances to reduce the data transactions which might have be made active through production clone?

[vinothkumar]

You can exclude certain table while cloning.

Exclude tables while cloning from prod

[puchu]

what does SncTriggerSynchronizer.synchronize(current); works in business rule?

i am searching the script for:

when the schedule job is active, its schedule in sys_trigger table is executed.

And when the scheduled job is made inactive, then from the sys_trigger_list, the schedule is also removed automatically,

Finding out how this is synchronized.

Because this is working when the scheduled job is made inactive manually but when the instance is cloned, this behaviour is not working.

So digging out how manual process is working in this case