《连续两次REMOTE_LISTENER 设置为null导致pmon和listener异常》的评论

《连续两次REMOTE_LISTENER 设置为null导致pmon和listener异常》的评论 https://www.xifenfei.com/2012/05/%e8%bf%9e%e7%bb%ad%e4%b8%a4%e6%ac%a1remote_listener-%e8%ae%be%e7%bd%ae%e4%b8%banull%e5%af%bc%e8%87%b4pmon%e5%92%8clistener%e5%bc%82%e5%b8%b8.html 提供7*24专业数据库(Oracle,SQL Server,MySQL,PostgreSQL等)恢复和技术支持@Tel:17813235971 Thu, 11 Dec 2025 02:46:14 +0000 hourly 1 作者：惜分飞 https://www.xifenfei.com/2012/05/%e8%bf%9e%e7%bb%ad%e4%b8%a4%e6%ac%a1remote_listener-%e8%ae%be%e7%bd%ae%e4%b8%banull%e5%af%bc%e8%87%b4pmon%e5%92%8clistener%e5%bc%82%e5%b8%b8.html/comment-page-1#comment-853 Wed, 30 May 2012 03:21:26 +0000 https://www.xifenfei.com/?p=3255#comment-853 Hdr: 9235880 11.1.0.7 NET 11.1.0.7 PRODID-115 PORTID-226 6836609 Abstract: ALTER OF REMOTE_LISTENER PARAMETER CAUSES SERVICE_UPDATE SPIN *** 12/22/09 08:38 am *** PROBLEM: 11.1.0.7 four Node RAC exadata system, Linux x86-64 Altering the value of REMOTE_LISTENER with a short delay inbetween, 1.ALTER SYSTEM SET remote_listener='' SCOPE=MEMORY 2.Wait few minutes 3.ALTER SYSTEM SET remote_listener='' SCOPE=SPFILE or ALTER SYSTEM SET remote_listener='' SCOPE=BOTH Causes PMON to to send service updates continuously to the TNS listener. In the region of 300+ updates within a second. This causes CPU increase for the TNS listener process and the listener.log to fill quickly. DIAGNOSTIC ANALYSIS: Alert.log Wed Dec 16 11:32:45 2009 ALTER SYSTEM SET remote_listener='' SCOPE=MEMORY; Wed Dec 16 11:34:23 2009 ALTER SYSTEM SET remote_listener='' SCOPE=BOTH; PMON Trace via event 10257 *** 11:34:24.394 kmmlrl: update remote_listener kmmlrl: 56 processes kmmlrl: nsgr update returned 0 kmmlrl: nsgr register returned 0 kmmlrl: update remote_listener kmmlrl: nsgr update returned 0 kmmlrl: nsgr register returned 0 kmmlrl: update remote_listener kmmlrl: nsgr update returned 0 kmmlrl: nsgr register returned 0 kmmlrl: update remote_listener kmmlrl: nsgr update returned 0 Listener.log 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 16-DEC-2009 11:34:24 * service_update * dmis0021 * 0 WORKAROUND: If the commands are run close together, within seconds, problems has yet to reproduce. Run ALTER SYSTEM command with SCOPE=BOTH straight away and the problem does not reproduce. RELATED BUGS: None found REPRODUCIBILITY: Customer can reproduce on 2 databases, one production, one test, on same RAC cluster. Unable to reproduce inhouse, tested 11.1.0.6/11.1.0.7 standalone/RAC and Exadata systems TEST CASE: Unable to reproduce inhouse STACK TRACE: #0 0x0000003bd62c8fdf in poll () from /lib64/libc.so.6 #1 0x000000000348dbbf in ntevpque () #2 0x000000000348a0b8 in ntevque () #3 0x000000000341fb3c in nsevwait () #4 0x0000000000a29503 in ksnwait () #5 0x0000000007943125 in ksliwat () #6 0x0000000007941050 in kslwaitctx () #7 0x0000000000ac29ca in ksuclnwt () #8 0x0000000000ac16bf in ksucln () #9 0x0000000001c37b5b in ksbrdp () #10 0x0000000001dcc2dd in opirip () #11 0x0000000001134ec2 in opidrv () #12 0x000000000183f2c2 in sou2o () #13 0x0000000000974eb5 in opimai_real () #14 0x0000000001844879 in ssthrdmain () #15 0x0000000000974d5f in main () ]]> 作者：惜分飞 https://www.xifenfei.com/2012/05/%e8%bf%9e%e7%bb%ad%e4%b8%a4%e6%ac%a1remote_listener-%e8%ae%be%e7%bd%ae%e4%b8%banull%e5%af%bc%e8%87%b4pmon%e5%92%8clistener%e5%bc%82%e5%b8%b8.html/comment-page-1#comment-852 Wed, 30 May 2012 03:20:38 +0000 https://www.xifenfei.com/?p=3255#comment-852 After REMOTE_LISTENER change, excessive CPU seen for TNS listener process

Applies to:
Oracle Net Services - Version: 11.1.0.6 - Release: 11.1
Information in this document applies to any platform.
11.1 databases onwards

Symptoms
After altering the value of the parameter REMOTE_LISTENER, 
excessive CPU is seen for the TNS listener process (TNSLSNR) and the listener.log file grows rapidly. 
Alert log confirms the REMOTE_LISTENER parameter in the SPFILE was altered.
Listener.log shows continuous service_update triggered from PMON to the TNS listener, 100's per second. 
REMOTE_LISTENER had been set to null twice

Listener.log example section
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0
16-DEC-2009 11:34:24 * service_update * orcl01 * 0

PMON trace
*** 2009-12-16 11:34:24.394
kmmlrl: update remote_listener
kmmlrl: 56 processes
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0
kmmlrl: update remote_listener
kmmlrl: nsgr update returned 0
kmmlrl: nsgr register returned 0

Alert log
Wed Dec 16 11:32:45 2009
ALTER SYSTEM SET remote_listener='' SCOPE=MEMORY;
Wed Dec 16 11:34:23 2009
ALTER SYSTEM SET remote_listener='' SCOPE=BOTH;

Changes
REMOTE_LISTENER parameter value changed to null value

Cause
Bug 9235880Alter of REMOTE_LISTENER parameter causes service update spinn

Solution
Bug is being worked on by development. 
Do not set REMOTE_LISTENER to Null if already Null

Workarounds
If REMOTE_LISTENER is required to by Null, set to value before setting to Null
ALTER SYSTEM SET remote_listener='example.com' SCOPE=BOTH;
ALTER SYSTEM SET remote_listener='' SCOPE=BOTH;
Or set to a false value
ALTER SYSTEM SET remote_listener='example2.com' SCOPE=BOTH;
Example2 not being a valid net-service-name entry

]]>