Re: Illegal option for "ALTER SYSTEM"???

From: joel garry <joel-garry_at_home.com>
Date: Wed, 7 Jul 2010 09:12:29 -0700 (PDT)
Message-ID: <cd68cff6-a869-400b-a1a1-bd12b121b4c5_at_h40g2000pro.googlegroups.com>

On Jul 7, 6:22 am, Mark D Powell <Mark.Powe..._at_hp.com> wrote:
> On Jul 7, 8:21 am, Mladen Gogala <gogala.mla..._at_gmail.com> wrote:
>
>
>
> > This is 10.2.0.4 on Linux x86-64:
>
> > SQL> alter system set events='1013 trace name context off' scope=both
> > sid='*';
> > alter system set events='1013 trace name context off' scope=both sid='*'
> >                                                       *
> > ERROR at line 1:
> > ORA-02065: illegal option for ALTER SYSTEM
>
> > What's going on? When I try something else, this works:
>
> > SQL> alter system set global_names=false scope=both sid='*';
>
> > System altered.
>
> > Elapsed: 00:00:00.17
> > SQL>
>
> > Why are "SCOPE=BOTH SID='*'" illegal options for alter system set events
> > and yet work perfectly well with set global_names?
>
> > --http://mgogala.byethost5.com
>
> Maybe because the correct spelling is event, not events, in the ALTER
> SYSTEM command per the SQL manual which also says the parameter is not
> modifiable
>
> SQL> alter system set event = '1013 trace name context off'
> scope=spfile;
>
> System altered.
>
> SQL> /
> alter system set event = '1013 trace name context off' scope=both
>                  *
> ERROR at line 1:
> ORA-02095: specified initialization parameter cannot be modified
>
> Though strangely enough if you leave scope= off the command works with
> events:
>
> SQL> alter system set events = '1013 trace name context off';
>
> System altered.
>
> Posted tests use 9.2.0.6 and appear to match initial posted results,
> but reference to SQL manual based on 10.2.
>
> HTH -- Mark D Powell --

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SYS_at_TTST> alter system set event = '1013 trace name context off' scope=both ;
alter system set event = '1013 trace name context off' scope=both

                 *

ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified

SYS_at_TTST> alter system set event = '1013 trace name context off';  alter system set event = '1013 trace name context off'

                  *

ERROR at line 1:
ORA-02095: specified initialization parameter cannot be modified

SYS_at_TTST> alter system set events= '1013 trace name context off';

System altered.

SYS_at_TTST> alter system set event = '1013 trace name context off' scope=spfile;

System altered.

"The default is SCOPE=BOTH if a server parameter file was used to start up the instance, and MEMORY if a text initialization parameter file was used to start up the instance."

And here I am, using a server parameter file. I wonder if someone had the idea of using events to mean something different than event, but the reality became confused when someone said "let's document it and call it a feature." The manual does not say event is not modifiable (I could've missed something...), but rather should only be modified under supervision.

jg

--
_at_home.com is bogus.
http://hosted.ap.org/dynamic/stories/U/US_TEC_TECHNOLOGY_CONSOLIDATION?SITE=KYWAM&SECTION=HOME&TEMPLATE=DEFAULT

Received on Wed Jul 07 2010 - 11:12:29 CDT