reaque,

https://www.freelists.org/post/oracle-l/plan-shows-insert-into-remote-table-using-all-remote-selects,1
Jonatahn LewisYou can't.

The query that supplies data to the insert has to be executed by the database
where the DML is taking place - which means the remote (to you) database. The
plan you see is the plan from the perspective of the remote (to you) database,
which is why it reports the table which you think of as local as being remote
(to the executing session).

If you want a plan which does ALL the work at the local (to you) database you
need to create a local (to you) view for the query (possibly with a no_merge
hint) and the do "insert into remote_table select * from local_view". You
might, however, manage to get away with creating a set of hints on the query
that force a nested loop join all the way through every table, then the plan
would be (just like operation 22 in the current plan) just "REMOTE", with the
join query being reported as the remote SQL.

Alternatively you could create a pipelined function that returns the data you
want and "insert ... select from pipelined function"
https://jonathanlewis.wordpress.com/2010/10/07/distributed-pipelines/


Regards
Jonathan Lewis