Re: Favorite tool
- From: Seth Miller <sethmiller.sm@xxxxxxxxx>
- To: Oracle L <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 7 Oct 2013 10:34:53 -0500
Robert,
To prove that the database is not "going down", you could write a simple
script to connect to the database via sqlnet (preferably from the client
server) every few minutes. You could also supplement that with the trace
log from the listener on the database server.
Include a time stamp before and after each connection so you can see if
there is a delay in the connection time. Maybe even throw in a query that
you know the client is executing when they are seeing the delays.
I'm sure you already know this, but this is what I would call a golden
opportunity to "coax" this application to upgrade to a database that is
supported.
Seth
On Mon, Oct 7, 2013 at 7:54 AM, Maaz Anjum <maazanjum@xxxxxxxxx> wrote:
> Assuming you have it set up, you could use Statspack as well.
>
> On Mon, Oct 7, 2013 at 8:25 AM, Storey, Robert (DCSO) <
> RStorey@xxxxxxxxxxxxxxxxxx> wrote:
>
> > Probably been asked a few times, so I'll throw it out there again.
> > Its Monday morning and our support team tells you that the database seems
> > to go up and down several times during a 30 minute period on Saturday
> > night. Users were complaining of using the application and getting the
> > dreaded spinning hour glass. But, a check of the alert.log and other
> > Windows logs shows no errors, no trace files, and no downtime on the
> > database.
> >
> > What's your preferred tool for after-the-fact diagnosis of the issue?
> > This is on a 9i system but I don't have it hooked into grid or cloud
> > control.
> >
> > Foglight from Toad? AWR reports (assuming you were in Grid or Cloud)?
> > Other good tool?
> >
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
> >
>
>
> --
> A life yet to be lived...
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
