From cdyke@froggy.com.au Mon, 26 Nov 2001 00:58:18 -0800 From: Casey Dyke Date: Mon, 26 Nov 2001 00:58:18 -0800 Subject: Creating a Reporting Instance Message-ID: MIME-Version: 1.0 Content-Type: text/plain Hiya folks, Task at hand is to create a reporting instance from an v8.0.4 beast (in structure, not size) originating from ISAM. We need to replicate the main transaction tables (30 in all) + reference tables. All will receive I, U and D activity. Seems to me quite an easy solution to use simple snapshots/snapshot logs and be done with it. A colleague, however, questioned why we need snapshot logs and "interference" w/the PROD instance. Fair enough I guess. The reason behind the logs was easy to refute, but the whether we have other non-intrusive methods didn't roll off my tongue as well as I would have liked it to have. Some options I came up with: - Transportable tablespaces - Log Miner - Shareplex - cloning - RO standby ... The question I have is what other options have others tried/implemented? And, for those of you w/DW experience (which I obviously do not have) - how do you handle the incremental transactions after initial population? Is it accepted practice to use triggers to feed scratch tables for ETL processes? What comes into play when restrictions on the prod instance are in place (ie: the config cannot change)? What sort of comparison routines are standard for an OLTP->Datamart/DW setup? Hope that all makes sense. My situation is not particularly complex, but I've no doubt others can provide handy insight. Cheers, Casey ... -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Casey Dyke INET: cdyke@froggy.com.au Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).