RE: db_file_multiblock_read_count

How do you know you're "being ignored"?  Just because it shows a value
of 128 doesn't mean your "reset" isn't working - maybe 128 is the value
that Oracle is coming up with?  Try this:

select isdefault from v$parameter where name =
'db_file_multiblock_read_count';

If it's not the default, you might want to try this:

alter system reset db_file_multiblock_read_count scope=spfile sid = '*';

Then bounce your instance and check again.

Regards,
Brandon

--
http://www.freelists.org/webpage/oracle-l

Other related posts: