title: Audit on oracle schema for dml statements
body: <p>I need to secure an oracle user for doing inserts/updates/deletes from outside programs written by me.</p>
  
  <p>I googled a bit around to find what I need. I know you can use own written db triggers.
  And I now there are two major systems from oracle (at least that is what I found).
  You can use fine grained auditing. And you can use the audit trail.</p>
  
  <p>I think in my case the audit trail comes close but just isn't what I am looking for. Because I need to now from which program the connection to the DB is coming. For example I need to register all connections that are doing inserts/updates/deletes with there statements executed that are coming from sql developer or toad. But all the other connections may pass without audit.</p>
  
  <p>On daily basis I have lots of connections so registering everything is too much overload.</p>
  
  <p>I hope one of you have a good idea on how to set this up.</p>
  
  <p>Regards</p>