| running the listener from ASM Home [message #443852] |
Wed, 17 February 2010 12:01  |
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  |
John Watson
Messages: 8960
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 #444127 is a reply to message #444122] |
Thu, 18 February 2010 15:23 |
John Watson
Messages: 8960
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.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
