There should not be a lot such users.Quote:
Originally posted by abhaysk
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.
Many bugs reported while using Oracle DB... should we stop using it?Quote:
Many bugs reported while using DB Link.
For simple task as "insert into t1 select * from t2@db2" it is very convenient to use db_links (not much bugs on this one, i think).Quote:
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 ).
If you need to do "not in" joins (i almost never do anyway) or something like that, you can still create temp table and insert in it through dblink, and process data single-sided afterwards.