| Monitoring Full tablescans [message #193535] |
Mon, 18 September 2006 02:42  |
M.Shakeel Azeem
Messages: 226
Registered: September 2006
|
Senior Member |
|
|
SQL> select name,value
2 from v$sysstat
3 where name like 'table scans%'
4 ;
NAME VALUE
----------------------------------------------------------------
table scans (short tables) 6599797
table scans (long tables) 14003
table scans (rowid ranges) 0
table scans (cache partitions) 0
table scans (direct read) 0
SQL> show parameter db_file_multiblock_read_count
NAME TYPE VALUE
------------------------------------ ------- --------------
db_file_multiblock_read_count integer 32
should i increase db_file_multiblock_read_count and how much it is needed to be increased?
|
|
|
|
| Re: Monitoring Full tablescans [message #193558 is a reply to message #193535] |
Mon, 18 September 2006 04:47  |
JRowbottom
Messages: 5933
Registered: June 2006
Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
No you shouldn't increase or decrease db_file_multiblock_read_count.
The value of that parameter should mirror the actual physical multiblock read count of the disks that your database is on.
You can gether System Statistics to measure what this value is if you don't know it.
On a related note, Tuning your system by changing the init-ora parameters and seeing what happens is probably the worst way of going about it.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
