<< Back to previous view

[QA-53] Starting Listener Hangs with "TNS-12531: TNS:cannot allocate memory" in Listener Log Created: 02/Jul/12  Updated: 12/Jul/12

Status: Closed
Project: Questions & Answers
Fix Version/s: None

Type: Oracle - SQL*Net Priority: Major
Reporter: ubTools Support Assignee: ubTools Support
Resolution: Answered Votes: 0

Product Version: 11.2.0.3
Operating System: Linux
Host Name: .
Database Name: .

 Description   
Starting the LISTENER hangs. The following errors appear as an infinite loop in the listener.log:
02-JUL-2012 15:54:06 * 12531
TNS-12531: TNS:cannot allocate memory
02-JUL-2012 15:54:06 * 12531
TNS-12531: TNS:cannot allocate memory
02-JUL-2012 15:54:06 * 12531
TNS-12531: TNS:cannot allocate memory
02-JUL-2012 15:54:06 * 12531
TNS-12531: TNS:cannot allocate memory
02-JUL-2012 15:54:06 * 12531
TNS-12531: TNS:cannot allocate memory


 Comments   
Comment by ubTools Support [ 02/Jul/12 02:19 PM ]
LISTENER trace enabled in listener.ora as below:
TRACE_LEVEL_LISTENER     = 16
TRACE_FILE_LISTENER      = listener.trc
TRACE_UNIQUE_LISTENER    = TRUE
TRACE_TIMESTAMP_LISTENER = TRUE

listener.trc was generated in $ORACLE_BASE/diag/tnslsnr/linux1/listener/trace/ as below:

2012-07-02 15:55:03.847203 : snlinGetAddrInfo:entry
2012-07-02 15:55:03.847276 : snlinGetAddrInfo:getaddrinfo() failed with error -3
2012-07-02 15:55:03.847295 : snlinGetAddrInfo:exit
2012-07-02 15:55:03.847307 : nserror:entry
2012-07-02 15:55:03.847319 : nserror:nsres: id=0, op=65, ns=12531, ns2=0; nt[0]=0, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=0
2012-07-02 15:55:03.847331 : nsmfr:entry
2012-07-02 15:55:03.847342 : nsmfr:1528 bytes at 0xa193a0
2012-07-02 15:55:03.847352 : nsmfr:normal exit
2012-07-02 15:55:03.847363 : nsopenmplx:error exit
2012-07-02 15:55:03.847373 : nsopen:unable to allocate context area
2012-07-02 15:55:03.847384 : nsopen:error exit
2012-07-02 15:55:03.847395 : nsanswer:error exit
2012-07-02 15:55:03.847411 : nsglhc:nsanswer error 12531

The problem appeared in getaddrinfo() system call.

Comment by ubTools Support [ 02/Jul/12 02:22 PM ]
The IPv4 for hostname was defined in the /etc/hosts; but there was no IPv6 definition.

Even though, only IPv4 address was used in the listener.ora, the problem occured again.

The problem has been disappeared after adding the same hostname as IPv6 to the /etc/hosts.

Generated at Thu Oct 16 08:44:15 UTC 2025 using JIRA Standard Edition, Version: 3.12.3-#302.