Hi Jeremiah > I don't like any of the suggestions so far, because they take more > time than necessary. DB links do ONE ROUND TRIP for every row > fetched! That is not efficient. Export is a nightmare of potential > failures. I think you can devise the best solution by just copying the > database files.
Are you sure about the "one round trip" thing. I may be mistaken but I must admit that has not been my experience. Are you thinking of occasions when you use a remote table (accessible via a DBLink) in a local join? In such cases the optimizer might set up the plan to get the remote rows individually rather than doing unproductive remote full or range scans. One would anticipate that a query like INSERT into <localtable> (select * from remotetable@link) would pull things over in a stream. OCI certainly streams query results like that - I'm not saying that DBLinks are based on OCI - just that there is precedent for this in at least one Oracle networking layer. Kind regards Dale -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
