cancel
Showing results for 
Search instead for 
Did you mean: 

SAPOSCOL NOT RUNNING(shared memory not available).

Former Member
0 Kudos

Hi,

We have DEV & QA on one LPAR running 4.6c on V5R3. Resources allocation is good enough. On QA system, TCode ST06 displays SAPOSCOL NOT RUNNING(shared memory not available). First this was the case on DEV, I restarted SAP on DEV and now this problem is occuring on QA system.

Can anyone please suggest what the problem can be? I am still trying to find the error. Log file and Status report is as below.

Log file for SAPOSCOL:

===========================================================

19:11:05 11.08.2007 MSG: ====================================================================================

19:11:05 11.08.2007 MSG: = OS Collector Start

19:11:05 11.08.2007 MSG: ====================================================================================

19:11:05 11.08.2007 MSG: Starting R346DEOPT/SAPOSCOL

19:11:05 11.08.2007 MSG: Saposcol Version is [COLL 20.81 07/01/20 46D - AS/400 SAPOSCOL Version (ILE/EBCDIC) 26 Mar 2007 from R3_2

19:12:01 11.08.2007 MSG: INFO: saposcol's shared memory size is 247222.

19:12:01 11.08.2007 MSG: INFO: size = (1 + 60 + 2268) * 106 + 348.

19:12:01 11.08.2007 MSG: Connected to existing shared memory !

19:12:01 11.08.2007 MSG: Reused shared memory ! Clearing contents.

19:12:04 11.08.2007 MSG: Collector started - Version: COLL 20.81 07/01/20 46D - AS/400 SAPOSCOL Version (ILE/EBCDIC) 26 Mar 2007 f

19:12:04 11.08.2007 WARNING: can't stat put-file /usr/sap/tmp/coll_put

19:12:04 11.08.2007 MSG: Collector PID: 3985

19:13:05 11.08.2007 MSG: Set validation records.

02:41:46 11.09.2007 MSG: PfSigGenHandler: ENDJOB (*CNTRLD) issued

02:41:47 11.09.2007 MSG: ==== Trying to stop saposcol while it is still collecting.

02:41:47 11.09.2007 MSG: ==== Stop Flag set: collector will stop as soon as possible.

02:41:47 11.09.2007 MSG: ====

===========================================================

Status of SAPOSCOL as shown in ST06 is as below:

===========================================================

Status report

Collector Versions

running COLL 20.81 07/01/20 46D - AS/400 SAPOSCOL Version

dialog COLL 20.81 07/01/20 46D - AS/400 SAPOSCOL Version

Shared Memory attached

Number of records 2329

Active Flag active (01)

Operating System OS/400 M0.V5R3 APPN.TEAMDEV 550

Collector PID 3985 (00000F91)

Collector not running (process ID not found)!

Current Time Thu Sep 13 04:13:08 2007

Last write access Mon Sep 3 13:40:08 2007

Last Read Access Thu Sep 13 04:09:30 2007

Collection Interval 59 sec (next delay).

Collection Interval 61 sec (last ).

Status free

Collect Details ? required

Refresh required

Header extention structure

number of x-header records 1

number of communication records 60

number of free com. records 60

resulting offset to 1.data rec. 61

Trace level 2

Collector in IDLE - mode ? NO

become idle after 300 sec without read access.

length of idle interval 60 sec

length of norm.interval 59 sec

===========================================================

Regards,

Sai R.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thanks Victor,

Kernel and SAPOSCOL are upto date. Need to check the PTFs. Would it be fine if I apply group PTFs for Hyper and database?

Regards,

Sai R.

Former Member
0 Kudos

Hello Sai,

Yes. Everything mentioned in the InfoAPAR should be included.

Good luck,

Victor

Former Member
0 Kudos

Hello Sai,

SAPOSCOL works well when the combination of PTF, Disp+work, and SAPOSCOL is good...

Patch SAP kernel and SAPOSCOL to the latest level, and PTF according to II13868. If still not working, call IBM support. (SAP support asked me to contact IBM directly before)

Good luck,

Victor