RE: db_file_multiblock_read_count

  • From: Claudia Zeiler <czeiler@xxxxxxxxxx>
  • To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
  • Date: Mon, 29 Sep 2008 16:57:47 -0700

One thing, I haven't done the bounce. I thought that this was a dynamic 
parameter.

I will get permission to bounce this db in a sec.

Btw, Allen, it is a posting from you in 2006 that I was following.  I see that 
you had the same problem the.  I guess that that makes you the expert on the 
topic.
-Claudia


-----Original Message-----
From: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx]
Sent: Monday, September 29, 2008 4:47 PM
To: Claudia Zeiler; oracle-l@xxxxxxxxxxxxx
Subject: 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

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


Other related posts: