----- Original Message -----
Sent: Thursday, December 12, 2002 5:23
AM
Subject: RE: ora_sql_txt system defined
event attribute
It (ora_sql_text) won't work in 8i .. but in 9202 it works
fine, I think it was introduced in 8i, but extended in 9i...
I am not yet using dbms_system.ksdwrt in prod but on our ACPT
instances, I use it to capture all the DDL that happens in the database.
Raj
______________________________________________________
Rajendra
Jamadagni
MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot
com
Any opinion expressed here is personal and doesn't
reflect that of ESPN Inc.
QOTD: Any clod can have
facts, but having an opinion is an art!
-----Original
Message-----
From: Casey Dyke [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 11, 2002 4:59 PM
To: Multiple recipients of list ORACLE-L
Subject: ora_sql_txt system defined event attribute
hiya folks,
just curious whether
anyone is successfully using this attribute w/servererror trigger to capture
the sql for a failed transaction -- say for a 1555 error?
it would appear to be new to 9i as i can see it in the doco
for 9.2 and not 8i. furthermore, the event is simply not defined in
dbms_system w/in my 8i rdbms/admin dir (dbmsstdx.sql/dbmstrig.sql).
after an admittedly brief faff about w/v$session/v$open_cursor
& prev_sql_addr/prev_hash_value in 8i (ie: not this fancy new function) it
would appear that i capture code from the servererror trigger itself (say
something like 'select userenv('sessionid') ...) - rather than the offending
sql code. not exactly what i am looking for. but maybe i ain't working
hard enough ...
also, how many out there use dbms_system.ksdwrt in prod?
works fine in dev for me ...
cheers,
casey ...
