Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Switchover succeeds but observer stops. Only happens one way.

user2638923Feb 18 2013 — edited Feb 19 2013
Hello

I have a problem with the following setup:

Oracle Enterprise Edition, version - 11.2.0.3
OS - RHEL6 64bit

Configuration:

2x hosts.
2x databases on each host.
each database forms 1/2 of a PRIMARY + PHYSICAL STANDBY 'pair'.
Mode = Maximum Availability.
FSFO is setup using a third host for the observer location.
Grid Control 11g


This setup is working fine on our acceptance test hosts (same software, spec etc.) and is also working fine for one of the two db pairs on these machines. However, for one of the pairs, a switchover one way will stop the observer and it does not restart. i.e.

we have host A and host B which have database 'pairs' for
SOA
In House db

Primary db switchover to result
soadba soadbb success
soadbb soadba success
inhousea inhouseb switchover succeeds, inhousea is reisnstated as physical standby but observer stops
inhouseb inhousea success


The contents of the observer log is:

Observer started
[W000 02/18 14:10:26.32] Observer started.
[P003 02/18 14:13:25.83] Authentication failed.
Observer stopped


This behaviour is consistent whichever way I invoke the switchover e.g.
DGMGRL on host A
DGMGRL on host B
Grid Control

I can sqlplus from everywhere to everywhere that I can think of using the range of connect identifiers I would expect:
@inhousea as sysdba
@inhousea_dgmgrl as sysdba
@inhousea_dgmgrl.acme.com as sysdba

Credentials are stored in Grid Control for hosts and dbs and all test okay. Static registration with default Grid listener seems to be working.



Any ideas where I should look next? I don't believe it is a typo, and in fact have just copied the 2xlistener (GRID and DB HOME) and 1xtnsnames.ora file from host A to host B so is there some other area of connectivity I'm not accounting for. Observer location on the third host is used by both the inhouse and the soa configurations so the problem is not with the ORACLE_HOME in use there (or at least the ORACLE_HOME on the third host can do the job).


Any help much appreciated as I'm scratching my head over this.



thanks
Mark
This post has been answered by CKPT on Feb 18 2013
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 19 2013
Added on Feb 18 2013
4 comments
2,586 views