We have a source database which is Oracle 11g RAC. The target database
is a stand laone database (11g).

We need to create Materialized View in the Target database based on
tables in the RAC source database.

The Refresh method is Refresh Fast on Demand.

Is the process of creating Materialized View Logs in a RAC same as the
one for creating MV logs in a stand alone database ? What if the
instance/node in the RAC where the MV Logs are created goes down ?

If the configuration of MV logs in a RAC is different from the one in
a stand alone database, can you please describe in detail or point to
web site that explains it in detail ?

Thanks in adavance.

On Apr 8, 6:42*pm, Ora_DBA <sanjaydharmadhik... (AT) gmail (DOT) com> wrote:
Yes, the basic way you define an mview when the source is RAC is the
same as when the source db is non-RAC.

What happens when one instance is down depends on how you define the
database link, that is, on a specific instance or capable of
connecting to any available instance.

HTH -- Mark D Powell --

On Apr 9, 3:42*am, Ora_DBA <sanjaydharmadhik... (AT) gmail (DOT) com> wrote:
Hi,
On RAC there is a single database. Each RAC instance runs on the very
same database.

RAC is a shared everything architecture - nothing at all like the
inferior (shared nothing) cluster technologies used by many of the
other database vendors.

In other words, a database resource (table/sequence/view/procedure/
etc) is available on all that database's cluster instances.

Regards
Sandy

On May 11, 10:16*am, sandeep pande <sandy.sof... (AT) gmail (DOT) com> wrote:
"nothing at all like the inferior (shared nothing) cluster
technologies used by many of the other database vendors."

Not sure about the meaning of 'inferior' here...

Cheers.

Carlos.