When required I did it through a logon trigger ... wait I still do it.
Raj
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having
Oradebug is the right way to go because, for some reason,
alter system set events='904 trace name errorstack forever, level 10';
doesn't do anything. The only way to activate trace is to go to
oradebug,
attach the session (of course, one needs to do gymnastics with V$SESSION
and V$PROCESS to find
Hi!
Note that when you set an event with alter system, it will only apply for
new sessions created, not for any existing ones.
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 4:19 PM
Oradebug is the right way to
On 01/20/2004 02:59:35 PM, Tanel Poder wrote:
Hi!
Note that when you set an event with alter system, it will only apply
for
new sessions created, not for any existing ones.
And that, exactly is the problem. First, when you set event using
alter system, the setting is system wide. Second, if you
You can also use DBMS_SYSTEM.SET_INT_PARAM_IN_SESSION and
DBMS_SYSTEM.SET_BOOL_PARAM_IN_SESSION, in lieu of oradebug.
-Mark
Mark J. Bobak
Oracle DBA
ProQuest Company
Ann Arbor, MI
Imagination was given to man to compensate him for what he is not, and
a sense of humor was provided to console him
But you can't set events with it :(
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 10:39 PM
You can also use DBMS_SYSTEM.SET_INT_PARAM_IN_SESSION and
DBMS_SYSTEM.SET_BOOL_PARAM_IN_SESSION, in lieu of oradebug.
For that, there is DBMS_SYSTEM.SET_EV. ;-)
-Mark
Mark J. Bobak
Oracle DBA
ProQuest Company
Ann Arbor, MI
Imagination was given to man to compensate him for what he is not, and
a sense of humor was provided to console him for what he is. --Unknown
-Original Message-
Sent: Tuesday,
One thing I've been looking for is a way to set a string parameter in
another session, The two you mention handle INTEGER and BOOLEAN. I want
a way to set TRACEFILE_IDENTIFIER to a string in another session to make
it easier to identify trace files.
Any ideas?
Stephen
[EMAIL PROTECTED]
Ok, yeap I confused this with READ_EV, which can't read event from other
sessions...
Great job ;)
Tanel.
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Tuesday, January 20, 2004 11:19 PM
For that, there is DBMS_SYSTEM.SET_EV. ;-)
-Mark
Mark
On 01/20/2004 03:39:25 PM, Bobak, Mark wrote:
You can also use DBMS_SYSTEM.SET_INT_PARAM_IN_SESSION and
DBMS_SYSTEM.SET_BOOL_PARAM_IN_SESSION, in lieu of oradebug.
Thanks, Mark! I've learned something from you today! Who says
that one cannot teach an old bear new tricks.
--
Please see the official
It turns out that the user had configured TOAD to use a table filter, which causes it
to create and store a query. As you've probably guessed, the query was referencing a
column which no longer exists.
On a related note, I initially tried to capture the failing query using alter system
set
I went through a similar problem with the 904 error. I had to use oradebug
to get a trace file to be produced.
Good luck,
Chris
-Original Message-
Sent: Monday, January 19, 2004 8:14 AM
To: Multiple recipients of list ORACLE-L
It turns out that the user had configured TOAD to use a
Does his version of TOAD support your Oracle server version ? We tried to
run our (outdated) version of SQL Navigator against a 9i DB and would get
weirdness like this from time to time when accessing the Oracle data
dictionary.
mvg/regards
Jo
Norris, Gregory T [ITS] [EMAIL PROTECTED]
13 matches
Mail list logo
