Register listeners with the Clusterware to startup automatically
Register other listeners with the Clusterware to startup automatically with Oracle Restart startup:
-- Mandatory info(listener name, port no) will get from Listener.ora file .
# vi /u01/app/grid/product/12.2.0/grid/network/admin/listener.ora
--Use the srvctl add listener command with the following syntax:
--log in as grid user
srvctl add listener [-l listener_name] [-p endpoints] [-s] [-o Oracle_home]
Option Description:
-l listener_name
-p endpoints
-s Skip checking for port conflicts with the supplied endpoints
-o Oracle_home
(Oracle home for the listener. If omitted, the Oracle Grid Infrastructure home is assumed)
$srvctl add listener -l <listener_name> -s -p <port no>
--To Start the same listener:
$srvctl start listener -l <Listener_name>
-- To config under crsctl status
$ srvctl config listener -l <listener_name>
--Now above listener will comes under crsctl status.
$ crsctl status res -t
-- Mandatory info(listener name, port no) will get from Listener.ora file .
# vi /u01/app/grid/product/12.2.0/grid/network/admin/listener.ora
--Use the srvctl add listener command with the following syntax:
--log in as grid user
srvctl add listener [-l listener_name] [-p endpoints] [-s] [-o Oracle_home]
Option Description:
-l listener_name
-p endpoints
-s Skip checking for port conflicts with the supplied endpoints
-o Oracle_home
(Oracle home for the listener. If omitted, the Oracle Grid Infrastructure home is assumed)
$srvctl add listener -l <listener_name> -s -p <port no>
--To Start the same listener:
$srvctl start listener -l <Listener_name>
-- To config under crsctl status
$ srvctl config listener -l <listener_name>
--Now above listener will comes under crsctl status.
$ crsctl status res -t
Comments
Post a Comment