Originally posted by adewri
And BTW Abhay on what basis have you said that using database link is not a good practise. What process gets slowed down? Either way you need to make a database connection. So whats wrong with database links.
Frist let me list defects in using DB link.

* Password of Remote DB can be known to any user who has got sufficient privilages to see sys objects. Even when DB link is private to the user x, user y can know the login credentials of the remote DB.

* Causes memory/stack overflow at times & this may lead to abnormal shutdown of the DB.

* Many bugs reported while using DB Link.

Now how would DB Link slow up process

* NOT IN clauses wont just turn up over DBs if Tables in Q are big.

* Even EQUI joins will eat time, due many round trips via N/W.

Rather, you can do some think like this ( On Local Sever )

* Create Temp_Table.

* Load data from remote DB through COPY ( by setting arraysize conisderably high ).

* Pick the data from temp_table load it to main table using Insert..Select ( the desired rows ).

Abhay.