Date: Tue, 30 Sep 2008 01:38:30 -0400
I don't think a bounce is required. Not tested, but, try log out and login, after the reset.
I think the reset will only affect new sessions, going forward.
Consider that existing sessions may already be committed to using the existing dbfmbrc value.
Hope that helps,
From: oracle-l-bounce_at_freelists.org [oracle-l-bounce_at_freelists.org] On Behalf Of Claudia Zeiler [czeiler_at_ecwise.com] Sent: Monday, September 29, 2008 7:57 PM To: Allen, Brandon; oracle-l_at_freelists.org Subject: RE: db_file_multiblock_read_count
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.
From: Allen, Brandon [mailto:Brandon.Allen_at_OneNeck.com] Sent: Monday, September 29, 2008 4:47 PM To: Claudia Zeiler; oracle-l_at_freelists.org 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.
http://www.freelists.org/webpage/oracle-l Received on Tue Sep 30 2008 - 00:38:30 CDT