Remote_listener Getting Reset To Blank After Cluster Startup
APPLIES TO:
Oracle Database – Enterprise Edition – Version 12.2.0.1 to 19.3.0.0.0 [Release 12.2 to 18]
Information in this document applies to any platform.
SYMPTOMS
users get error while connecting to database
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
remote_listener value got reset to blank after db node patching on all databases of the cluster causing databases not able to connect from outside, and databases are not getting registered with scan_listeners.
crsd_oraagent_oracle.trc inside <oracle base>/diag/crs/<HOSTNAME>/crs/trace location indicate following messages2019-05-11 19:41:49.764 : USRTHRD:3059689216: {2:49138:41584} LsnrRegThd::setRemoteListener 391 tmpSet endp:<scan name>:<PORT>
2019-05-11 19:41:49.764 : USRTHRD:3059689216: {2:49138:41584} LsnrRegThd::setRemoteListener 440 skip remote listener registration m_runRegRLUpdate:0 isForceRemoteListenerSet:0 isRemoteListenerSet:1
2019-05-11 19:41:49.774 : USRTHRD:3059689216: {2:49138:41584} ORA-01405: fetched column value is NULL
CHANGES
CAUSE
This is due to unpublished Bug 29637215 – FAEOPS: SHELL DB DOESN’T HAVE REMOTE_LISTENER VALUE WITH GRID 19.1.0.3
SOLUTION
Bug 29637215 fixed in future release. Apply interim fix 29637215, if available for your platform and Oracle version.
If no patch exists for your version, please contact Oracle Support for a backport request
As a workaround,
Manually update the remote_listener values every time bounce the instances from this cluster.
alter system set remote_listener=’racscan.com:1521′ scope=both sid=’*’;
