SAPOSCOL not running:Shared Memory not available

Dears,
On my PI 7.1 server when I go to ST06 I get message:
SAPOSCOL not running:Shared Memory not available
Please suggest.
Shivam

few suggestions
FAQs on saposcol - http://www.saptechies.com/os-collector-saposcol/
SAP Note 165188 - saposcol not running on AIX-DB2
SAP Note 548699 - FAQ: OS collector SAPOSCOL
SAP Note 103135 - DB2-z/OS: Installing saposcol manually
Regards
Sekhar

Similar Messages

SAPOSCOL is not running,shared memory not available

Hi,
While I tried to start the SAPOSCOL ,it is not starting and throughing the below error.
Profile          : no profile used
06:59:26 05.03.2010   LOG: Saposcol Version : [COLL 20.95 701 - V3.72 64Bit]
06:59:26 05.03.2010   LOG: Working directory : /usr/sap/tmp
06:59:26 05.03.2010   LOG: Process Monitoring active.
06:59:26 05.03.2010   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
06:59:26 05.03.2010   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
06:59:26 05.03.2010   LOG: The following processes will be monitored:
06:59:26 05.03.2010   LOG: Process:    jlaunch-DSAPINFO=IDH_00_dispatcher* for user:               idhadm
06:59:26 05.03.2010   LOG: Process:        jlaunch-DSAPINFO=IDH_00_server* for user:               idhadm
06:59:26 05.03.2010   LOG: Process:           jlaunch-DSAPINFO=IDH_00_sdm* for user:               idhadm
06:59:26 05.03.2010   LOG: RefreshDeviceFiltering failed - no filtering done!
06:59:26 05.03.2010   LOG: Shared Memory Size: 328100.
06:59:26 05.03.2010   LOG: Connected to existing shared memory.
06:59:26 05.03.2010   LOG: MaxRecords = 3492 <> RecordCnt + Dta_offset = 3031 + 61
06:59:42 05.03.2010 WARNING: WaitFree: could not set new shared memory status after 15 sec
06:59:42 05.03.2010   LOG: PfDeleteMonArea Failed
06:59:42 05.03.2010 _WARNING: Cannot create Shared Memory_
06:59:53 05.03.2010   LOG: check_remap: Switched to new shared memory.
Please help me regarding this .
Regards,
Minakshi

This is a bug in NT
Note 1322232 - saposcol: attaching to existing shared memory
I donot see a straight forward correction declared for the same issue in unix flavored systems. From the log file,working directory format(/usr/sap/tmp) looks like a unix box. Could you let us know the OS ? If its AIX there are many notes u may check , to begin with
Note 561356 - saposcol on AIX terminates due to memory leak
Note 710975 - FAQ: which saposcol should be used on AIX
cheers !
PRADi

SAPOSCOL is not working(shared memory not available)

Hi All,
One of my Prodn appln server instance is not displaying the data in tcode OS06,
Even though other instances of app server was able to display;
Getting message : SAPOSCOL is not working(shared memory not available)
Envirn :
Kernel 640 patch 196 ; 64 bit
Collector Versions
running COLL 20.94 640 - V3.73 64Bit
dialog COLL 20.94 640 - V3.73 64Bit
What could be reason for it ? Please suggest possible solutions..
Thanks in Advance

Hello Ramakrishna,
I suggest you to kindly go to OS level and restart the saposcol service and check if that works.
<b>No values and/or problems with shared memory</b>
Check whether saposcol belongs to user 'root' and whether the authorizations are correct: -rwsr-x---
Because the values of saposcol must be visible for all R/3 systems/instances on a host, saposcol writes data in the shared memory segment with key 1002. This shared memory segment must not be changed (for example, by setting profile parameter ipc/shm_psize_1002). In all profiles, check whether the parameter ipc/shm_psize_1002 is set. If it is, this parameter must be removed from the profiles ---> Note 37537.
For further details please refer SAP Note 189072 , 726094.
Regards,
Prem

SAPOsCol running but not working (shared memory not available)

Dear Forum,
We have just set new passwords for SAP AD users (incl SAPService<SID> and <SID>adm), after this restarted SAP instances and servers / clusters). Everything came up well and all services, incl SAPOsCol started up automatically with the new passwords.
Everything works fine - only this morning i wanted to have a look in ST06 and the program tells me "SAPOSCOL not running? (shared memory not available).
The service is running tho, would a restart of the service do any difference, and is there any possibility that a restart of the service on a live and running system would force a system restart? (i couldnt think of any, but I hate restarting services on a live running production system).
Would it be an option to stop/start the collector from ST06?
Thanks in advance,
Kind regards,
Soren

