Re: logfile_name_convert set in spfile
- From: "Finn Jorgensen" <finn.oracledba@xxxxxxxxx>
- To: Prasad <p4cldba@xxxxxxxxx>
- Date: Fri, 25 Jan 2008 13:53:36 -0500
Well here's another little interesting quirk of Oracle's :
1* alter system set
log_file_name_convert=('/DGTEST01/DGTEST10','/DGTEST01/DGTEST10')
scope=spfile
DGTEST10> /
alter system set
log_file_name_convert=('/DGTEST01/DGTEST10','/DGTEST01/DGTEST10')
scope=spfile
*
ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified
DGTEST10> c/(//
1* alter system set
log_file_name_convert='/DGTEST01/DGTEST10','/DGTEST01/DGTEST10')
scope=spfile
DGTEST10> c/)//
1* alter system set
log_file_name_convert='/DGTEST01/DGTEST10','/DGTEST01/DGTEST10' scope=spfile
DGTEST10> /
System altered.
DGTEST10>
Put paren's around the parameter and it says you can't change it (which is
what the manual says as well), but remove the paren's and it works. Go
figure.
Mayen, yes that's doable, but as I said in my OP it's clumsy. I'm dealing
with 50+ production databases that needs this changed, and having to jump
through hoops like that means something gets missed...
Thanks Prasad for the "workaround".
Finn
On 1/25/08, Prasad <p4cldba@xxxxxxxxx> wrote:
>
> Hi Finn,
>
> It works for me .
>
> strings spfilemtrx.ora| grep log_file_name_convert
> *.log_file_name_convert='/metrix','/metrix'
>
> SQL> show parameter log_file
>
> NAME TYPE VALUE
> ------------------------------------ -----------
> ------------------------------
> log_file_name_convert string /metrix, /metrix
>
> SQL> alter system set log_file_name_convert='metrix','metrix'
> scope=spfile;
>
> System altered.
>
> then you can verify the spfile for the changes you made
>
> $ strings spfilemtrx.ora| grep log_file_name_convert
> *.log_file_name_convert='metrix','metrix'
>
>
> hth
> -Prasad
>
> On Jan 25, 2008 8:24 AM, Finn Jorgensen <finn.oracledba@xxxxxxxxx> wrote:
>
> > Folks,
> >
> > I'm in the process of testing data guard switchover in 10.2. A while
> > back I learned that log_file_name_convert must be set on the standby (as per
> > note 352879.1) in order to avoid ORA-19527's in the alert log. In a
> > switchover the old primary becomes the new standby. As such it needs this
> > parameter set prior to being started as the new standby to avoid the errors.
> >
> >
> > The problem now becomes that this parameter can not be changed with an
> > "alter system" command, not even if I specify "scope=spfile" (the manual
> > says it can only be changed with "alter session"
> > http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams112.htm#sthref478).
> > If my old primary is running on an spfile I am therefore unable to set this
> > parameter at all (at least, not without first creating a pfile, starting the
> > primary on that pfile, then creating a new spfile, which is clumsy).
> >
> > Anybody have any input on this dilemma? Seems Oracle shot them self in
> > the foot a little bit on this one.
> >
> > TIA
> > Finn
> >
> >
>
>
Other related posts:
