-
Listener not working in one of the servers of the Standby site
Hello,
The system is a RAC with two servers working as Primary site, and two servers working as Standby site.
Both servers of the Primary site are sending redo logs to one of the servers of the Standby site. The other server of the Standby site is not receiving any redo log.
I have checked the listener.ora and the tnsnames.ora files of the server that is not receiving and it is well configured comparing it with the server that is receiving the redo logs.
If I check the status of the listener: lsnrctl status listener_
Both of the Standby servers look fine.
But if I connect directly to the database...
In the 1st server of the Standby, the IP appears:
SQL> show parameter listener
NAME TYPE VALUE
-------------------------------------------------------------------------
local_listener string (ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.xxx)(PORT = xxxx))
remote_listener string LISTENERS_VSDB
Nevertheless, in the second server of the Standby site, the one that is not receiving the redo logs, the IP does not appear:
SQL> show parameter listener
NAME TYPE VALUE
----------------------------------------------------------------------
local_listener string (ADDRESS = (PROTOCOL = TCP)(HOST = )(PORT = xxxx))
remote_listener string LISTENERS_VSDB
I have found the following to reload the listener:
Oracle# lsnrctl reload listener_`hostname`
Oracle# lsnrctl reload listener_standby
Has anyone tried this? Did it work? It can be run without affecting the sytem, Dataguard, replication..., right?
If you have another idea to fix this, let me know please.
Thank you
Last edited by lulon; 10-31-2009 at 07:12 AM.
-
What do you see when doing... lsnrctl status listener_standby ?
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
-
In the first server of the Standby site:
#lsnrctl status listener_standby
LSNRCTL for Solaris: Version 10.1.0.4.0 - Production on dd-mm-yyyy hh:mm:ss
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=IP_first_server)(PORT=xxxx)))
STATUS of the LISTENER
------------------------
Alias listener_standby
Version TNSLSNR for Solaris: Version 10.1.0.4.0 - Production
Start Date dd-mm-yyyy hh:mm:ss
Uptime xx days yy hr. zz min. vv sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/product/10.1.0/db_1/network/admin/listener.ora
Listener Log File /opt/oracle/product/10.1.0/db_1/network/log/listener_standby.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=IP_first_server)(PORT=xxxx)))
Services Summary...
Service "DB1" has 1 instance(s).
Instance "DB1", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
In the second server of the Standby site:
#lsnrctl status listener_standby
LSNRCTL for Solaris: Version 10.1.0.4.0 - Production on dd-mm-yyyy hh:mm:ss
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=IP_second_server)(PORT=xxxx)))
STATUS of the LISTENER
------------------------
Alias listener_standby
Version TNSLSNR for Solaris: Version 10.1.0.4.0 - Production
Start Date dd-mm-yyyy hh:mm:ss
Uptime xx days yy hr. zz min. vv sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/product/10.1.0/db_1/network/admin/listener.ora
Listener Log File /opt/oracle/product/10.1.0/db_1/network/log/listener_standby.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=IP_second_server)(PORT=xxxx)))
Services Summary...
Service "DB2" has 1 instance(s).
Instance "DB2", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
-
Seems listener are up and running on both nodes of standby,check the alert log on 2nd server of standby for any errors and make sure the password for sys is same as that of the primary and you have a passwordfile on 2nd node of the standby and make sure you have proper tns entries on primary for the standby .
can you connect to both the standby server through sqlplus?
-
Thanks Rayyah.
There are no errors in the alert log of the second server of the Standby site. It only does not receive redo logs from the Primary.
The sys passwords are the same and I can connect from any server to every server of the Primary and Standby.
How can I check the passwordfile in the 2nd node of the Standby?
How can I check that the Primary server would send redo logs to the 2nd node of the Standby if the 1st node fails?
Thanks
-
I've just checked that when I connect from the Primary site to the 2nd server by SQL I can see in the log the conexion is right:
29-OCT-2009 19:12:25 * (CONNECT_DATA=(SERVER=DEDICATED)(SID=DB2)(CID=(PROGRAM=sqlplus@server1b)(HOST=server1b)(USER=root))) * (ADDRESS=(PROTOCOL=tcp)(HOST=IP_2nd_server_Primary)(PORT=xxxx)) * establish * DB2 * 0
Last edited by lulon; 10-30-2009 at 06:11 AM.
-
How can I check that if the 1st server of the Standby fails, then the Primary servers will send the redo logs to the 2nd Standby server?
-
RTFM-http://youngcow.net/doc/oracle10g/server.102/b14239/rac_support.htm
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|