Home » Server Options » Data Guard » Data Guard on RAC (9i)
Data Guard on RAC [message #450603] Thu, 08 April 2010 04:48 Go to next message
maoro
Messages: 312
Registered: May 2005
Senior Member
hello
when setting up data guard, if the primary clustered database is already in archive log mode,
is there a need to restart both cluster instances when we update the spfile parameters for data guard ?
or we can simply add the data guard parameters to the spfile while both cluster instances are online ?

thank you
Re: Data Guard on RAC [message #451100 is a reply to message #450603] Mon, 12 April 2010 07:56 Go to previous messageGo to next message
babuknb
Messages: 1734
Registered: December 2005
Location: NJ
Senior Member

>>is there a need to restart both cluster instances when we update the spfile parameters for data guard ?

Yes
Re: Data Guard on RAC [message #451110 is a reply to message #451100] Mon, 12 April 2010 09:50 Go to previous messageGo to next message
maoro
Messages: 312
Registered: May 2005
Senior Member
thanks for help
but i am really getting confused since another post on oracle forums says no need to
http://forums.oracle.com/forums/message.jspa?messageID=4218940#4218940
please clarify if possible
thanks
Re: Data Guard on RAC [message #451130 is a reply to message #451110] Mon, 12 April 2010 11:09 Go to previous messageGo to next message
babuknb
Messages: 1734
Registered: December 2005
Location: NJ
Senior Member

Quote:
if the primary clustered database is already in archive log mode


  1* select name, ISSYS_MODIFIABLE from v$parameter where name like '%fal%'
SQL> /

NAME                                     ISSYS_MOD
---------------------------------------- ---------
fal_client                               IMMEDIATE
fal_server                               IMMEDIATE

SQL> select name, ISSYS_MODIFIABLE from v$parameter where name like '%standby%';

NAME                                     ISSYS_MOD
---------------------------------------- ---------
standby_archive_dest                     IMMEDIATE
standby_file_management                  IMMEDIATE

SQL> select name, ISSYS_MODIFIABLE from v$parameter where name like '%log_archive%';

NAME                                     ISSYS_MOD
---------------------------------------- ---------
log_archive_config                       IMMEDIATE
log_archive_start                        FALSE
log_archive_dest                         IMMEDIATE
log_archive_duplex_dest                  IMMEDIATE
log_archive_dest_1                       IMMEDIATE
log_archive_dest_2                       IMMEDIATE
log_archive_dest_3                       IMMEDIATE
log_archive_dest_4                       IMMEDIATE
log_archive_dest_5                       IMMEDIATE
log_archive_dest_6                       IMMEDIATE
log_archive_dest_7                       IMMEDIATE

NAME                                     ISSYS_MOD
---------------------------------------- ---------
log_archive_dest_8                       IMMEDIATE
log_archive_dest_9                       IMMEDIATE
log_archive_dest_10                      IMMEDIATE
log_archive_dest_state_1                 IMMEDIATE
log_archive_dest_state_2                 IMMEDIATE
log_archive_dest_state_3                 IMMEDIATE
log_archive_dest_state_4                 IMMEDIATE
log_archive_dest_state_5                 IMMEDIATE
log_archive_dest_state_6                 IMMEDIATE
log_archive_dest_state_7                 IMMEDIATE
log_archive_dest_state_8                 IMMEDIATE

NAME                                     ISSYS_MOD
---------------------------------------- ---------
log_archive_dest_state_9                 IMMEDIATE
log_archive_dest_state_10                IMMEDIATE
log_archive_max_processes                IMMEDIATE
log_archive_min_succeed_dest             IMMEDIATE
log_archive_trace                        IMMEDIATE
log_archive_local_first                  IMMEDIATE
log_archive_format                       FALSE

29 rows selected.

SQL> select name, ISSYS_MODIFIABLE from v$parameter where name like '%remode%';

no rows selected

SQL> select name, ISSYS_MODIFIABLE from v$parameter where name like '%remote%';

NAME                                     ISSYS_MOD
---------------------------------------- ---------
remote_archive_enable                    FALSE
remote_os_authent                        FALSE
remote_os_roles                          FALSE
remote_login_passwordfile                FALSE
remote_listener                          IMMEDIATE
remote_dependencies_mode                 IMMEDIATE

6 rows selected.

SQL>


Quote:
is there a need to restart both cluster instances when we update the spfile parameters for data guard ?


As per your update archive log mode already enabled and once again I had double check data guard related parameter.

It's dynamic only; so no need to bounce production database.

Thanks for catching this.

Babu
Re: Data Guard on RAC [message #451203 is a reply to message #450603] Tue, 13 April 2010 02:07 Go to previous message
maoro
Messages: 312
Registered: May 2005
Senior Member
Many thanks
Previous Topic: Unable to issue " show configuration " while setting up the data broker setup
Next Topic: Data guard Configuration
Goto Forum:
  


Current Time: Wed May 27 18:31:28 CDT 2020