Hello Kaushal,
Thank you for your answer!
I tried to start and stop/start the service from ST06, but it doesnt work. Here is a content og the log - any ideas how i could start the collector without booting the server?
HWO description
      SAPOSCOL version COLL 20.95 701 - 20.64 NT 07/10/17, 64 bit, multithreaded, Non-Unicode
      compiled at   Feb 24 2009
      systemid      562 (PC with Windows NT)
      relno         7010
      patch text    COLL 20.95 701 - 20.64 NT 07/10/17
      patchno       32
      intno         20020600
      running on    L5183N01 Windows NT 6.0 6002 Service Pack 2 16x AMD64 Level 6 (Mod 26 Step 5)
      PATCHES
      DATE     CHANGELIST           PLATFORM             PATCHTEXT
      20081211 1032251              ALL                  Option -w support. Removed SizeOfRecord warning rt 130.
      20090114 1036522              UNIX                 Log file permissions: 664.
      20090203 1041526              UNIX                 Add. single instance check.
      20090210 1042962              ALL                  Continue after EWA HW XML generation failure.
09:46:39 12.04.2010   LOG: Profile          : no profile used
09:46:39 12.04.2010   LOG: Saposcol Version : [COLL 20.95 701 - 20.64 NT 07/10/17]
09:46:39 12.04.2010   LOG: Working directory : C:\usr\sap\PRFCLOG
09:46:39 12.04.2010   LOG: Allocate Counter Buffer [10000 Bytes]
09:46:39 12.04.2010   LOG: Allocate Instance Buffer [10000 Bytes]
09:46:40 12.04.2010   LOG: Shared Memory Size: 118220.
09:46:40 12.04.2010   LOG: Connected to existing shared memory.
09:46:40 12.04.2010   LOG: MaxRecords = 1037 <> RecordCnt + Dta_offset = 1051 + 61
09:46:55 12.04.2010 WARNING: WaitFree: could not set new shared memory status after 15 sec
09:46:55 12.04.2010 WARNING: Cannot create Shared Memory
thanks!
Soren
Edited by: Soeren Friis Pedersen on Apr 12, 2010 9:49 AM

SAPOSCOLL not running...shared memory not available...!!!!

Hi All,
The saposcoll is always getting terminated with a error message "shared memory not available".We have tried all possible remedies but it was of no use, There is no version mismatch and and there is also one saposcoll service running on that host.The problem is coming after we have upgraded our system.
Please suggest me some suitable notes or any solution for it as it is a production server.
Ashwini

Hi,
Please have a look at below link.
SAPOSCOL not running ? (shared memory not available )
Also Check SAP Note 548699 - FAQ: OS collector SAPOSCOL.
Hope this helps.
Thanks
Sushil

SAPOSCOL not runnin? (Shared memory not available)

Hi SAP Experts,
OS:AIX, DB:DB2; R/3: 4.7 ; SID:PW1;
ST06 showing SAPOSCOL is not running
Status Bar shows:SAPOSCOL not runnin? (Shared memory not available)
I checked below
cpaiss51:pw1adm 6> id
uid=15271(pw1adm) gid=506(sapsys) groups=720(sysadm)
pw1adm 7> saposcol -s
Shared Memory:           not attached
no further information available ***
file permission is ok
-rwsr-x---   1 root     sapsys      1118225 Sep 14 2006 saposcol
cpaiss51:pw1adm 10> file saposcol
saposcol:       64-bit XCOFF executable or object module not stripped
Advanced thanks for Quick reply
Thanks & Regards
Kishore

Hi Ruchit,
SAPOSCOL -s is already pasted (It shows the Status of SAPOSCOL)
DEV_COLL
========
cpaiss51:pw1adm 61> more dev_coll
      SAPOSCOL version COLL 20.89 640 - AIX v6.55 5L-64 bit 060323, 64 bit, single threaded, Non-Unicode
      compiled at   May 8 2006
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    COLL 20.89 640 - AIX v6.55 5L-64 bit 060323
      patchno       126
      intno         20020600
      running on    cpaiss51 AIX 1 5 000F3B6F4C00
