Hi,
I had to bounce my primary database which is replicated to another database
(secondary, read-only) on another box. When I bounced the primary database, it
broke the replication with secondary. when I ran onstat -g dri to check
replication status on secondary it did not show secondary (read only). It only
showed ONLINE status. So I ran onmode -d secondary <primaryserver>, this made
it back to secondary. My question is every time i bounce primary do I need to
set secondary manually?...I thought it will go back to its original
replication status after bouncing successfully.
Your responses will be greatly appreciated.
Thanks,
Sunita
↪ replying to SUNITA RAINA
SUNITA RAINA wrote:
> Hi,
>
> I had to bounce my primary database which is replicated to another database
> (secondary, read-only) on another box. When I bounced the primary database,
it
> broke the replication with secondary. when I ran onstat -g dri to check
> replication status on secondary it did not show secondary (read only). It
only
> showed ONLINE status. So I ran onmode -d secondary <primaryserver>, this made
> it back to secondary. My question is every time i bounce primary do I need to
> set secondary manually?...I thought it will go back to its original
> replication status after bouncing successfully.
>
See the description of the DR* ONCONFIG file parameters in the
Administator's Guide and Reference manuals. Note that in some versions
there were disabled but were reinstated in 9.40 and later IB. These
parameters control the behavior of the secondary when it finds that the
primary has gone down and of both servers if the primary is restarted
later. There are several options, the default for which (and the only
option for versions without the DR* parameters active) is what you
witnessed, that the secondary remains a secondary and the primary comes
back online as a standalone server.
Art S. Kagel
Oninit
> Your responses will be greatly appreciated.
>
> Thanks,
> Sunita
================================================================================
===========
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.oninit.com/home/disclaimer.php
================================================================================
===========