saposcol shared memory issue

[Former Member]

Dear all,

We have issue with saposcol in one of our systems.

The environment is - SAP ECC 6.0 - ORACLE 11 - AIX version 6.

If we try to start the OS collector we get the below given error:

-

---

4> saposcol -l

-l

Cannot create Shared Memory

-

---

5> saposcol -status

**************************************************************

Collector Versions :

running :

dialog : COLL 20.95 700 - AIX v11.65 5L-64 bit 090118

Shared Memory : attached

Number of records : 17353

Active Flag : active (01)

Operating System :

Collector PID : 0 (00000000)

Collector : not running (process ID not found).

Start time coll. : Thu Jan 1 01:00:00 1970

Current Time : Fri Sep 16 12:15:26 2011

Last write access : Thu Sep 15 14:05:42 2011

Last Read Access : Fri Sep 16 05:33:01 2011

Collection Interval : 10 sec (next delay).

Collection Interval : 0 sec (last ).

Status : read

Collect Details : not required

Refresh : not 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 : 0 sec

**************************************************************

-

---

7> saposcol -k

PID 0 not found. Collecting process not running ?

Setting Stop Flag :

12:16:44 16.09.2011 WARNING: WaitFree: could not set new shared memory status after 15 sec

12:16:44 16.09.2011 LOG: ==== Stop Flag was set by saposcol (kill_collector()).

12:16:44 16.09.2011 LOG: ==== The collection process will stop as soon as possible

Collecting process has stopped.

Process died without reaction ?

12:16:55 16.09.2011 ERROR: ShmCleanup failed (rtc = 1)

-

---

8> saposcol -d

*****************************************************************************

• This is Saposcol Version COLL 20.95 700 - AIX v11.65 5L-64 bit 090118

• Please use 'help' to see the usage.

*****************************************************************************

Collector > leave

leave

12:18:43 16.09.2011 LOG: check_remap: Switched to new shared memory.

12:18:43 16.09.2011 LOG: PfDeleteMonArea failed.

Shared memory deleted.

Collector > quit

Now connected to shared memory.

quit

******************************************************************************

• leaving dialog collector Fri Sep 16 12:18:48 2011

******************************************************************************

9> ipcs -ma|grep 4dbe

m 726663692 0x00004dbe --rw-rw-rw- root system root system 0 1839766 1962086 1560646 12:18:48 12:18:48 14:05:42

-

---

We tried to delete the shared memory used by OS coll with the key 4dbe. (with the help of sap note 548699)

But it did not help and new shared memory is being created but saposcol is not able to start.

Thanks and Regards,

Kiran

[Former Member · Accepted solution]

Hi Kiran,

Seems IPC shared memory segments parameters need to be adjusted.

Goto the profile directory and run the following command.

sappfpar check pf=<your Instance profile>

And see if there any recommendations (errors/warnings) in the output.

Br,

Venky.

[Former Member · Accepted solution]

Hi Venki,

Thanks for the reply, i checked the profile and got one warning and there were no errors.

The warning is:

***WARNING: Unexpected parameter: zcsa/bufdir_entries =10000

Should this be adjusted.

Thanks in advance!

Kiran

[former_member189546]

Hello,

***WARNING: Unexpected parameter: zcsa/bufdir_entries =10000

is not connected to problem you are having

Just means sapfpar does not recognise this paramaeter but kernel does so its ok

Problem you have Cannot create Shared Memory

is probable with ipc memory seqments

Perform command to clear any faulty shared memory at OS level:

cleanipc <instance number> remove

i.e cleanipc 00 remove (if the instance number is 00)

if the problem persists reboot the OS that shouls clear the shared memory

regards,

John Feely

[Former Member]

Hi,

The above issue was resolved with the above steps and also by removing the parameter 'exe/saposcol = (DIR_CT_RUN)/saposcol' from instance profile.

Thanks to all !

Regards,

Kiran

[Former Member]

Hi,

Sometimes, because of the shared memory cannot be created, you may face with that kind of problem. Reboot the server, if it is possible.

Best regards,

Orkun Gedik