Re: Snapshot Logs/Triggers

From: Casey Dyke <cdyke_at_froggy.com.au>
Date: Wed, 28 Nov 2001 08:32:10 +1100
Message-ID: <3C04065A.EF9595FE@froggy.com.au>

Have definitely considered, but probably not to lengths I could have. Simple snapshot replication works so easily - but it comes at the cost already mentioned. Think I'll dive deeper into logmnr today to see if it provides potential.

Guess I could do something like:

Have a marker to record last archived redo touched (from v$archived_log)
process wakes up, reads marker and loops through all since archived log files and feeds them into logmnr (dbms_logmnr.add ... - can't remember the package call, but you get the drift :-) )
start my analysis on the logmnr view containing my redo
build a file of transactions as I suck them out of the log files
replay that on the reporting instance

If that is possible - and as I type I guess I'm thinking it is - that potentially gets around the cost of snapshot logs and triggers. Anyone disagree w/that? Anyone doing similar? Any scalability issues? Will need to look into the actual text of the logmnr contents, but am assuming they're in a format in which I can easily suck them out w/out much formatting.

Thanks for the suggestion. If anyone is interested in the outcome, mail me offline. :-)

aviion wrote:
>
> Have u tried building your own replication using dbms_logmnr.
>
> --
> Posted via dBforums
> http://dbforums.com
Received on Tue Nov 27 2001 - 15:32:10 CST