15:30:06 26.10.2006   LOG: Profile          : no profile used
15:30:06 26.10.2006   LOG: Saposcol Version : [COLL 20.89 640 - AIX v6.55 5L-64 bit 060323]
15:30:06 26.10.2006   LOG: Working directory : /usr/sap/tmp
15:30:06 26.10.2006   LOG: Process Monitoring active.
15:30:06 26.10.2006   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/dev_proc
15:30:06 26.10.2006   LOG: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/
15:30:06 26.10.2006   LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.
15:30:06 26.10.2006   LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.
15:30:06 26.10.2006   LOG: INIT    : Disk data collected for 5 disks (0 filtered)
15:30:06 26.10.2006   LOG: INIT    : Network data collected for 3 interfaces
15:30:06 26.10.2006   LOG: INIT    : Global CPU data collected.
15:30:06 26.10.2006   LOG: INIT    : CPU data collected for 4 cpus
Thanks & Regards,
Kishore Reddy

Shared Memory not available

Hi,
I'm using MaxDB Community Edition 7.6.06.10
Now the second customer has the error
-24700 Could not start DBM Server
-24832 Shared memory not available
-24744 Shared Memory from different platform Unknown (0x00) (expected WIN32, I386)
Both installations worked fine over several weeks/months.
What can I do?
Thank you,
Christoph Schwerdtner

Hi
I was given this fix by SAP Support.
In the directory X:\sapdb\data\wrk you will find two files SID.dbm.shm and SID.dbm.shi.
Rename these files to have a .old extension and restart your DBM session. These files will be recreated automatically.
This can be done while the database is online.
Regards
Doug

TREX Shared memory not initialized

Hi,
       we have installed TREX 7.0 on windows and there is some problem after installation. when we try to start the admin tool with "TREXAdmin.bat" we are getting a mesg like "shared memory not initialized. retry in 5 sec ...disabling shared memory"
       and after few seconds in the same cmd console, we are getting "TREX-nameserver <hostname>:34001 not responding after 1 retries. giving up.".
       feel that the nameserver has some communication problem. can someone please suggest any solution for this ?
Thanks
   Sourav

I had the same error and solved it. Here is what I found out:
the message "shared memory not initialized. retry in 5 sec" is a symptom for a faulty nameserver start
look at the nameserver traces. If you cannot find anything, increase the trace level to 5. In case of HANA the trace level is called saptracelevel in /hana/shared/SID/exe/linuxx86_64/hdb/config/global.ini
in case of HANA hdbdaemon starts hdbnameserver. You can find this info in hdbdaemon's traces at tracelevel 5.
In my case the hdbnameserver could not start because the system was set to be a secondary site with System Replication and it could not communicate with the primary site. The reason was that jumbo frames were enabled on the primary and secondary site, but not on the switches between. So the work-around was to set MTU to 1500 on both sites.

NOT ENOUGH SHARED MEMORY

Hi,
I am facing "NOT ENOUGH SHARED MEMORY " problem even with 1-2 users in portal 3.0.6.x.
The init.ora settings are:
shared_pool_size=104857600 large_pool_size=614400
java_pool_size=20971520
Is it due to hanging sessions?
How to see the hanging sessions inside database?
Can you tell me what is going wrong?
Thanks
Vikas
null

Think I got it figured out. Oracle 10g XE doesn't
have a DB_HANDLE initialization parameter. The
problem is that the initialization parameters are
located in $ORACLE_HOME/dbs/spfileXE.ora, but sqlplus
is looking for initORCL.ora.You mean instance is looking for initORCL.ora and not for SPFILE, or ;-)
So does anyone besides Faust knowSorry, again me ;-)
how to configure
sqlplus to look for spfileXE.ora instead of
initORCL.ora? I can't find an SQL*Plus setting that
will do this.How to set SPFILE and arond it you can find here:
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#i1013934
Cheers!

ADI - Excel is not running, or is not available.

Hi friends,
I am trying to upload the journal entries through ADI. When I try to do this I get the following error
"Excel is not running, or is not available. You cannot upload at this time.".
We are on 11.5.9 and the excel we are using is 2003. This was working absolutely fine earlier. Can some one let me know what the issue could be. Please note the Macro>Security> Options> Publisher Options. This is checked too.
Thanks

