Why is the sysauto table NOT excluded from a clone, when it is in the exclude list?

[chuckb1]

My requirement is that after a clone to a non-prod instance, I do not want the scheduled jobs to run in the non-prod instance because they muck up data.

I've tried to address this by adding the sysauto table to the exclude list. I also set the scheduled jobs in non-prod to inactive.

However, after a recent clone, the jobs ran in the non-prod instance.

Any insights?

[ARG645 · Accepted solution]

chuckb,

Not new to me, I encountered this two years ago. After some research I came to know that to exclude scheduled jobs from clone, you also have to exclude all the child tables of sysauto table.

sysauto is the parent, if the child tables like sysauto_script and sysauto_report are not excluded along with the sysauto, then your jobs will get carried over from source to target instance. 

Thank you,

Aman Gurram

Attached is the picture describing 9 child tables of the sysauto table. 

Please mark the answer correct/helpful if applicable as it may help others in future. 

[chuckb1]

Ah, interesting. Thank you. I'll give this a try next week during our next clone.

[ARG645]

Also make sure to exclude sys_trigger table, this table will contain the jobs that are about to be executed in near future.