Re: How to increase max size of sqlnet traces?

Martin,

Lol, I don't know how I missed that parameter. Thanks, I'll try it out now. You asked about the OS: it is solaris.

Mark: In the past I have used sqlnet tracing to diagnose ora-3113 errors. I always set the trace_level to 16, just because. :) Does it go higher than that? :)

On Fri, Mar 15, 2019 at 2:30 PM Martin Berger <martin.a.berger_at_gmail.com> wrote:

> Hi Charles,
>
> what OS are you using?
>
> Did you try to set TRACE_FILELEN_SERVER to a value greater than 4G?
>
> just my ideas,
> Martin
>
> Am Fr., 15. März 2019 um 18:43 Uhr schrieb Charles Schultz <
> sacrophyte_at_gmail.com>:
>
>> Good day,
>>
>> We have an annoying issue whereby a connection fails with ora-3113 after
>> retrieving several million rows. I am trying to use sqlnet tracing to learn
>> more about the issue, but the server-side trace caps out at 4gb
>> (trace_level_server=16). Is it possible to increase the maximum size of the
>> server-side trace? If so, how? I also tried trace_level_server=10, but then
>> I realized that the auth_sesskey is not captured (or at least, I could not
>> find it), which makes it rather difficult to match the thousands of server
>> traces with the client trace.
>>
>> Help? :)
>>
>> --
>> Charles Schultz
>>
>

-- 
Charles Schultz

--
http://www.freelists.org/webpage/oracle-l