Hi Pete!I am indeed using an spfile, but IMO for a parameter to be effective data guard needs to do the alter system set ... scope=both, otherwise I'd have to bounce the instance. Interesting point though, I'll have a look at v$spparameter to see if the situation is the same there.
TA, Martin Pete Sharman wrote:
Are you by chance using an SPFILE, in which case the relevant view is V$SPPARAMETER?Pete"Controlling developers is like herding cats." Kevin Loney, Oracle DBA Handbook"Oh no, it's not, it's much harder than that!" Bruce Pihlamae, long term Oracle DBA*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Jason Heinrich*Sent:* Saturday, 1 March 2008 2:59 AM *To:* development@xxxxxxxxxxxxxxxxx *Cc:* Oracle-L@xxxxxxxxxxxxx *Subject:* Re: Data Guard Broker 10.2.0.3 and log_archive_dest_nDo you have the same problem if you do a "show parameter log_archive_dest" in sqlplus?On 2/29/08, *Martin Bach* <development@xxxxxxxxxxxxxxxxx <mailto:development@xxxxxxxxxxxxxxxxx>> wrote:However, one thing is quite odd: in the databases' v$parameter views on primary and standby I don't find a value for log_archive_dest_n. Here you'd normally see a value similar to "service=myServiceDescriptor LGWR ASYNC valid_for(....." but not in my case. I know the settings are working (show configuration in DGMGRL) but that's still quite surprising. I also see lines beginning with "alter system set log_archive_dest_2=..." but why don't they appear in v$parameter? I have done a quick search on Metalink but did not find anything related to this feature. -- Jason Heinrich
-- //www.freelists.org/webpage/oracle-l