Re: Connection dropped on long remote DB link

To speed your queries you might try passing a hint in your select statement.

select /*+ DRIVING_SITE() */ *
from remotetable where certainstuff = otherstuff;

This will cause your table join on the remote stuff and will only bring the results back across the connection.

GREGORY KNESER wrote:

> Hello,
> We are using a remote DB link to connect to a machine far far away in
> Nebraska and then performing a
>
> insert into localtable
> select * from remotetable
> where certainstuff = otherstuff
>
> query to get certain data from the remote machine locally to perform some
> analysis on it. The only problem is that our db link connections get
> dropped with some frequency requiring us to restart the transfer process.
>
> Also, the transfer process itself takes several hours (too long).
>
> Does anyone have advice on
> 1)What could be causing the DB link to get dropped or what to do to maket
> it more stable?
>
> and/or
>
> 2)What (cheap) method we could use to transport this data? Most ETL tools
> seem to be out of the range of this project since the import of this data
> is just a relatively small part of our whole process.
>
> Thanks!
> Greg
Received on Wed Jul 18 2001 - 13:38:08 CDT