I think you got yourself a bug there... Here's what I found (Fedora Linux 32-bit x86):
1> log_archive_dest_1 = 'location=/mypath' works as expected. 2> If I do ALTER SYSTEM ... SCOPE=both for: ----log_archive_dest_1='' ----db_recovery_file_dest='/mypath' then SELECT DEST_NAME, DESTINATION FROM V$ARCHIVE_DEST, I get: log_archive_dest_1 is empty show parameter log_archive_dest_1 is empty3> If I *RESTART* the instance and then SELECT DEST_NAME, DESTINATION FROM V$ARCHIVE_DEST, I get:
log_archive_dest_1 = $ORACLE_HOME/dbs/arch show parameter log_archive_dest_1 is still emptyGeez, that's a pretty basic QA test. Doesn't Oracle test ANYTHING anymore? :)
--Roby On Aug 18, 2007, at 7:16 PM, Roby Sherman wrote:
Hmmmm... Not seeing that on linux... Although, standby_archive_dest seems to be defaulting to that location... interesting... Does your database think its somehow running Data Guard?What does v$archive_dest show? On Aug 18, 2007, at 5:29 PM, Robert Freeman wrote:Any of you fine people install 11g yet and find that your new 11g database was creating archived redo logs in $ORACLE_HOME/dbs?? I've got a database that I created with the DBCA that is doing just that, and I'll be darned ifI can figure out why. RF Robert G. Freeman Oracle Consultant/DBA/Author Principal Engineer/Team Manager The Church of Jesus Christ of Latter-Day Saints Father of Five, Husband of One, Author of various geeky computer titles from Osborne/McGraw Hill (Oracle Press)Oracle Database 11g New Features Now Available for Pre-sales on Amazon.com!BLOG: http://robertgfreeman.blogspot.com/ Sig V1.2 -- //www.freelists.org/webpage/oracle-l
-- //www.freelists.org/webpage/oracle-l