I am using 10g rac . We have scheduled gather stats on node 1 from OEM with instance stickiness is False.
but it is running on node2 sometimes . When it runs on node 2 , node 1 is up and running with lightest load.
I am confused why it is running on node 2?
Please help me out what are the possibilities for this issue.
You could set instance ID to where job have to run using
begin dbms_scheduler.set_attribute(name => '<job_owner>.<job_name>' ,attribute=>'INSTANCE_ID', value=> <instance_id>); end; /
replace symbolic names in <> by your real values.
When no instance_id is set then RAC load balance choose on node to run the job.
Thanks for your reply. Our DB version is 10.2.0.5 . I have seen that Instance_id attribute is 11g .
we set instance stickiness to false so it has to pick up the first available node means it has to go for node 1 to run the job.
But why it is fluctuating nodes?
what is the use of stickiness to false value?
Please guide me. .
Doc for 10g say about instance_stickiness this:
|This attribute should only be used for a database running in RAC mode. By default, it is set to |
For non-RAC environments, this attribute is not useful because there is only one instance.
So check you job repeat_interval.