You've got that wrong. DB_SEQUENTIAL_WAITS are usually index lookups,
NOT FTS.
FTS can generate sequential reads if you have chained rows, a lot of
blocks of that table already in the buffer, or a very messed up extent
strategy, else they generate scattered reads.
Do you know that your slow batch jobs suffer because of FTS or do you
merely assume that?
Chirag DBA wrote:
> Still,
>
> Well, Users are happy. but in the morning when they run large batch
> jobs, yeah couple of guys do face some problems. As per my observations
> ,highest waits were DB_SEQUENTIAL_WAITS.
>
> So have done rebuilding of indexes as Sequential reads can be high
> because of the FTS on the tables. Even for the 40GB Database, we have
> only 250 MB SGA so which I am planning to increase. In normal day
> operation no query is getting locked or taking very long to execute.
>
--
Regards
Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Sep 13 2005 - 16:45:50 CDT
