Re: ORA-32000

From: Ricard Martínez <ricard.martinez_at_gmail.com>
Date: Wed, 28 Mar 2012 12:34:19 +0100
Message-ID: <CAFGV9uncLtScPbdAAcAJsdoRsDiEDOEL-OL4QwUrJfwcHyw-+Q_at_mail.gmail.com>

Thanks for the help guys but problem is solved. Problem is node1 had the spfile in $ORACLE_HOME/dbs meanwhile another had the spfile in ASM diskgroup (seems someone made a mistake recreating the spfile in correct location).
When trying to alter system any parameter from node1 it shows the ORA-32000. After deleting the spfile in $ORACLE_HOME/dbs and checked it is using ASM one again, all starts working properly. (That means bounce database ofc) Maybe will help someone in the future.
Regards
On Wed, Mar 28, 2012 at 12:23 PM, Rodrigo Mufalani <rodrigo_at_mufalani.com.br>wrote:

> Then the issue can be the miss sid clause, try with that. Please correct
> the no specification of spfile to share it between nodes (simplify
> management).
>
>
> []'s
>
> Rodrigo Mufalani
> Oracle Ace member
> OCP/OCE Rac
> Www.mufalani.com.br
>
> Sent via my DROID :-)
>
>
>
> Stefano Cislaghi <s.cislaghi_at_gmail.com> escreveu:
>
>
>
> Ho Ricard,
> Which version are you using of clusterware and database?
> May you check also permission of file inside ASM?
>
> Stefano
> On Mar 28, 2012 12:46 PM, "Ricard Mart�ez" <ricard.martinez_at_gmail.com>
>
> wrote:
>
> > Hello
> > Anyone have hit this error trying to do alter system scope=spfile?
> > ORA-32000: write to SPFILE requested but SPFILE is not modifiable
> >
> > No single note on metalink about it. I saw a few notes in oracle forum
> > about ASM diskgroup being down, but they are up and runing.
> > Thanks
> >
> >
> > --
> > http://www.freelists.org/webpage/oracle-l
> >
> >
> >
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Wed Mar 28 2012 - 06:34:19 CDT