OraFAQ Forum: Enterprise Manager » DBMS

Home » RDBMS Server » Enterprise Manager » DBMS_ SCHEDULER ISSUE (oracle 10g RAC)

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

DBMS_ SCHEDULER ISSUE [message #594935]

Wed, 04 September 2013 03:02

roopeshh
Messages: 3
Registered: September 2013

Junior Member

Hi All,

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.

Thanks,
Roopesh

[EDITED by LF: fixed topic title typo; was SCHEDULAR]

[Updated on: Sun, 08 September 2013 04:46] by Moderator

Report message to a moderator

Re: DBMS_ SCHEDULAR ISSUE [message #594972 is a reply to message #594935]

Wed, 04 September 2013 09:19

LKBrwn_DBA
Messages: 487
Registered: July 2003
Location: WPB, FL

Senior Member

Depends on the assigned service from the "Job class".

[Updated on: Wed, 04 September 2013 10:34] by Moderator

Report message to a moderator

Re: DBMS_ SCHEDULAR ISSUE [message #595014 is a reply to message #594972]

Thu, 05 September 2013 01:22

roopeshh
Messages: 3
Registered: September 2013

Junior Member

Hi,
As you suggested job_class has to set to a particular service to run the job on constant node. I agree with that.

But please clarify my below doubts.
If We have set instance stickiness to false clause . so it has to take the first available node means node 1. If node 1 is not available then it has to go for node 2.

So according to node stickiness option it has to go as above. then why it is taking node 2 when node 1 is available?

Then what is use of Stickiness option ?

Report message to a moderator

Re: DBMS_ SCHEDULAR ISSUE [message #595020 is a reply to message #595014]

Thu, 05 September 2013 02:30

John Watson
Messages: 8964
Registered: January 2010
Location: Global Village

Senior Member

I think this may be misunderstanding the situation,Quote:

the first available node means node 1

why should "the first available node" mean node 1? It could mean the first node that happens to be selected by a round-robin algorithm. I have always assumed that instance_stickiness=false gives an effectively random placement of jobs. I am of course open to correction on this.

Report message to a moderator

Re: DBMS_ SCHEDULAR ISSUE [message #595029 is a reply to message #595020]

Thu, 05 September 2013 03:32

roopeshh
Messages: 3
Registered: September 2013

Junior Member

Please
can you explain this clearly "happens to be selected by a round-robin algorithm".

Thanks in advance.....

Report message to a moderator

Re: DBMS_ SCHEDULAR ISSUE [message #595128 is a reply to message #595029]

Sat, 07 September 2013 07:02

Lalit Kumar B
Messages: 3174
Registered: May 2013
Location: World Wide on the Web

Senior Member

It means, to find the first node, internally Oracle decides to pick an available node on the basis of "Round-robin" algorithm. Usually for scheduling tasks the "Round-robin" principle is used. You can google it for more information.

Report message to a moderator

Previous Topic:	error start database control
Next Topic:	configuring EM failure after applying patches

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Feb 10 01:00:59 CST 2025