Comments on: Issues with CLUSTER_DATABASE parameter

By: Orlando

Orlando — Mon, 14 Jun 2010 11:18:43 +0000

Maybe it was inserted in the spfile a time ago and you didn’t notice.
I had similar issue this weekend,

*.cluster_database =false and also
sid.cluster_database =true

present in the spfile, inserted by another dba.

By: Amit

Amit — Sun, 13 Jun 2010 09:08:21 +0000

Thanks Arul. I am aware of the parameter precedence, but not sure why the parameter had instance specified to it. If we are using spfile and do not specify sid parameter it takes default value of “*” by default.

Regards
Amit

By: Arul

Arul — Tue, 08 Jun 2010 03:47:45 +0000

Its might be too late and you might have figured out teh root cause by now.

In case you haven’t, In a RAC environment SID.parameter=value takes the precedence over *.parameter=value.

So if you use alter sytesm without sid clause it defaults to * and if tehre is an existing entry with explicit “sid.” in spfile, you alter system will not work for this particular instace.

Hope this explains…