Re: Performance probs with db_links in PL/SQL

Just a guess, but this might be a TCP_NODELAY problem. Try a very simple test with a table of 1 column varchar2(2000). Copy it using the PL/SQL loop with 1300 bytes used, and then with 1500 bytes and see if you get the same performance drop.

--

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Dwight Walker wrote in message <7leaai$ffd$1_at_news.mel.aone.net.au>...
>I have a procedure that has a cursor for loop that basically selects all
>columns from a remote ( but on the same physical system ) database and
>inserts them into a local table.
>
>It takes hours to insert 100,000 rows using the PL/SQL procedure, but a
>couple of minutes via a " create table as select .... " or "insert into
>table select..." SQL statements. There are no indexes on the local tables,
>and no indexes used on the remote table as it is selecting every row
anyway.
>
>After some investigation, it seems that if the cursor returns any more
than
>43 columns the time taken to run startes to blow out 100 fold, but less
than
>43 columns, run times are acceptable.
Received on Thu Jul 01 1999 - 16:13:55 CDT