Re: Physical Standby and Streams

What is your OS, version? What database is this LOG_ARCHIVE_CONFIG from? I guess the primary, but please specify your setup carefully to enable the people on this list to help you properly. How are you managing the standby? EM/GC, Data Guard broker or manually through SQL*Plus?

Assuming Oracle 10gR2, parameters from the primary:

Essentially, the LOG_ARCHIVE_CONFIG parameter is used to define the DB_UNIQUE_NAMES that are part of the DG configuration. Additionally you can also specify the direction of the redo stream. This is used to prevent a primary from accidently receiving archives from another database, e.g. when a standby has been activated, resulting in two primarys within the setup.

The name (DB_UNIQUE_NAME) 'STANDBY' you use makes me think you have named your databases PRIMARY and STANDBY. Why? this is going to be very confusing when the primary fails and your database STANDBY has to fullfill the PRIMARY role. I'd suggest to use unique, but just identifying, not role-describing names for your databases!

SEND only will do the job, but you can also consider to use 'SEND,(STANDBY,WAREHOUSE)'. But I'm not very knowledgeable (not to say ignorant) about streams, maybe WAREHOUSE (or what the DB_UNIQUE_NAME of that database might be) shouldn't be included here. Sam Chakkanat (search the archives) will be happy to help on streams topics.

I set up Data Guard w/o EM/GC/DGBroker. Just SQL*Plus/script/manually managed. And it doesn't need LOG_ARCHIVE_CONFIG at all. Which doesn't mean you shouldn't use it. Normally I just set it at SEND,NORECEIVE or NOSEND,RECEIVE. Best regards,

Carel-Jan Engel

===
If you think education is expensive, try ignorance. (Derek Bok) ===

On Mon, 2006-12-18 at 14:18 -0700, UtahToad wrote:

> We have a physical standby (DataGuard) set up and want to set up streams
> to a warehouse. The physical standby is functioning well , but we can't
> get the logs shipped over to the warehouse database. Does anyone have
> any experience on this type of configuration? Are there any insights for
> us? Could there be a missing parameter?
>
> We think that the parameter LOG_ARCHIVE_CONFIG is the culprit. It is
> currently set at "SEND,DG_CONFIG=(STANDBY)" and we think it might need
> to be just "SEND" only, but we are hesitant to change it because it
> might screw up our physical standby. It originally was
> "DG_CONFIG=(STANDBY)".
>
> Insights, anyone?
>
> Thanks,
> David
>
> --
> David Hicken
> Flying J - Senior Database Administrator
> david(dot)hicken(at)flyingj(dot)com
>
> Everybody is ignorant, only of different subjects.
> -- Will Rogers
>
>

--
http://www.freelists.org/webpage/oracle-l