| Query monitoring/intercepting [message #438679] |
Mon, 11 January 2010 14:09  |
newerakb
Messages: 3
Registered: January 2010
|
Junior Member |
|
|
Wasn't sure exactly where to put this, sorry if I'm in the wrong place.
I was brainstorming for an Oracle->Teradata Data Warehouse ETL process, and was wondering if it's possible to run an application on the Oracle side that constantly monitors incoming queries, and triggers a separate action on certain conditions.
Example: If a user or batch runs a DELETE statement, when the DELETE query is sent to the parser (or wherever Oracle sends queries, I'm a Teradata guy), the application will see the query and write it to a separate transaction table.
Essentially we don't want to have to update hundreds of separate applications to put new logging transactions in every time we delete. It would be better if a single application ran at a lower level that monitored every transaction by itself. This would allow our ETL process to just pick up the transaction list.
Thanks for any suggestions.
-Kevin
|
|
|
|
|
|
| Re: Query monitoring/intercepting [message #438681 is a reply to message #438680] |
Mon, 11 January 2010 14:32  |
newerakb
Messages: 3
Registered: January 2010
|
Junior Member |
|
|
BlackSwan wrote on Mon, 11 January 2010 14:20I suggest you modify the application doing the SQL to add it to your transaction list.
What would 'the application' be in this instance? We have hundreds of PL/SQL batches that would have to be updated with improved transaction logging to allow for any sort of accurate ETL process. Either way the work has to be done on Oracle.
I'm trying to think of a way to make life EASIER on the Oracle DEVs, not harder.
|
|
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
