Aychin's Oracle RDBMS Blog

Only for Advanced level Professionals

Monthly Archives: January 2011

Renaming ASM Listener in 11gR2

HP-UX, Oralce 11g 11.2.0.1.0, Grid Infrastructure, Oracle Restart


After renaming ASM listener in Grid Infrastructure Oracle Restart mode, the dependency of the ora.asm resource not updated by new listener resource, even if You use netca tool.

For example, after renaming the listener from default LISTENER to ASM_LISTENER using netca, the new resource ora.ASM_LISTENER.lsnr is successfully created and started but, when we check ASM config through srvctl we see

bash$ srvctl config asm
ASM home: /home/grid/product/11gR2
ASM listener was not found
PRCA-1032 : ASM listener LISTENER does not exist
Spfile: +DATA/asm/asmparameterfile/registry.237.345639401
ASM diskgroup discovery string:

When trying to modify listener through srvctl it returns next message:

bash$ srvctl modify asm -l ASM_LISTENER
PRCA-1032 : ASM listener LISTENER does not exist

Checking OLR entry for ora.asm resource, using “strings host123.olr  | grep ora.asm” command, will show that START_DEPENDENCIES=hard(ora.cssd) weak(ora.LISTENER.lsnr), so we need to change it manually to new listener resource name, use crsctl:

bash$ crsctl modify resource ora.asm -attr START_DEPENDENCIES="hard(ora.cssd) weak(ora.ASM_LISTENER.lsnr)"

after this modification everything will be ok

bash$ srvctl config asm
ASM home: /home/grid/product/11gR2
ASM listener: ASM_LISTENER
Spfile: +DATA/asm/asmparameterfile/registry.237.345639401
ASM diskgroup discovery string:

I think it is bug because it must be done automatically when we use netca tool, and I hope it will be solved in the near releases.


(c) Aychin Gasimov, 01/2011, Azerbaijan Republic