Anyone seen this behaviour before ?

I have a HDR pair which were working fine up until lately. The primary runs in a veritas clustered environment - secondary is standalone. Configuration is fine. However, when i recently failed over to the second node in the cluster the instance came up cleanly BUT there was a connectivity foobah between the second node and the standalone secondary hdr partner. As this is a high vis platform i immediately failed back to node 1 - the instance came online and the HDR pair connected, primary sent the latest log and both became operational simultaneously. Onstat -g dri tells me all is fine and the checkpoints are in synch. HOWEVER, this is just an illusion - nothing had been replicated since the failover. I have created dummy tables on the primary which fail to replicate and monitored row counts on heavily hit tables - nada - zip. I realise that i have no choice but to break the pair and do a restore to the secondary ( the logs have been long since copied to numerous tapes and overwritten) - Just wondering if anyone else has had a similar experience. IDS 9.30 UC1 and Solaris 8 btw

mad_villan wrote: > I have a HDR pair which were working fine up until lately. The primary > runs in a veritas clustered environment - secondary is standalone. > Configuration is fine. However, when i recently failed over to the > second node in the cluster the instance came up cleanly BUT there was > a connectivity foobah between the second node and the standalone > secondary hdr partner. > As this is a high vis platform i immediately failed back to node 1 - > the instance came online and the HDR pair connected, primary sent the > latest log and both became operational simultaneously. > Onstat -g dri tells me all is fine and the checkpoints are in synch. > HOWEVER, > this is just an illusion - nothing had been replicated since the > failover. > I have created dummy tables on the primary which fail to replicate and > monitored row counts on heavily hit tables - nada - zip. > I realise that i have no choice but to break the pair and do a restore > to the secondary ( the logs have been long since copied to numerous > tapes and overwritten) - Just wondering if anyone else has had a > similar experience. > > IDS 9.30 UC1 and Solaris 8 btw Post an onstat -g dri from both primary and secondary. What is a => connectivity foobah between the second node and the standalone secondary hdr partner. <=