Just *.cluster_database=true will do; On Sep 17, 2014 9:35 PM, "Saad Khan" <saad4u@xxxxxxxxx> wrote: > Its the same spfile Riyaj. Its on ASM. > > Thats why this whole behaviour is very strange. > > Again, should it be *.cluster_database parameter in the pfile/spfile or > should it be orcl1.cluster_database and orcl2.cluster_database? > > On Wed, Sep 17, 2014 at 6:27 PM, Riyaj Shamsudeen < > riyaj.shamsudeen@xxxxxxxxx> wrote: > >> *.cluster_database=true is the only version of the parameter you would >> need. >> >> If you have reset the parameter and checked the spfile, then restarting >> the database should not bring in the parameters. May be that, you have >> started the database with a different spfile? Verify that you are using >> just one common spfile between the nodes, hopefully, kept in ASM. If you >> are using two different spfiles between the nodes, then you will have to >> repeat the commands in both instances. >> >> >> Cheers >> >> Riyaj Shamsudeen >> Principal DBA, >> Ora!nternals - http://www.orainternals.com - Specialists in >> Performance, RAC and EBS >> Blog: http://orainternals.wordpress.com/ >> Oracle ACE Director and OakTable member <http://www.oaktable.com/> >> >> Co-author of the books: Expert Oracle Practices >> <http://tinyurl.com/book-expert-oracle-practices/>, Pro Oracle SQL, >> <http://tinyurl.com/ahpvms8> <http://tinyurl.com/ahpvms8>Expert RAC >> Practices 12c. <http://tinyurl.com/expert-rac-12c> Expert PL/SQL >> practices <http://tinyurl.com/book-expert-plsql-practices> >> >> <http://tinyurl.com/book-expert-plsql-practices> >> >> >> On Wed, Sep 17, 2014 at 2:54 PM, Saad Khan <saad4u@xxxxxxxxx> wrote: >> >>> So I reset the system today by issueing following: >>> >>> alter system reset cluster_database scope=spfile sid='orcl051'; >>> alter system reset cluster_database scope=spfile sid='ocrl021'; >>> alter system reset cluster_database scope=spfile sid='orcl21'; >>> alter system reset cluster_database scope=spfile sid='*'; >>> >>> It left the two entries orcl021 and orcl022. But when I restarted the >>> database, it brought back these (prevously reset) entries again. >>> >>> I then had to recreate the spfile after editing pfile and leaving only >>> following: >>> >>> *.cluster_database=true >>> >>> But restarting the database from node 1 via srvctl caused issue with >>> instance 2 (orcl2) >>> >>> Question: Is the right parameter to be left in spfile be >>> *.cluster_database or it should be orcl1.cluster_database and >>> orcl2.cluster_database?? >>> >>> Thanks. >>> >>> On Tue, Sep 16, 2014 at 11:03 AM, Radoulov, Dimitre < >>> cichomitiko@xxxxxxxxx> wrote: >>> >>>> I mean that removing a parameter from the spfile/pfile and setting it >>>> to its default value should have the same effect. >>>> >>>> Dimitre >>>> >>>> >>>> On 16/09/2014 16:59, Saad Khan wrote: >>>> >>>> Please correct me if 'm wrong but the default value is FALSE and that >>>> could cause problem with the startup of instance just like im facing right >>>> now. Those incorrect "name" shouldnt be there at all. >>>> >>>> On Tue, Sep 16, 2014 at 5:06 AM, Radoulov, Dimitre < >>>> cichomitiko@xxxxxxxxx> wrote: >>>> >>>>> >>>>> [...] >>>>>> But will that reset command remove the entries from spfile? >>>>>> >>>>>> i thought reset will move the value of parameter to the default! >>>>>> >>>>>> >>>>> What's the difference? >>>>> >>>>> >>>>> Dimitre >>>>> >>>> >>>> >>>> >>> >> >