Re: Streams question

philip wrote:
> I am trying to do the following, and would like to know if anyone else
> has either done it before, or know of any reason it will not work.
>
> I am using Oracle 10.1.0.4 and have streams setup for replicating data
> to a reporting DB (one way). There is a large amount of data (80 GB
> and growing) so things go slow. The reporting DB is in a remote
> location that only has a 2 Mb link going to it.
>
> On a regular basis, once every week or two, we need to do a large
> amount of deletes, inserts and updates. On occassion we completely
> rebuild the master DB, due to ongoing changes in development.
>
> Currently, when a new DB comes along, I do the following steps: stop
> streams, rebuild the DB, export the DB using datapump and a certain
> SCN, compress and FTP the dump to the remote location, uncompress and
> import the dump and then turn streams back on. From the export on,
> takes about 8 - 10 hours, and I have to take an outage for the entire
> duration.
>
> I would like to turn the master DB back on for regular use after the
> export, and let streams handle synchronizing the report DB afterwards.
> Is this going to blow up in my face, or should I be OK?
>
> Any suggestions or advice would be appreciated.
>
> Thanks,
> Philip

Transportable tablespaces and a larger pipe.

But it seems to me that your biggest problem is a maintenance process that is broken. Complete rebuilds of the master DB shouldn't be happening as often as you seem to indicate.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)