Re: 10046/10079 Tracing understanding - SOLVED

  • From: Nuno Souto <dbvision@xxxxxxxxxxxx>
  • To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 5 Aug 2005 09:07:53 +0800

Quoting Brian Wisniewski <brian_wisniewski@xxxxxxxxx>:

> When it was called from java it was definitely returing the entire 32K when
> the OUT field was CHAR.  When I called it from another PL/SQL pgm via sqlplus
> @..  it did NOT return the entire contents. 
>  
> I'm not sure if this is a thin driver issue or what but I'm still researching
> this.  I'm going to try the OCI driver next and see if that makes a
> difference or not.
>  
> That was fun to track down in a twisted sort of way.
>  


Excellent work, Brian.  Thanks for sharing this, might actually explain
many "weird" performance problems.
I'm curious if this would happen as well if the parameter being passed
was a type with CHAR attributes inside?  I'm quite sure we've used CHAR 
in some of our types in the past but because we always used the type 
itself rather than discrete fields we never hit the problem.  
Must try this out. You were using 10.1, right?

-- 
Cheers
Nuno Souto
from sunny Sydney
--
//www.freelists.org/webpage/oracle-l

Other related posts: