Lsnrctl status/start hangs

转载请注明出处：http://blog.csdn.net/xiaofan23z

Environment：

HPUX B11.31 + oracle 10.2.0.4 three nodes rac

Symptom：

The listener on the first node was stoped and can’t be start use crs_start or lsnrctl start，restart the instance symptom still exist；

Crs_stat rac1.lsnr offline

Use lsnrctl status/start command will be stuck。

Use crs_startora.sfc12rc1.LISTENER_SFC12RC1.lsnr command will be stuck.

Restart this instance symptom still exist; there is no way to shutdown this node，but users complained the program sometimes hangs when it open；

There is no error information in alert.log listener.log。

Solution：

the program sometimes hangs when it open，sometimes is normal。

Check that：

Crs_stat –t –vinstance was down

Use commandPs –ef|grep tnsfind listener_sfc12rc1 still alive….. this is the root of the program。

Kill -9 ospidkill this listener on os；

Startup database solve the problem out；

转载请注明出处：http://blog.csdn.net/xiaofan23z

Tworelateddocumentationon MOS

Intermittent TNS Listener Hang, New Child Listener Process Forked [ID 340091.1]

Modified03-JUN-2011TypeALERTStatusPUBLISHED

Applies to:

Oracle Net Services - Version: 10.1.0.3.0 to 10.2.0.2.0 - Release: 10.1 to 10.2

Information in this document applies to any platform.

All new connections via TNS listener hang, no errors reported

Checked for relevance on 05-FEB-2010.

Description

Intermittently the TNS listener hangs and new connections to the database are not possible.

Likelihood of Occurrence

The issue is that the TNS listener can hang under load if a second spawned listener process is not closed (remains persistent). Secondary listener processes are not unusual, depending on traffic as well as when the OS grep snapshot is taken. However, a persistent secondary process (longer than say 5 second) is not normal and may be a result of this referenced problem.

TNS listener can hang at any time and effect standalone or RAC systems

Possible Symptoms

Listener process can also consume high amount of CPU

Child TNS listener process is seen when doing a ps on the listener process, eg.:

$ ps -ef | grep tnslsnrora10g 8909 1 0 Sep 15 ? 902:44 /u05/10GHOME/DBHOME/bin/tnslsnr sales -inheritora10g 22685 8909 0 14:19:23 ? 0:00 /u05/10GHOME/DBHOME/bin/tnslsnr sales -inherit

Killing the child process allows new connections to work until the problem reoccurs

Workaround or Resolution

Issue is fixed in 10.2.0.3 Patch Set

Oracle Support recommends patching to 10.2.0.5 as this the lastest release

- OR -

Apply Patch 4518443 for the problem (if a patch is available)

- OR -

As a workaround, two steps should be done:

1. The following parameter can be added to listener.ora

SUBSCRIBE_FOR_NODE_DOWN_EVENT_=OFF

Where should be replaced with the actual listener name configured in the LISTENER.ORA file. This parameter is to be placed by itself on an empty line / at the end of file.

For example, if the listener name is LISTENER (default), the parameter would be:

SUBSCRIBE_FOR_NODE_DOWN_EVENT_LISTENER=OFF

2. Locate the ons.config file in the 10g(rdbms) home and rename it to something else.

For example:

cd $ORACLE_HOME/opmn/conf

mv ons.config ons.config.orig

The listener needs to be restarted after these changes.

This will both prevent the listener from registering against ONS (Oracle Notification Services), which is the area affected by bug:4518443, as well as disable ONS itself. For more information on ONS, please refer to the specific Oracle documentation, for example, for 10.2, see the Oracle10g Release 2 Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.

Please note, that adding the SUBSCRIBE_FOR_NODE_DOWN_EVENT_ to listener.ora file on RAC and disabling the ONS file, will mean that FAN (fast application notification) will not be possible. SeeNote 220970.1 RAC: Frequently Asked Questions for further information on FAN. Therefore, if you have a RAC configuration, then apply the patch and do not disable ONS or FAN.

