Unsolved

This post is more than 5 years old

5 Posts

632

February 12th, 2009 04:00

Data Source shows Warning after failover

We have Automated Availability Manager 5.1.2 and Co-Standby Server AAdvanced clustering an Oracle 9i database on two servers running Windows 2000 Advanced Server. Last week the power spiked in the main dataroom taking out the UPS at the same time. AAM failed over to the secondary server, but since then the data sources are showing up as "Warning" and we can not relocate back onto the primary server.

The data source status is as follows:
--------------------
Feb 2, 2009 12:01:34 PM
Details for mirror volume volume: rgr01dso01

Mounted Drive: E
File System: NTFS
Total Space: 440,225,177,600 Bytes
Available Space: 128,580,841,472 Bytes

Mirror Link: Up

View from local host "server2"
---------------------------------
Local Mirror Status : Online
Source Member : Local
Local Member State : Healthy
Remote Member State : Broken

View from remote host "server1"
---------------------------------
Local Mirror Status : Offline
Source Member : Not Applicable
Local Member State : Broken
Remote Member State : Broken


Volume Info: rgr01dso01: Online; Dispatcher: Not Active, Not Suspended
Member Server Disk Sig Offset Length State
1 server1 19A2813B7 7E00 667F772400 100 Broken
2 server2 767D1C13 7E00 668B3B5400 100 Healthy

-----------------------
I only got limited training on using AAM, which didn't include fixing mirroring problems like this. When we selected server2 datasource, the button "Resynchronise using selected node's drive as the source" becomes active, but the help system doesn't actually mention its exsistence!

Can someone confirm if that is how we can restart the mirror and so relocate back to the primary server.

TIA
Tim

262 Posts

February 12th, 2009 06:00

Hi,

Please execute the restart mirror because it is status of Broken.

Please make the data source again if you cannot do the restart mirror.

5 Posts

February 17th, 2009 00:00

Restarting the mirror did work and it was the "Resynchronise using selected node's drive as the source" button that restarted the mirror on each data source.

Thanks for guidance.
No Events found!

Top