Hi;
"Excel is not running, or is not available. You cannot upload at this time.".
We are on 11.5.9 and the excel we are using is 2003. This was working absolutely fine earlier. Can some one let me know what the issue could be. Please note the Macro>Security> Options> Publisher Options. This is checked too.It was working before? So what have you been changed on your system? patch etc?
Please check below which could be helpful for your issue:
Journal Upload Errors With Excel Is Not Running, Or Is Not Available, You Cannot Upload At This Time [ID 243893.1]
Hope it helps
Regard
Helios

SAPOSCOL Problems with Shared Memory

Has anyone had any problems in either starting the saposcol or with keeping it running? We have noticed multiple problems for several years now, and are at a point where the saposcol is not running at all on any of our servers, nor can we start it running.
We're seeing "SAPOSCOL not running ? (Shared memory not available)". I am working with SAP with two different customer messages trying to determine why we cannot start the saposcol.
Does anyone have any ideas?
Thanks,
Traci Wakefield
CV Industries

I do have entries in the os-collector log:
      SAPOSCOL version COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005, 64 bit, single threaded, Non-Unicode
      compiled at   Nov 26 2005
      systemid      324 (IBM iSeries with OS400)
      relno         6400
      patch text    COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005
      patchno       102
      intno         20020600
      running on    CENTDB1 OS400 3 5 0010000A1E1B
