Shulou(Shulou.com)06/01 Report--

The machine with 256g memory can not be connected when listening, then check the monitoring log and report

TNS-12531: TNS:cannot allocate memory, not every time. Repeat it several times. That's it.

Check the MOS instructions:

Windows: Oracle Net or Connections Via the Listener Fail with TNS-12531 On Windows 64-bit Platform (document ID 1384337.1) CAUSE

This can be caused by an inadequate setting for Desktop Heap Size. Even if this is a 64-bit OS with high amount of memory, there is still a limitation that generates this error.

Of course, it can also be caused when the memory is actually low. Check the resource consumption at the time of this problem. If there is no apparent memory shortage

The solution documented here may resolve the issue.

SOLUTION

Check and edit the Desktop Heap size located here in the registry:

Launch regedt32 and go to:

\ HKEY_LOCAL_MACHINE\ SYSTEM\ CurrentControlSet\ Control\ Session Manager\ SubSystems\

In the right pane, click on Windows and pull down Edit then select Modify.

You should see a string that resembles this in its entirety:

% SystemRoot%\ system32\ csrss.exe ObjectDirectory=\ Windows SharedSection=1024,20480768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sx***v,4 ProfileControl=Off MaxRequestThreads=16

Focus on this section:

Windows SharedSection=1024,20480768

The third argument is the maximum amount of heap memory allocated to non interactive desktops.

Increase this third value and check when the TNS error disappears. There is no optimum value. It

Varies on each MS Windows server.

Let me explain:

The third SharedSection value is the size of each desktop heap associated with the "non-interactive" window station. If this value does not exist, the size of the desktop heap for the non-interactive window station will be the same as the size specified for the interactive window station (the second SharedSection value).

Check this value, 2048 has been increased, if increased, it can indeed alleviate the problem, but at this time there are not many sessions connected, only 73, then the problem is obviously not here; who used up the non-interactive stack, look at the number of processes, all conhost&cmd.exe processes, that is, this thing is used up

Simple violence point, direct: taskkill / im:conhost.exe / f, no more errors

The official also made it clear that this is a BUG.

Bug 14324057-Windows: "% i was unexpected at this time" when cluvfy executes (document ID 14324057.8)

Fixed in 11.2.0.3.10

Verification method:

C:\ Users\ oradba >% ORACLE_HOME%\ bin\ cluvfy comp nodecon-n all

The temporary solution is to kill. If you do process analysis, you can consider using windbg.

First import SRV*C:\ Symbols* http://msdl.microsoft.com/download/symbols

Open a dmp file

Common windbg commands:

Command description. Loadby sos clr load debug extension (use mscorwks below. Net 4.0)! threadpool or! tp displays information about managed thread pool ~ * eStack displays the stack of all threads ~ * runaway shows the last exception that occurred on all threads! runaway shows thread elapsed CPU time! syncblk view program block.logopen log debug log vertarget view system run time! peb to view command line parameters for complete process startup Loaded DLL and environment variables, etc.! dml_proc view process Id and process full path name. CLS clear screen Q exit the current debugging! analyze-v details the current exception information ~ 0s to switch to the specified thread (the middle number represents the thread number)! clrstack view the call stack of the thread Only stack trace parameters for managed code are provided-p displays the parameter values of the managed method! printexception or! pe displays the last exception on the currently active thread! dumpstackobjects or! dso displays all managed objects found within the boundaries of the current stack! dumpobj or! do displays object information Specify any valid object address and you can view the contents of the object! dumparray or! da display array information! gcroot-nostacks display object memory reference The-nostacks option restricts search to garbage collector handles and Freachable objects! dumpheap-stat views all object information in the heap, including type information, number, size, etc.! dumpheap-mt [- min] to view objects of specified type and size, you can specify minimum and large values! eeheap-gc |-loader to view the memory usage of managed objects and program structures! address-summary to view the memory distribution of the process Includes unmanaged memory. Foreach (myobj {! dumpheap-mt 008f4104-short}) {! do ${myobj}} outputs multiple object information, which calls the! do command for all objects of type 008f4104 in the heap

Download WinDGG: http://msdn.microsoft.com/en-us/windows/hardware/hh852365

64bit: http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools_amd64/dbg_amd64.msi

32bit: http://download.microsoft.com/download/A/6/A/A6AC035D-DA3F-4F0C-ADA4-37C8E5D34E3D/setup/WinSDKDebuggingTools/dbg_x86.msi

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.