From: "Dan A." <nospam@email.com>
Newsgroups: comp.databases.oracle.misc
Subject: database link - SQL getting chopped off?
Date: Tue, 5 Jun 2001 22:16:54 -0700
Lines: 30
Message-ID: <9fkec8$l7p$1@nntp.Stanford.EDU>
NNTP-Posting-Host: wrodenp733.stanford.edu
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400


We have some SQL here that uses a database link.  It works fine in most of
our
environments, but when we try and execute it in our production environment,
we get an error.

insert into table1
select field1, field2 from remotetable@otherdb b
where  b.field3 = 'X'
 and b.field4 = 'Y'

(The real SQL is much longer.)  It usually errors out with an  ORA-03113:
end-of-file on communication channel.  When we start reducing the where
clauses, (down to a total of about 2120 bytes for the whole SQL statement)
it will work.

One test actually worked with the full SQL but the results were as if the
last line of the where clause was never part of the
SQL statement.  It returned many more rows than the full where clause would
have allowed.


Is there a parameter to set the number of bytes a database link can
handle???

Any other ideas out there?

Thanks for any info on this!       -Dan