cancel
Showing results for 
Search instead for 
Did you mean: 

saposcol is not running?(shared memory not available)

Former Member
0 Kudos

Hi all,

Please help me in solving the problem.In st06, there is no data for display.When i try refresh the st06 the sysytem message is *"saposcol is not running?(shared memory not available)"*

The sap oscol is in start status.This is the log .

Contents of log file

SAPOSCOL version COLL 20.94 640 - 20.55 NT 07/01/17, 32 bit, multithreaded, Non-Unicode

compiled at Mar 22 2007

systemid 560 (PC with Windows NT)

relno 6400

patch text COLL 20.94 640 - 20.55 NT 07/01/17

patchno 175

intno 20020600

running on xxxxxxxxxxxxx Windows NT 5.2 3790 Service Pack 1 8x Intel 801586 (Mod 4 Step 😎

09:09:18 15.07.2008 LOG: Profile : no profile used

09:09:18 15.07.2008 LOG: Saposcol Version : [COLL 20.94 640 - 20.55 NT 07/01/17]

09:09:18 15.07.2008 LOG: Working directory : H:\usr\sap\PRFCLOG

09:09:18 15.07.2008 LOG: Allocate Counter Buffer [10000 Bytes]

09:09:18 15.07.2008 LOG: Allocate Instance Buffer [10000 Bytes]

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:18 15.07.2008 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT

09:09:19 15.07.2008 LOG: Shared Memory Size: 80272.

09:09:19 15.07.2008 LOG: Connected to existing shared memory.

09:09:19 15.07.2008 LOG: MaxRecords = 729 <> RecordCnt + Dta_offset = 693 + 61

09:09:24 15.07.2008 WARNING: WaitFree: could not set new shared memory status after 5 sec

09:09:24 15.07.2008 WARNING: Cannot create Shared Memory

please help me its urgent

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi all!

The problem might be that the virtual memory is not big enough. Please extend this to usually physical memory*3 or more. This is done by, if you are using windows server, going to my computer --> properties -->Advanced --> Performance settings --> Virtual Memory --> change.

Let me know if this works

Francis

Former Member
0 Kudos

HelloSuper Fujitsu,

In order to try to clean the shared memory, please follow the steps of note 189072. In some cases, in Windows platforms, this note doesn't help. If so, you will have to reboot the machine where the SAPOSCOL is running. This will solve the problem.

Hope this helps!

Best regards,

Rafael Toshiaki

Former Member
0 Kudos

Goto the O/S level and stop the "SAPOSCOL" NT Service. Backup then clear out the h:\usr\sap\PERFCLOG folder but keep the sub folder contents. Start the SAPOSCOL NT service then check again.

Former Member
0 Kudos

Thanks

Your solution has worked perfect

Thanks