| **
Hey Claire: I’ve been there, (with other non-ARS
applications) and it isn’t any fun. Have you been able to capture the
SQL that the users are getting timeouts with? Since this is slow death by
way of DBA, I would suggest that getting him to run an explain plan on the SQL
that is generating the timeouts might be helpful. Usually the problem
that you run into is on of I/O choking the system when you’ve just run gather
stats. As I first step in cases like this I always ask the DBA to begin
gathering statspack information so that we can track performance; that is
somewhere that you might want to look into. Also, it would be interesting to know what
sort of operations it is that are choking the server. My bet would be
that INSERT and UPDATE statements are the problem, and that because of the
increased reliance on indices after the gather statistics you are now losing
performance and getting timeouts. Sorry if this doesn’t really help
exactly, but some statspack results or an explain plan results on the failing
SQL would be helpful. Regards, Adam Pederson ITSM Consultant Xinify Technologies, Inc. From: Action Request
System discussion list(ARSList) [mailto: This is the thing the DBA did. exec dbms_stats.gather_schema_stats('ARADMIN') Right now we are dead in the water. Remedy Tech
Support is working on it too... The AR System was up and running at the time and
that command has never been run on this database. If I stop and start the ARS Server service,
people can do searches for a little while, then they get time outs. Any ideas? Claire "10 hours of sleep in 72 hours"
From: Action
Request System discussion list(ARSList) [mailto: ** I was thinking the same thing - the Analyze
was like a Checkpoint, updating the statistics. That would constitute a
pretty significant re-org of the DB, especially if it had been a while since
the last time it was run. Rick
From: Action
Request System discussion list(ARSList) [mailto: ** Ensure that you have
appropriate indexes for the long running queries. Running statistics
should be a good thing. Maybe they had not been run in a long time and now your
current indexes do not support your bigger queries. Also, fund out exactly what
the DBA did. I can remember having problems when stats were run on each table
in its entirety. There is a way ton run stats on just a small percentage of the
rows in each table which may work better. On 7/22/06, Rick
Cook <[EMAIL PROTECTED]>
wrote: Ask your DBA what the Analyze function did. I wonder if it
reset some indexes or page sizes or something.
|
- Re: Oracle Analyze Sanford, Claire
- Re: Oracle Analyze Adam D Pederson
- Re: Oracle Analyze Benter, David W CTR NSWC PC
- Re: Oracle Analyze Rick Cook
- Re: Oracle Analyze Axton
- Re: Oracle Analyze McKenzie, James J C-E LCMC HQISEC/L3
