On the subject of direct path INSERT,
I have given Append hint in the insert query which is loding data from remote DB,eventhough the time taken by the insert query is not reduced.
Is a direct-path INSERT actually taking place at all? A couple of quick ways to check:

1) Attempt to count the rows in the table immediately after the INSERT completes (before any COMMIT or ROLLBACK). If you get "ORA-12838: cannot read/modify an object after modifying it in parallel" then it was a direct-path INSERT.

2) Using SQL*Plus AUTOTRACE (or equivalent - I don't have TOAD but I'm sure it has a session stats page), is the redo size smaller when using the APPEND hint than without?

Are you talking about the NOLOGGING in the create table command?
It is a table/index/mview attribute and can only appear in CREATE or ALTER syntax. If your database is running in NOARCHIVELOG mode, everything is in effect NOLOGGING ("SELECT log_mode FROM v$database" to check); if not, check the table with "SELECT logging FROM user_tables WHERE table_name = ...".

However as others have suggested, the performance issue is most likely nothing to do with the INSERT but more to do with the SELECT and its execution plan.