If for whatever reason you need to add a component to the OCR, and the corresponding GUI is not cooperating, you can manually add it. This afternoon, I had to add a new node to a cluster. When I tried to add the listener on the new node, netca kept complaining about the listener already existing, when it in fact didn’t. OK, it probably had a good reason for thinking it did exist, but I couldn’t find it. I think it may be that the listener name to be registered already existed in the listener.ora file.<\/p>\n
As an alternative, I used crs_stat and crs_register to manually add them. In the case of a listener, the easiest way to is to get a cap file for another listener already in the cluster and then edit it.<\/p>\n
\r\nlinux1:oracle:tst10g2:\/home\/oracle>.\/crsstat.ksh | grep LISTEN\r\nora.linux1.LISTENER_LINUX1.lsnr ONLINE ONLINE on linux1\r\nora.linux2.LISTENER_LINUX2.lsnr ONLINE ONLINE on linux2\r\nlinux1:oracle:tst10g2:\/home\/oracle>$ORA_CRS_HOME\/bin\/crs_stat -p ora.linux1.LISTENER_LINUX1.lsnr\r\nNAME=ora.linux1.LISTENER_LINUX1.lsnr\r\nTYPE=application\r\nACTION_SCRIPT=\/u01\/app\/oracle\/product\/10.2.0\/bin\/racgwrap\r\nACTIVE_PLACEMENT=0\r\nAUTO_START=1\r\nCHECK_INTERVAL=600\r\nDESCRIPTION=CRS application for listener on node\r\nFAILOVER_DELAY=0\r\nFAILURE_INTERVAL=0\r\nFAILURE_THRESHOLD=0\r\nHOSTING_MEMBERS=linux1\r\nOPTIONAL_RESOURCES=\r\nPLACEMENT=restricted\r\nREQUIRED_RESOURCES=ora.linux1.vip\r\nRESTART_ATTEMPTS=5\r\nSCRIPT_TIMEOUT=600\r\nSTART_TIMEOUT=0\r\nSTOP_TIMEOUT=0\r\nUPTIME_THRESHOLD=7d\r\nUSR_ORA_ALERT_NAME=\r\nUSR_ORA_CHECK_TIMEOUT=0\r\nUSR_ORA_CONNECT_STR=\/ as sysdba\r\nUSR_ORA_DEBUG=0\r\nUSR_ORA_DISCONNECT=false\r\nUSR_ORA_FLAGS=\r\nUSR_ORA_IF=\r\nUSR_ORA_INST_NOT_SHUTDOWN=\r\nUSR_ORA_LANG=\r\nUSR_ORA_NETMASK=\r\nUSR_ORA_OPEN_MODE=\r\nUSR_ORA_OPI=false\r\nUSR_ORA_PFILE=\r\nUSR_ORA_PRECONNECT=none\r\nUSR_ORA_SRV=\r\nUSR_ORA_START_TIMEOUT=0\r\nUSR_ORA_STOP_MODE=immediate\r\nUSR_ORA_STOP_TIMEOUT=0\r\nUSR_ORA_VIP=\r\n\r\nlinux1:oracle:tst10g2:\/home\/oracle>\r\n<\/pre>\nTake the output of the crs_stat -p command above and add it to a file with a similar profile name, such as ora.linux3.LISTENER_LINUX3.lsnr. This file must have .cap appended to the name, i.e., ora.linux3.LISTENER_LINUX3.lsnr.cap<\/p>\n
Edit the file to change the relevant pieces (host name in this case). <\/p>\n
You can then either:<\/p>\n
1) Place the file under $ORA_CRS_HOME\/crs\/public
\n2) Place it in an arbitrary location and tell the crs_register executable where it is<\/p>\n
If you choose 1) above, then you must simply issue the following:<\/p>\n
\r\ncrs_register ora.linux3.LISTENER_LINUX3.lsnr\r\n<\/pre>\nIf you choose 2), you can issue the following:<\/p>\n
\r\ncrs_register -dir directory_where_you_put_the_cap_file ora.linux3.LISTENER_LINUX3.lsnr\r\n<\/pre>\nNotice you don’t<\/b> append the .cap to the resource name to be registered.<\/p>\n
In the case of a listener, you also must have the corresponding entry in the listener.ora on the affected node.<\/p>\n","protected":false},"excerpt":{"rendered":"
If for whatever reason you need to add a component to the OCR, and the corresponding GUI is not cooperating, you can manually add it. This afternoon, I had to add a new node to a cluster. When I tried…<\/p>\n