Re: TNS-12531 listener trouble on Windows 2003
Date: Thu, 6 Jan 2011 11:45:19 -0800 (PST)
On 6 jan, 20:28, "Gerard H. Pille" <g..._at_skynet.be> wrote:
> HansP wrote:
> > This is happening at a 2 node windows 2003 rac with 96G ram (free ram
> > about 70G)
> > Release of grid infrastructure is 11.2
> > Database 10.2.0.5.
> > When too many users connect (little fewer than 150) all listeners
> > report then 12531 error and become unresponsive afterwards
> > Thu Jan 06 13:32:43 2011
> > No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)
> > (HOST=x.x.x.x)(PORT=1521)))
> > 06-JAN-2011 13:32:43 * service_died * LsnrAgt * 12537
> > 06-JAN-2011 13:32:43 * 12531
> > TNS-12531: TNS:cannot allocate memory
> > lsnrctl status gives protocol adapter error
> > Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)
> > (KEY=LISTENER_SCAN2)))
> > TNS-12560: TNS:protocol adapter error
> > We have increased the desktop heap size to 1M.
> > Any clues or directions?
> > regards HansP
> The only working solution would be switching to Linux.
> But it is clear that the Listener doesn't find enough memory to start an oracle server process.
> If "desktop heap" is needed for that purpose, then 1Mb is not a lot, is it? 1Mb / 150 is not
> much for a server process. Does the listener or do the server processes have access to that
> "desktop heap"?
> Or is your OS running against the 4Gb limit? I quote µicro$oft: "Limits on physical memory for
> 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit
> Windows systems to use more than 4 GB of physical memory."
Well I agree Linux would be much better but the application uses
external procedures in this case DLL's so we are stuck with
The platform is 64bit (the sga is already 20G) I am more familiar with unix/linux so I am just copying what others say which is that that desktop heap size is important.
regards HansP Received on Thu Jan 06 2011 - 13:45:19 CST