Re: driving_site hint in Materialized View definition

That "demonstrations" in that note are a complete load of rubbish - the only sensible point is the conclusion:

"
a distributed DML statement must execute on the database where the DML target resides. The DRIVING_SITE hint cannot override this.

DRIVING_SITE hint means that entire cursor (not a subquey) is supposed to be mapped remotely. That means INSERT, UPDATE or DELETE or also CREATE TABLE cannot be executed remotely. "

I've emailed support suggesting they withdraw it and rewrite the examples.

-- 
Regards

Jonathan Lewis
http://jonathanlewis.wordpress.com

Author: Cost Based Oracle: Fundamentals
http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html

The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


"Yong Huang" <yong321_at_yahoo.com> wrote in message 
news:06ac8013-c447-45b7-bc73-8a8cd452329b_at_l32g2000vba.googlegroups.com...


> On Jun 27, 9:11 am, "Jonathan Lewis" <jonat..._at_jlcomp.demon.co.uk>

> wrote:

>>

>> The driving_site() hint is not legal in "create as select"

>> or "insert as select". The select statement has to operate

>> at the database where the create or insert takes place.

>>

>> I think if you search metalink, you'll find a note that makes

>> this point - but I don't have a reference to the doc ID.

>

> Metalink Note:825677.1 says in

>

> insert /* DRIVING_SITE(remote_example_data) */ into example_data

> select /* DRIVING_SITE(remote_example_data) */ remote_example_data.*

> from ...

>

> the first driving_site hint, the one after insert, is ignored. That

> must be the note you're referring to?

>

> Yong Huang