Adding INSERT statement to SELECT statement changes execution plan

We have a query based on few tables and views.
When we run "SELECT" statement, this query goes for Nested Loop based Execution plan and finishes off very quickly.
However, when we add INSERT statement to this "SELECT" statement goes for HASH join based execution Plan. Any help highly appreciated.:confused:

The database being used is 10g R 2.

An INSERT needs to optimize the update off ALL the indexes also.
;)

Hi,

How many records are you trying to load? What is the time difference in both the approach?

Why not use a USE_NL HINT to achieve this?
OR Use a BULK LOAD using FOR ALL statement?

Kind Regards,