Events and the SPFILE
Posted on May 8, 2008
Using the ALTER SYSTEM SET EVENT command always results in a static change;
specifying the SCOPE=MEMORY clause is not allowed.
The events use the syntax described earlier, but only the concatenated form is allowed
if there are multiple events. To disable or alter a single event in a list, the whole list
has to be reentered.
To disable all events, the EVENT keyword has to be cleared using:
SQL> alter system reset event scope=SPFILE sid=’*';
The “*” in the example above can be replaced by the an instance name in a Real
Application Clusters configuration.
Examples
The init.ora method (ascii text file):
event=’10325 trace name context forever, level 10′ # CF trace
event=’10015 trace name context forever, level 1′ # Rollback
The SPFILE method (server-side binary file):
SQL> alter system set event =
2 ’10325 trace name context forever, level 10
3 :10015 trace name context forever, level 1′
4 comment = ‘Debug tracing of control and rollback’
5 scope = SPFILE;
Copyright © Oracle Corporation, 2001. All rights reserved.
Diagnostic Events
Chapter 2 – Page 27
The text string must be on a single line, and cannot be a string expression (that is,
several strings joined by the || operator.)
Note the syntactical differences when setting an immediate event:
SQL> alter session set events =
2 ‘immediate trace name controlf level 2′;
Popularity: 3% [?]
Related Posts:
» Filed Under Other
Comments
Leave a Reply