RE: db_file_multiblock_read_count
Date: Mon, 29 Sep 2008 16:53:33 -0700
Message-ID: <B47109E95A4F8C4AB42CC4D4169D997B14620B1AA3@ecsrm01.ecwise.local>
Hi Allen,
Here is how I know that I'm being ignored.
SQL> select isdefault from v$parameter where name = 'db_file_multiblock_read_count';
ISDEFAULT
FALSE
- So, 124 is not my default. I'll set it to some other value - any value. 1* alter system set db_file_multiblock_read_count = 8 scope=memory sid = 'my_sid' SQL> /
SQL> show parameter db_file_multiblock_read_count
NAME TYPE VALUESQL> alter system reset db_file_multiblock_read_count scope=memory sid = 'my_sid ';
------------------------------------ ----------- ------------------------------
db_file_multiblock_read_count integer 8
System altered.
SQL> show parameter db_file_multiblock_read_count
NAME TYPE VALUESQL> select isdefault from v$parameter where name = 'db_file_multiblock_read_count';
------------------------------------ ----------- ------------------------------
db_file_multiblock_read_count integer 8
ISDEFAULT
FALSE I can set it to what ever I want. I just haven't succeeded in UN SETTING it.
Thank you for the idea though.
-Claudia
-----Original Message-----
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.
Regards,
Brandon
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Sep 29 2008 - 18:53:33 CDT