SAPOSCOL Problems with Shared Memory

[Former Member]

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

[Former Member]

Hello Traci,

you have tried a lot of things....

I would suggest to stop all running saposcol jobs and only use the 7.00 saposcol newest version for your tests.

Otherwise SAP-Support should resolve it.

Regards

Guido

[Former Member]

Hi Tracy,

ok, you write, that you are using 3.1I, 5.0 & 6.0 on one box.

Then you need - different to all other platforms - 2 SAPOSCOLs ...

3.1I needs one SAPOSCOL and this could be 3.1I (very old & outdated coding) or you use the 4.6D SAPOSCOL for that. This only works with the EXT 3.1I kernel and a pretty new patch level and new SAPOSCOL.

On the other hand, most likely it should be sufficient to have ST06 in 5.0 and 6.0 only ))

ECC:

Go for the latest SAPOSCOL in 6.40 in the ecc 5 kernel and the latest SAPOSCOL in the 7.00 kernel and then both will work fine (only one will stay active as they are compatible)

Your SAPOSCOL seems to be not really patched right now:

COLL 20.89 640 - AS/400 SAPOSCOL Version 18 Oct 2005 ...

=> Go for a newer version in SAPOSCOL and kernel and you are fine )

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hello Traci,

have you any entries in the os-collector log files in ST06?

Did you already try saposcol -d and its options?

Regards

Guido

[Former Member]

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"

[hannes_kuehnemund]

Dear Traci,

what version of saposcol are you using? As saposcol is completely downwards compatible, I always use the latest version. I also had several problems with the 6.20 and 6.40 version, but the 7.00 version works fine for me. Maybe you give it a try.

Cheers,

Hannes

[Former Member]

Dear Hannes,

We have three different system levels (ECC5.0, ECC6.0, and 31I). I have used saposcol versions 640, 46D, and even 31I (SAP sent me the savf for a 31I saposcol).

What version of SAP are you using the 7.0 saposcol with?

Thanks,

Traci