Re: Tracking problems
Date: Wed, 3 Mar 2010 11:12:15 +0000
I'm pretty certain that the first step would be to get a better problem statement, difficult maybe if it is your boss asking. The log checking that you and Grid do is the reactive standard thing. But it appears that there is a very specific reason for a very general question here.Your bosses question is
"There is a problem with connection pools on one of our weblogic servers, is the database OK?"
I think I'd be asking
"What *exactly* is the problem on the weblogic server, is it reporting an Oracle error, has it got a performance issue, what logs does weblogic have that indicate a database issue?"
I've spent far too much of my life chasing problems that didn't actually exist to spend too much more time doing that.
On Wed, Mar 3, 2010 at 11:02 AM, Ozgur Ozdemircili < ozgur.ozdemircili_at_gmail.com> wrote:
> How do you track the problems? It seems we had a problem with connecction
> pools of one of the Weblogic servers.My boss asked me if there was any
> problem with the DB.Now reviewing our Gridcontrol there seems no problem. I
> have checked the logs CRS_ADMIN / *dump files / alert.log.Yet nothing.
> How do you guys resolve this kind of issues? Which logs do you review? Any
> scripts or tools that can show me if there was any error/ problem on a node?
> Özgür Özdemircili
> Code so clean you could eat off it
-- Niall Litchfield Oracle DBA http://www.orawin.info -- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 03 2010 - 05:12:15 CST