RE: Unsetting init.ora parameter (WAS: db_file_multiblock_read_count causing...)
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 21 Dec 2006 11:43:08 -0600
Yup! Thanks Brandon and Nigel. Now that I have a 10g DVD loaded
locally, I can finally See The Light to my overly-simple question.
And as a bonus, I realize that in Crisis Mode, I would probably want a
local copy of the docs anyway, in case the Internet or tahiti wasn't
available.
Thanks! Merry Christmas!
Rich
-----Original Message-----
From: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx]
Sent: Thursday, December 21, 2006 11:07 AM
To: Jesse, Rich; oracle-l@xxxxxxxxxxxxx
Subject: RE: Unsetting init.ora parameter (WAS:
db_file_multiblock_read_count causing...)
I know you can reset it in the spfile with the following syntax:
alter system reset db_file_multiblock_read_count scope=spfile sid='*';
But, then I ran the following test:
SQL> show parameter multiblock
NAME TYPE VALUE
------------------------------------ -----------
------------------------------
db_file_multiblock_read_count integer 128 <--(this was
the "unset" value that Oracle set on its own at startup)
SQL> alter system set db_file_multiblock_read_count=64; <--(I changed
it to a hardcoded value of 64)
System altered.
SQL> alter system reset db_file_multiblock_read_count scope=memory
sid='baantst1';
System altered.
The above command completes successfully, but below you can see the
parameter is still set to 64, so it doesn't appear to have had the
desired affect of forcing Oracle to dynamically calculate its own value.
SQL> show parameter multi
NAME TYPE VALUE
------------------------------------ -----------
------------------------------
db_file_multiblock_read_count integer 64
Regards,
Brandon
--
//www.freelists.org/webpage/oracle-l
Other related posts:
