Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Diagnosing ORA-3113 errors

Re: Diagnosing ORA-3113 errors

From: Gaja Krishna Vaidyanatha <gajav_at_yahoo.com>
Date: Wed, 28 Jun 2000 18:32:42 -0700 (PDT)
Message-Id: <10542.110734@fatcity.com>


Bill,

You can turn on SQL*Net/Net 8 trace on the client and the server side and the tracefile usually points at the culprit. Most of the time, it is a network/router problem, an incompatible protocol stack or a version of SQL*Net that is buggy. I have also seen a flavor of this problem, when the version of SQL*Net on the client side is higher than the version of the listener. This was in the SQL*Net 2.2/2.3 days.

If the problem is re-produceable with a certain amount of accuracy and predictability, then turn trace on during a time of day, when not much is going on, so that you don't bottleneck your system/network by the tracing effort. You might want to set the trace at level - 16, so that you can get packet dumps to tell you in detail, what is going on. If you need help with reading the trace file, please post it (a part of it should be sufficient) and we could look at it.

Hope that helps,

Gaja.


Gaja Krishna Vaidyanatha
Director, I-O Management Products
Quest Software Inc.
(972)-304-1170
gajav_at_yahoo.com

"Opinions and views expressed are my own and not of Quest"



Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere! Received on Wed Jun 28 2000 - 20:32:42 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US