Path: text.usenetserver.com!out03b.usenetserver.com!news.usenetserver.com!in01.usenetserver.com!news.usenetserver.com!in03.usenetserver.com!news.usenetserver.com!news.glorb.com!news-feed.eu.lambdanet.net!not-for-mail
Date: Sun, 04 Nov 2007 18:27:53 +0100
From: Jan Krueger <jk@stud.uni-hannover.de>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
Newsgroups: comp.databases.oracle.server
Subject: Re: Database Performance Problem between 3:00PM and 4:00PM
References: <1193064977.148736.166830@i38g2000prf.googlegroups.com>
In-Reply-To: <1193064977.148736.166830@i38g2000prf.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 23
Message-ID: <472e0071$0$29370$4c56b896@news-read1.lambdanet.net>
Organization: Lambdanet
NNTP-Posting-Date: 04 Nov 2007 17:25:05 GMT
NNTP-Posting-Host: 	ª7Ž..news-read1.lambdanet.net
X-Trace: DXC=ekdi\ok7]bEoZ0@HBeNQ?@Xl04NJR<Y^MgS=CF9eQ^kIASkKU=o\gCOXBJ5klm9c>B@Jik<YWKBoMadfCka<L`ZN
X-Complaints-To: abuse@lambdanet.net
Xref: usenetserver.com comp.databases.oracle.server:437255
X-Received-Date: Sun, 04 Nov 2007 12:25:07 EST (text.usenetserver.com)

zigzagdna@yahoo.com wrote:
> I am Windows 2000 server using Oracle 9.2.0.6. We have strange problem
> where by database becomes extremely slow between 3:00PM and 4:00PM.
> Same queries which take  15 seconds before 3:00PM (e.g., 2:55PM) take
> 3-4 minutes at 3:00PM and after that. Poblem starts right at 3:00PM
> every day. No of users etc are same. We have asked users not to use
> the system during that period for isolating performance problem,
> without any success.
> 
> When one looks at CPU Usage, Memory Usage and Disk Usage nothing
> changes between 2:55PM and (3:00PM-4:00PM). I kooked at task mgr,  no
> new processes. I have looked at Windows scheduler, Oracle dbms_job.
> Nothing is running between 3:00PM-4:00PM. I have no clue why system
> becomes so slow in that period. I was hoping that some job starts at
> that time, but cannot find any. Any ideas for troubleshooting will be
> appreciated.
> 

Take one query where the performance difference is significant and trace 
it using SLQ trace outside and inside the bad period. You will find the 
resource causing the difference in the tracefile.

Jan
