Oracle Database Appliance has quite a lot of nice features, but when looking into the documentation, at least one thing is missing. How to configure multiple listeners? Odacli apparently doesn’t know what’s a listener. Let’s find out how to add new ones.<\/p>\n
Everything should be done using odacli on ODA, but unfortunately odacli has no commands for configuring listeners: <\/p>\n
One could tell me that configuring a listener is easy, you just have to describe it into the listener.ora file, for example:<\/p>\n … and start it with: But if it works fine, it’s not the best way to do that. Why? Simply because it will not survive a reboot.<\/p>\n ODA makes use of Grid Infrastructure for its default listener on port 1521. The listener is an Oracle service running in Grid Infrastructure, so additional listeners should be declared in the Grid Infrastructure using srvctl. This is an example to configure a new listener on port 1576:<\/p>\n The new listener is running fine, and the listener.ora has been completed with this new item:<\/p>\n For sure, configuring a listener on a particular port is only possible if this port is not in use.<\/p>\n If you want to remove a listener, you just need to remove the service from Grid Infrastructure: Obviously, if you plan to remove a listener, please make sure that no database is using it prior removing it.<\/p>\n Since 12c, a new LREG process in the instance is doing the registration of the database in a listener. Previously, this job was done by PMON process. The default behavior is to register the instance in the standard listener on 1521. If you want to configure your database with the new listener you just created with srvctl, configure the local_listener parameter:<\/p>\n No need to reboot anything.<\/p>\n You may think about removing the standard listener on port 1521. But I wouldn’t do that. I think it’s better to keep this default one, even if none of your databases are using it. It could later cause troubles when patching or configuring something else on your ODA.<\/p>\n The listener management with odacli could come one day, but for now (19.9 and before) you still have to configure it using Grid Infrastructure. It’s quite easy and pretty straightforward if you do it the proper way.<\/p>\n","protected":false},"excerpt":{"rendered":" Introduction Oracle Database Appliance has quite a lot of nice features, but when looking into the documentation, at least one thing is missing. How to configure multiple listeners? Odacli apparently doesn’t know what’s a listener. Let’s find out how to add new ones. odacli Everything should be done using odacli on ODA, but unfortunately odacli […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198,199,59],"tags":[2265,2266,2267,2268,2269,2270,79,2271,2272,365,2273,1330,1331,1332,1697,1698,1699],"type_dbi":[],"class_list":["post-15847","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","category-database-management","category-hardware-storage","category-oracle","tag-add-a-listener","tag-additional-listener","tag-configure-a-listener","tag-listener-management","tag-listener-ora","tag-lsnrctl","tag-oda","tag-odacli-add-listener","tag-odacli-configure-listener","tag-oracle-database-appliance","tag-srvctl","tag-x7-2ha","tag-x7-2m","tag-x7-2s","tag-x8-2ha","tag-x8-2m","tag-x8-2s"],"acf":[],"yoast_head":"\nodacli -h | grep listener<\/strong>
\nnothing!<\/em>
\n<\/code><\/p>\nThe wrong way to configure a listener<\/h2>\n
echo \"DBI_LSN=(DESCRIPTION_LIST=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=oda-dbi-test)(PORT=1576))))\" >> $ORACLE_HOME\/network\/admin\/listener.ora<\/strong><\/code><\/p>\n
\nlsnrctl start DBI_LSN<\/strong><\/code><\/p>\nA better way to configure a listener: through Grid Intrastructure<\/h2>\n
su - grid
\nwhich srvctl<\/strong>
\n\/u01\/app\/19.0.0.0\/oracle\/bin\/srvctl
\nsrvctl add listener -listener DBI_LSN -endpoints 1576
\nsrvctl config listener -listener DBI_LSN<\/strong>
\nName: DBI_LSN
\nType: Database Listener
\nNetwork: 1, Owner: grid
\nHome:
\nEnd points: TCP:1576
\nListener is enabled.
\nListener is individually enabled on nodes:
\nListener is individually disabled on nodes:
\nsrvctl start listener -listener DBI_LSN
\nps -ef | grep tnslsn | grep DBI<\/strong>
\noracle 71530 1 0 12:41 ? 00:00:00 \/u01\/app\/19.0.0.0\/oracle\/bin\/tnslsnr DBI_LSN -no_crs_notify -inherit
\n<\/code><\/p>\ncat \/u01\/app\/19.0.0.0\/oracle\/network\/admin\/listener.ora | grep DBI<\/strong>
\nDBI_LSN=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=DBI_LSN)))) # line added by Agent
\nENABLE_GLOBAL_DYNAMIC_ENDPOINT_DBI_LSN=ON # line added by Agent
\nVALID_NODE_CHECKING_REGISTRATION_DBI_LSN=SUBNET # line added by Agent
\n<\/code><\/p>\nRemoving a listener<\/h2>\n
\nsu - grid
\nsrvctl stop listener -listener DBI_LSN
\nsrvctl remove listener -listener DBI_LSN
\nps -ef | grep tnslsn | grep DBI<\/strong>
\nno more listener DBI_LSN running<\/em>
\ncat \/u01\/app\/19.0.0.0\/oracle\/network\/admin\/listener.ora | grep DBI<\/strong>
\nno more configuration in the listener.ora file<\/em>
\n<\/code><\/p>\nHow to use this listener for my database<\/h2>\n
su - oracle
\n. oraenv <<< DBTEST
\nsqlplus \/ as sysdba
\nalter system set local_listener='(ADDRESS=(PROTOCOL=TCP)(HOST=oda-dbi-test)(PORT=1576))' scope=both;
\nalter system register;
\nexit;<\/strong><\/code><\/p>\nWhat about standard 1521 listener?<\/h2>\n
Conclusion<\/h2>\n