13:25:06 28.02.2007   LOG: Profile          : no profile used
13:25:06 28.02.2007   LOG: Saposcol Version : [COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005]
13:25:06 28.02.2007   LOG: Working directory : /usr/sap/tmp
13:26:01 28.02.2007   LOG: Shared Memory Size: 339972.
13:26:01 28.02.2007   LOG: INFO: size = (1 + 60 + 3143) * 106 + 348.
13:26:01 28.02.2007   LOG: Connected to existing shared memory.
13:26:01 28.02.2007   LOG: Reused shared memory. Clearing contents.
13:26:04 28.02.2007   LOG: Collector daemon started
13:26:04 28.02.2007   LOG: read coll.put Wed Feb 28 13:22:01 2007
13:26:04 28.02.2007   LOG: Collector PID: 2469
13:27:05 28.02.2007   LOG: Set validation records.
14:00:32 28.02.2007 WARNING: Out of int limits in pfas41c1.c line 1528
12:58:37 10.03.2007   LOG: Stop Signal received.
12:58:38 10.03.2007   LOG: ==== Starting to deactivate collector ==========
12:59:01 10.03.2007   LOG: ==== Collector deactivated ================
Also, I have tried saposcol -d (and other parameters below):
saposcol -d
kill
clean
leave
quit.
delete the files coll.put, dev_coll"
4" From my open SAP message:
I have also done the following:
1 Check the authorizations of SAPOSCOL as mentioned in SAP Notes:
637174 SAPOSCOL cannot access Libraries of different SAP systems
175852 AS/400: Authorization problems in SAPOSCOL
2 Remove the shared memory (coll.put)
(according to SAP Note: #189072). You could find 'coll.put' in path:
'/usr/sap/tmp'.
3 End the following jobs in QSYSWRK:
QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA
4 Delete the temporary user space:
WRKOBJ OBJ(R3400/PERFMISC) OBJTYPE(USRSPC)
Afterwards you could start SAPOSCOL on operating system level.
Just logon to iSeries as <SID>OFR and run the following command:
SBMJOB CMD(CALL PGM(<kernel_lib>/SAPOSCOL) PARM('-l'))
JOB(SAPOSCOL) JOBQ(R3<SID>400/R3_<nn>)
LOG(4 0 SECLVL) CPYENVVAR(YES)
Thanks,
Traci"

Air 3.4 iOS Push Notification is not fired when app is not running and is not in background

Hello,
I'm making an Air iOS application which uses the iOS Push Notification from Air 3.4.
All is working perfectly except when I receive notifications when the app is not running and is not in background (The app is killed).
I suppose the RemoteNotificationEvent.NOTIFICATION must be dispatched when I receive a notification even if my app is not currently running or in background ?
Do you have already get the same issue ? Do you know what can prevent the notification to be handled ?
Thanks,
Loïc

issue has been fixed in the build available at http://labs.adobe.com/downloads/air3-5.html.
You would now have to attach listener to InvokeEvent. For cases, when application is killed, InvokeEventReason will be InvokeEventReason.NOTIFICATION. The notification payload can be accessed by the following code
protected function onInvokeEvent(event:InvokeEvent):void
     trace("Invokehandler called .... \n");
     trace("reason: " + event.reason + "\n");
     if( event.reason == InvokeEventReason.NOTIFICATION)
                    var payload:Object = Object(event.arguments[0]);
          for (var i:String in payload)
                trace("Key:value pair " + i + ":" + payload[i] + "\n");
          // TODO: DO THE NEEDFUL ON RECIEVING A NOTIFICATION HERE

JDK 1.4.1 + UseISM shared memory not shown by ipcs?

Hello,
Under 1.4.0 (and earlier if i remember correclty) i's able to see the shared memory area in the list generated by ipcs and i'd be sure that shared memory was used. Now, under JDK 1.4.1 ipcs never(?) shows any shared memory areas which could belong to the application? Even though, i sometimes get the error message saying that not enough memory is availbe to use ISM. I've -Xms300m, -Xmx1300m, XX:UseISM. I'm not sure that the application is really using any shared memory. Top-program shows both SIZE 1575M and RES 1473M. So something is happening there anyways. If i don't use ISM top shows different figures.. Running Solaris 5.8 under Sun Fire 280R. One more thing, can set -Xms and -Xmx to a different values and still use ISM?

This is the response I got back from sun...
Hi Phil,
In the previous version of ISM, the shared memory segment was explicitly removed once the vm exited. The problem with this is that if an abnormal vm termination occurred, the shared memory segment would stay resident in the system. In the new version, it has a built in reference counter such that, once all references to that shared memory has exited, it will cleanup the shared memory on its own. This is nice because we don't need to cleanup anything and even under abnormal exit conditions we know that the segment will be removed.
So it is an expected behavior, not a bug.
Let me know if you have any further question or concern about this new
change.
Thanks,
Ingrid Yao

Not enough physical memory is available to power on this virtual machine with its configured settings.

hi ... My opering system is windows 8.1 and my system RAM is 6 GB with intel core i3 processor...
I got error in vmvare " not enough physical memory to start virtual machine. then after some day i visit at your webside and read the bolg about this error solution and i uninstalled the microsofts update like
"KB2995388" then reboot the system, after that i search config.ini file in drive "C:\Program Files (x86)\VMware\VMware Workstation" but i did'nt got this file, so i created a new "config.ini" file and write one line
vmmon.disableHostParameters = “TRUE” and save the file , then i copied this file to vmware workstation , like this path 'C:\Program Files (x86)\VMware\VMware Workstation' after that i opened my vmware and power on virtula machine but still i getting same error like not enough physical memory..........plesae any one can help me ? and give me a better solution to solve this problem ?

Welcome to the Community,
without any details about the VMware Workstation version you are using and the blog you read it's pretty hard to help. Anyway, the issue you mentioned was resolved with VMware Workstation 10.0.4 (see VMware Workstation 10.0.4 Release Notes), so in case you are running an older version it may be worth updating.
André
Message was edited by: a.p. - Fixed typo in version number 10.0.4 (instead of 10.4)

Dv6928us: Laptop not running in Battery, '0% available, Plugged in, not charging' but fine in power

Product No. dv6928us: Laptop is not running in Battery. Battery icon indicates, '0% available, Plugged in, not charging' even when the battery is inserted. But the laptop works fine in power mode.
Battery check indicates: "The primary battery was not detected. Check to assure the battery is properly inserted then restart the computer'.
Execution of this did not help.
Can anybody tell me whether battery life is over or loose connection in battery placement?

whoswho wrote:
Product No. dv6928us: Laptop is not running in Battery. Battery icon indicates, '0% available, Plugged in, not charging' even when the battery is inserted. But the laptop works fine in power mode.
Battery check indicates: "The primary battery was not detected. Check to assure the battery is properly inserted then restart the computer'.
Execution of this did not help.
Can anybody tell me whether battery life is over or loose connection in battery placement?
Try updating The BIOS and then try it again. BIOS (latest): http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-62510-1&cc=us&dlc=en&lc=en&... If that fails to fix it, the battery will need replaced (if you want to) or ignored.

SAPOSCOL not running:Shared Memory not available

Similar Messages

Maybe you are looking for