Dataguard. log_archives_dest_n reconfiguration
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 9 of 9

Thread: Dataguard. log_archives_dest_n reconfiguration

  1. #1
    Join Date
    Jun 2009
    Posts
    40

    Dataguard. log_archives_dest_n reconfiguration

    Hello,

    - The Primary site is a RAC with two servers.
    - The Standby is a logical Standby database with two servers as RAC as well.
    - Dataguard broker is used
    - Both servers of the Primary have one log_archive_dest parameter that is wronly configured because it is pointing to another IP of a Standby server that is not used anymore.

    I think I can delete it by running the following in both Primary servers:

    SQL> alter system set log_archive_dest_4='' scope=memory sid='*';

    But, does the database keep the update after, for example, rebooting the instances?

    Thank you!

  2. #2
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    No. to keep the update, if you are using spfile scope=both and if you are using pfile then edit the pfile.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  3. #3
    Join Date
    Jun 2009
    Posts
    40
    Thanks Vijay

    I've found that there is another way with scope=spfile and it keeps the change as when you use scop=both.

    What is the difference between them?

  4. #4
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    scope=both updates the dynamic parameter in both memory & spfile so the changes will reflect immediately.

    scope=spfile updates only in spfile so the changes will reflect only after db bounce.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  5. #5
    Join Date
    Jun 2009
    Posts
    40
    Thanks, that is the answer

    I've been told by another Oracle expert to change the log_archive_dest_4 parameter of the Primary site by scope=spfile.

    Do you know why to use this, instead of scope=both, since I have to reboot the instance to take the change?

  6. #6
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    I have no idea why he suggested that.

    log_archive_dest_n parameter is modifiable, so if you want the change takes effect immediately and persists after the database shutdown and start up you must use scope=both

    scope=spfile will be used for static parameters. changes will effect after shutdown and start up the database only.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  7. #7
    Join Date
    Jun 2009
    Posts
    40
    could it be due to the broker??

  8. #8
    Join Date
    Mar 2006
    Location
    Charlotte, NC
    Posts
    865
    I never used broker. No idea. But I believe broker is nothing to do with setting log_archive_dest parameter.

    Thanks,
    Vijay Tummala

    Try hard to get what you like OR you will be forced to like what you get.

  9. #9
    Join Date
    Jun 2009
    Posts
    40
    The broker configures the log_archive_dest parameters by itself, I've seen it in this case.
    But I don't know if a reboot is required because of this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width