| Urgent please! standby client tns entry issue [message #115981] |
Fri, 15 April 2005 12:36  |
sheela
Messages: 66
Registered: March 2002
|
Member |
|
|
Hi,
We are running oracle 9i (9.2.0.6.0) on solaris. I have configured a physical standby using data guard manager (using OEM). It is all configured correctly and also switching between primary and standby sites too. We are going live tonight.
here's the tnsnames.ora client entry :
db.world = ( DESCRIPTION=
(FAILOVER=ON)
(LOAD_BALANCE=OFF)
(ADDRESS=(PROTOCOL=tcp)(PORT=1521)HOST=primhost))
(ADDRESS=(PROTOCOL=tcp)(PORT=1521)(HOST=stdbyhost))
(CONNECT_DATA=(SID=a4sjcprd))
)
However I get a connectivity problem when a 'switchover' takes place and when the primary site becomes standby and the standby site becomes primary:
I tried using sqlplus to connect after the switchover (where the primhost is now the standby host and the stbyhost is the primary host) and I get the following error:
"
ERROR:
ORA-O1033 Oracle initialization or shutdown in progress"
For some reason instead of ignoring the standby site (primhost) and connecting to the primary host (which is now 'stdbyhost') it still tries to connect to the primhost thinking it is still acting as primary even though after the switchover it is only a standby.
This is the article I used for the client tnsnames.ora configuration (under section "Local TNS Configuration":
http://www.cs.uwm.edu/~oracle/oracle_doc/doc/server.817/a76995/standbys.htm#30835
Thanks
|
|
|
|
| Re: Urgent please! standby client tns entry issue [message #116083 is a reply to message #115981] |
Sun, 17 April 2005 09:52  |
pscjhe
Messages: 38
Registered: April 2005
|
Member |
|
|
TAF won't apply to standby, I believe. Because standy is mounted, listener is in fact listening. You can sqlplus as sysdba into standby without problem. When your primary turns into standby, client will use TAF to "connect" to your primary, which is at "mount" stage. Hence it will not try the second entry in TAF. For RAC, since the instance is really down not at "mount" stage, so client connection is not successful, the second entry is tried.
IP failover is one way to avoid change Oracle service entry.
Without third party tool to manage IP failover, you can replace tnsnames.ora, which you may store on some shared network drive, or change tnsnames.ora locally (it is a lot more hassle). The other way is to configure a centralized Oracle Names, LDDP, OID etc. After switchover/failover, you can replace the entry for the service.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
