Re: Oracle delta
Date: 6 Nov 92 10:32:53 PST
Message-ID: <1992Nov6.103253.18990_at_mic.ucla.edu>
In article <dtb.721034078_at_otto> dtb_at_otto (David Bath) writes:
>sstephen_at_us.oracle.com writes:
>
>>In article <1992Oct28.172223.11805_at_aio.jsc.nasa.gov>, russell_at_gothamcity.uucp (Russell Sellers [GHG]) writes:
>>>
>>> I have a question about the way oracle keeps track of the transactions
>>> that occurr during the day. I know that if I do a transaction then I can roll
>>> it back as long as a commit wasn't performed. Is there something like this
>>> that would allow me to rollback everything that occured during a say.
>>> What I am trying to find out is there some way to keep track of database
>>> delta's for each day. If there is can this file be parsed by a different
>>> program to produce some type of summary report.
V7 includes a Snapshot facility that does this. It keeps track of changes to tables (inserts, updates, deletes) and stores this in a log for each snapshot. You could use this information in whatever fashion you like. Snapshots are supposed to be for asynchronous database replication, but I don't see why you couldn't use them for what you want.
In any case, you can use post-insert, update, and delete triggers to log changes including pre and post values quite easily , if snapshots don't automatically give you everything you need.
Hope this helps,
- Dan
Daniel Druker
Anderson Graduate School of Management at UCLA
| Dan Druker | | agsm mail : ddruker | | internet : ddruker_at_agsm.ucla.edu | | oracle*mail : unix:ddruker_at_agsm.ucla.edu | ----------------------------------------------------------------------------
Disclaimer: None. I'm a student now and I don't care what you think. Received on Fri Nov 06 1992 - 19:32:53 CET