Sender: rwessman@rwessman-sun.us.oracle.com Newsgroups: comp.databases.oracle.misc Subject: Re: database link - SQL getting chopped off? References: <9fkec8$l7p$1@nntp.Stanford.EDU> From: Rick Wessman Message-ID: Organization: Oracle Corporation, Redwood Shores, CA Lines: 50 User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: 06 Jun 2001 04:48:03 -0700 NNTP-Posting-Host: 130.35.48.251 X-Trace: inet16.us.oracle.com 991828562 130.35.48.251 (Wed, 06 Jun 2001 04:56:02 PDT) NNTP-Posting-Date: Wed, 06 Jun 2001 04:56:02 PDT Sounds like a bug. ORA-3113 many times means that the server has died. Given the behavior that you're seeing, I would suspect memory corruption on the database server. I would contact Oracle customer support. There may be a fix for the bug already. One tip: locate a trace file that shows the SQL and have it handy. Rick "Dan A." writes: > 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 > > > -- Rick Wessman Security Assessment Group Oracle Corporation Rick.Wessman@oracle.com The opinions expressed above are mine and do not necessarily reflect those of Oracle Corporation.