Re: read-only snapshots

Pat

What's the error you're getting? There shouldn't be a problem with a single refresh group that I can think of. The intelligent agent is only needed for job and event handling, so if you're not setting up the refresh as a job through OEM, it shouldn't be causing the problem.

You only need a single snapshot log on the master for each table being replicated. If there's a lot of data being moved, I'd certainly recommend using snapshot logs so you can do a fast refresh rather than a complete one. If you have dubious communication links, make sure you use fast rather than the default force.

HTH. Pete

Pat Minnis wrote:

> I recently had to come up with a solution for 3 laptop computers to access
> real data and the application had to use Oracle SQL to access it. The
> laptops will be connected to the network only nightly.
>
> I setup the 3 laptops to use a database server and read-only snapshot images
> of 3 tables. Works fine as long as a night operator manually refreshes each
> snapshot separately.
>
> The problem is this: The data will be large enough that having a night
> operator stick around to do this would be a new full-time job. I tried
> creating a refresh group for all three snapshots using Enterprise Manager,
> but I get an error -- unless I have a separate refresh group for each
> snapshot. I tried filling in the next and interval values. When the next
> interval time comes, no automatic refresh. I don't need intelligent agent
> for this, do I?
>
> I haven't put any snapshot logs out there yet, so I'm not getting fast
> refresh. Do I put this on the master database? Do I need a separate
> snapshot log for each laptop snapshot?
>
> Can anyone shed some light on how this is done?

--
Regards

Pete

Received on Thu Aug 05 1999 - 11:12:35 CDT