Also, please note that this might happen with ANY 10g installation, whether it is RAC related or not, and whether there is an Oracle Application installation or not.

Patches

ApplyPatch 4518443 for the problem (if a patch is available)

Modification History

References

Related

Products

·Oracle Database Products > Oracle Database > Net Services > Oracle Net Services

Keywords

HIGH CPU USAGE; INTERMITTENT; LISTENER HANGS; NOTIFICATION SERVICES; SERVICES; TNSLSNR

Extproc Listener Spinning / Hanging [ID 406269.1]

Modified21-AUG-2007     Type PROBLEM     Status MODERATED

This document is being delivered to you via Oracle Support'sRapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

Applies to:

Oracle Net Services - Version: 10.2.0.2

This problem can occur on any platform.

UNIX platforms

Symptoms

On 10.2.x (On UNIX platforms):

- Trying to start extproc listener as non-'oracle' user

- lsnrctl hangs and the tnslsnr process spins (consumes excessive cpu).

- Works fine when started as the 'oracle' user.

- No errors as such just spinning/hanging and inabillity to connect to extproc listener.

- Listener log file indicates that listener has started.

- On node that works the listener log also contains the message:

'Listener completed notification to CRS on start'.

- This doesn't appear on node with problem.

- Trace file also indicates that the listener is trying to contact CRS. As not using RAC.

- Trying workaround of the bug 4518443 by setting:

'SUBSCRIBE_FOR_NODE_DOWN_EVENT_=OFF', but problem still occurs.

Cause

- The problem is caused by lack of world read permission on $ORACLE_HOME/log.

- This probably had been set on the working system earlier.

- The script changePerm.sh does evidently doesn't set this ,although it might be expected to.

Solution

DIAGNOSTIC DETAILS:

==================

Running truss -feao /tmp/truss.log $ORACLE_HOME/bin/tnslsnr EXTPROC_MERLYN1

on non-working system shows the following:

- Listener is looping while trying to access:

$ORACLE_HOME/log/ukblx187/client

,but failing with err# 13.

- Notice that on working system (ukblx186) permissions on:

$ORACLE_HOME/log

were 755 (world read+execute)

,while on non-working they were 750

- Change the permission of:

$ORACLE_HOME/log

on non-working to be 755 , however it might still not work.

- Then rm -rf $ORACLE_HOME/log/ukblx187

retry and all works, the above directory being automatically recreated.

NOTES / ISSUES:

=============

1 - The $ORACLE_HOME/log/ directory doesn't get recreated once deleted

2 - It is not needed to delete it and grant execute to world (read isn't needed) on:

$ORACLE_HOME/log

before the listener would work.

3 - It is possible that after implementing this ,the extproc listener now starts up as a non-oracle user

but when trying to to invoke the extproc program, it fails with:

ORA-12518 - Couldn't hand off client Connection

- This can be fixed by granting world read and execute permission on

$ORACLE_HOME/lib/libagtsh.so.1.0

4 - One further problem might be encountered:

The extproc process failed with:

ORA 28595 - Extproc Agent Invalid DLL path

- This is because a third party supplied shared library was needed which have been stored outside $ORACLE_HOME.

- The solution is covered in Note 198523.1

References

NOTE:198523.1 - External Procedure Calls and ORA-28595 In Versions 9.2 through 10gR2

NOTE:340091.1 - Intermittent TNS listener hang, new child listener process forked.

Related

Products

Oracle Database Products > Oracle Database > Net Services > Oracle Net Services

Keywords

EXTPROC; HANGING; INVALID DLL PATH; LSNRCTL; PROCESS SPINS; SPINNING PROCESS; START LISTENER; TNSLSNR

Errors

ORA-12518

Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement

转载请注明出处：http://blog.csdn.net/xiaofan23z