Home » Server Options » RAC & Failsafe » running the listener from ASM Home
running the listener from ASM Home [message #443852] Wed, 17 February 2010 12:01 Go to next message
siriravi
Messages: 2
Registered: February 2010
Junior Member
According to some Oracle documents, it's good practice to run the listener from ASM_HOME instead of ORACLE_HOME. I'm wondering what .profile PATH changes are necessary to make sure that listener starts up from ASM home instead of ORACLE_HOME and not mess up database startup and shutdown?
Re: running the listener from ASM Home [message #443855 is a reply to message #443852] Wed, 17 February 2010 12:09 Go to previous messageGo to next message
John Watson
Messages: 6396
Registered: January 2010
Location: Global Village
Senior Member
If your listener is registered in the cluster registry correctly, which it will be if you created it with netca running from the ASM home, the Clusterware will start it from the correct home, no problem. Your .profile is not relevant to the Clusterware daemons' environment.
Re: running the listener from ASM Home [message #444119 is a reply to message #443855] Thu, 18 February 2010 14:32 Go to previous messageGo to next message
siriravi
Messages: 2
Registered: February 2010
Junior Member
I actually configured listener through netca running from Oracle Home. I have separate homes for ASM and Oracle. Now I need to make the listener run from ASM_HOME instead of the ORACLE_HOME.

[Updated on: Thu, 18 February 2010 14:34]

Report message to a moderator

Re: running the listener from ASM Home [message #444122 is a reply to message #444119] Thu, 18 February 2010 14:49 Go to previous messageGo to next message
BlackSwan
Messages: 24905
Registered: January 2009
Senior Member
It would be helpful if you followed Posting Guidelines - http://www.orafaq.com/forum/t/88153/0/
Re: running the listener from ASM Home [message #444127 is a reply to message #444122] Thu, 18 February 2010 15:23 Go to previous message
John Watson
Messages: 6396
Registered: January 2010
Location: Global Village
Senior Member
I would use netca running from the RDBMS home to remove the listeners you have at the moment, then connect to the ASM home and use netca to create new listeners. Check the OCR afterwards (with crs_stat -p) and you'll see that the listeners are on automatic start, with appropriate dependencies.
Alternatively, you could use srvctl or crs_unregister to remove the listeners and register new ones, but I have found that netca is the best tool to make sure that the configuration files are kept synchronized with the OCR.
Previous Topic: Oracle Application split configuration
Next Topic: Moving control file
Goto Forum:
  


Current Time: Mon Sep 26 16:17:11 CDT 2016

Total time taken to generate the page: 0.10205 seconds