LogMiner?
Gus Spier, December 09, 2010 - 9:41 pm UTC
Tom, is this a case for LogMiner? It depends on having archived redo logs from last month, of course. It might be a heck of a lot of bother, but it's feasible, right?
Gus
December 10, 2010 - 9:55 am UTC
it would be almost impossible to process - it would be a HUGE amount of data for every change, you would have to filter millions or billions of rows.
while technical possible, I do not believe it to be feasible.
(from Middleburg! I'm in Round Hill :) )
OK
Raama, December 10, 2010 - 5:12 am UTC
Hi,
You can try versioning using dbms_wm.enableversioning. Please refer documentation for arguments and usage. This creates a history table named as <table_name>_hist with complete list of DML changes happened for the table.
December 10, 2010 - 10:17 am UTC
that actually creates a history VIEW, the history is versioned in the table itself.
I forgot about that - but yes, that would be viable IF you can take the performance hit. Lots of triggers in play and your table constantly gets larger as deletes are turned into updates and updates are turned into an update and insert of a new row. You'd have to be purging old rows manually (using the documented calls in dbms_wm) over time.