Analysis on the slow startup of ORACLE monitoring in Linux environment

Virtual machine environment, OEL7.2, ORACLE 12.1. After restarting the host, it appears that the listener started for almost 1 minutes.

Here is the analysis process:

Perform a listening start operation, hang up for a while, and finally listen to start successfully

[[email protected] ~]$ lsnrctl start

Connecting to (Description= (address= (protocol=tcp) (HOST=SKY-OEL7) (port=1521)))

STATUS of the LISTENER

------------------------

Alias LISTENER

Version Tnslsnr for Linux:version 12.1.0.2.0-production

Start Date 12-jan-2016 16:42:57

Uptime 0 days 0 hr. 0 min. sec

Boot time is 40 seconds.

Specifies a logging level of 16 for listening

[Email protected] trace]$ Cat/oracle/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora

# Listener.ora Network Configuration File:/oracle/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora

# Generated by Oracle configuration tools.

LISTENER =

(Description_list =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = sky-oel7) (PORT = 1521))

)

)

Trace_level_listener=16

Restart the listener, log

[Email protected] trace]$ tail-f Listener.log

Log messages Written To/oracle/app/oracle/diag/tnslsnr/sky-oel7/listener/alert/log.xml

Trace information written to /oracle/app/oracle/diag/tnslsnr/sky-oel7/listener/trace/ora_4179_140717186082304. TRC

Trace level is currently 16

Started with pid=4179

Listening on: (Description= (Address= (protocol=tcp) (HOST=SKY-OEL7) (port=1521)))

TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE

Warning:subscription for node-down event still pending

12-jan-2016 16:10:14 * (Connect_data= (cid= (program=) (HOST=SKY-OEL7) (user=oracle)) (Command=status) (ARGUMENTS=64) ( Service=listener) (version=202375680)) * Status * 0

[Email protected] admin]$ VI/ORACLE/APP/ORACLE/DIAG/TNSLSNR/SKY-OEL7/LISTENER/TRACE/ORA_4179_140717186082304.TRC

2016-01-12 16:09:34.211259:nttcnp:binding an address to a socket.

2016-01-12 16:09:34.211275:nttcnp:listening on a bound socket (Queue size = 128).

2016-01-12 16:09:34.211324:nttcnp:getting Sockname

2016-01-12 16:09:34.211342:nttcnp:getting PeerName

2016-01-12 16:09:34.211355:nttcnp:exit

2016-01-12 16:09:34.211368:snlingetaddrinfo:entry

2016-01-12 16:10:14.256096:snlingetaddrinfo:getaddrinfo () failed with error-3

2016-01-12 16:10:14.256193:snlingetaddrinfo:exit

2016-01-12 16:10:14.256215:nttcon:exit

2016-01-12 16:10:14.256241:nsopen:transport is open

2016-01-12 16:10:14.256261:nsoptions:entry

No more information is available.

Process initiation Information analysis via Strace

[Email protected] ~]$ strace-f-t-o ~/listener.trc lsnrctl start

View Strace Log Information

5042 16:42:57 socket (pf_inet, sock_dgram| Sock_nonblock, ipproto_ip) = 13

5042 16:42:57 Connect (+, {sa_family=af_inet, sin_port=htons (+), sin_addr=inet_addr ("172.24.97.1")}, 16) = 0

5042 16:42:57 Poll ([{fd=13, events=pollout}], 1, 0) = 1 ([{fd=13, revents=pollout}])

5042 16:42:57 sendto (": \26\1\0\0\1\0\0\0\0\0\0\10sky-oel7\tworkgroup\0" ..., $, msg_nosignal, NULL, 0) = 36

5042 16:42:57 Poll ([{fd=13, Events=pollin}], 1, 0 (Timeout)

5042 16:43:02 socket (pf_inet, sock_dgram| Sock_nonblock, ipproto_ip) = 14

5042 16:43:02 Connect (+, {sa_family=af_inet, sin_port=htons (+), sin_addr=inet_addr ("192.168.191.1")}, 16) = 0

5042 16:43:02 Poll ([{fd=14, events=pollout}], 1, 0) = 1 ([{fd=14, revents=pollout}])

5042 16:43:02 sendto (": \26\1\0\0\1\0\0\0\0\0\0\10sky-oel7\tworkgroup\0" ..., $, msg_nosignal, NULL, 0) = 36

5042 16:43:02 Poll ([{fd=14, Events=pollin}], 1, 0 (Timeout)

The above information indicates that the network timed out due to an address resolution failure.

These addresses are installed, automatically generated DNS address information, due to changes in the environment, the DNS address is different, resulting in access operations

[Email protected] ~]# cat/etc/resolv.conf

# Generated by NetworkManager

Search Workgroup

NameServer 172.24.97.1

NameServer 192.168.191.1

When these addresses are blocked, the listener starts normally.

This article from "Facing the sea, spring Flowers" blog, please be sure to keep this source http://recyclebin.blog.51cto.com/805498/1735281

Analysis on the slow startup of ORACLE monitoring in Linux environment