I wrote about tracking ddl changes with a trigger there : track ddl changes
Another option is to use auditing.
A new and cool alternative is to use enable_ddl_logging (11gR2). This will track all ddl’s in the alert log
ALTER SYSTEM SET enable_ddl_logging=TRUE
Then later you issue
create table t(x number)
and you see in the alertLSC01.log
Tue Apr 05 14:43:32 2011
create table t(x number)
Wait, that’s not really verbose !?
Remember the alert log is just there for backward compatibility, it is time you start looking in the xml file 🙂
There is not really much more there but the module, which indeed reveals someone is using TOAD to access my database !
“which indeed reveals someone is using TOAD to access my database” – are you suggesting that using TOAD is wrong against database???
shhh, don’t tell anyone, it’s me 😉
exec dbms_application_info.set_module(‘Toadlicker’,’;-)’);
This feature comes with “Oracle Change Management Pack” and is available for EE only. You got pay extra to use this. 🙁
http://download.oracle.com/docs/cd/B28359_01/license.111/b28287/editions.htm#CJACGHEB
@Joel 😉 indeed you could fake your module !
@Asif Thanks for this info
Hi Laurent
, this feature was already in 11gR1 available.
See here: http://sysdba.wordpress.com/2007/10/16/ddd-logging-in-the-alert-log-in-11g/
Cheers,
Lutz
Indeed, any clue why it is not documented in the 11gR1 reference ?
So, please let us all know, what are, if any, are issues using Toad against a database? I have some DBAs talking about turning off access to clients using Toad, but I dont know what the reservations are?
Thanks
Pingback: Laurent Schneider » On using Toad against a database
@Ebrahim : I like your question, I tried to answered it there : https://laurentschneider.com/2011/06/on-using-toad-against-a-database.html
Pingback: On using Toad against a database « Ukrainian Oracle User Group