on 08-09-2013 10:34 AM
Dear Experts,
We are facing a problem with SAPOSCOL for all newly upgraded systems (Quality, Development, and Sandbox)
The problem is that when I check in ST06 the operating system collector is not running.
When I checked the SAPOSCOL services in services applet the service is running fine there.
xxxxx::/ # ps -ef|grep saposcol
root 18513 18492 0 09:51:41 pts/0 0:00 grep saposcol
root 7532 1 0 15:49:01 ? 0:42 /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sa p/hostctrl/exe/host_profile
Check permissions... Looks fine
xxxx::/usr/sap/hostctrl/exe # ls -l saposcol
-rwxr-x--- 1 root sapsys 6461152 Jul 29 15:01 saposcol
I tried restarting the service, but no use. It’s running may be a hour time after that we are getting same error like
Error type:
======================= LOG: WaitFree: could not set new shared memory status after 15 sec
16:57:04 08.08.2013 WARNING: pfhpux.c 575: WaitFree() failed. No write access to shared memory
Check Shared memory…Looks fine
Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....: 32
System-imposed number of shared memories.: 512
Shared memory segment size required min..: 479232000 ( 457.0 MB)
Currently available maximum segment size.: 5435817984 (5184.0 MB)
SAPOSCOL Info:
SAPOSCOL version COLL 21.04 720 - V3.0.0 2010-04-07 HP-UX IA64, 64 bit, single threaded, Non-Unicode
compiled at Mar 2 2013
systemid 274 (HP (IA-64) with HP-UX)
relno 7200
patch text COLL 21.04 720 - V3.0.0 2010-04-07 HP-UX IA64
patchno 418
intno 20020600
running on xxxxxx HP-UX B.11.31 U ia64
chgno(local) 1394268
chgno(global) 1398155
sappfpar Output:
================================================================================
== Checking profile: /sapmnt/WDQ/profile/WDQ_DVEBMGS00_xxxx
================================================================================
***WARNING: Unexpected parameter: auth/check_value_write_on =1
***WARNING: Unexpected parameter: ipc/shm_permission_01 =10740
***WARNING: Unexpected parameter: ipc/shm_permission_02 =10740
***WARNING: Unexpected parameter: ipc/shm_permission_03 =10740
***WARNING: Unexpected parameter: ipc/shm_permission_16 =10740
***WARNING: Unexpected parameter: ipc/shm_permission_31 =10740
***WARNING: Unexpected parameter: ipc/shm_permission_52 =10740
***WARNING: Unexpected parameter: ipc/shm_permission_62 =10740
Shared memory disposition overview
================================================================
Shared memory pools
Key: 10 Pool
Size configured.....: 728000000 ( 694.3 MB)
Size min. estimated.: 97022912 ( 92.5 MB)
Advised Size........: 100000000 ( 95.4 MB)
Key: 40 Pool for database buffers
Size configured.....: 140000000 ( 133.5 MB)
Size min. estimated.: 125088088 ( 119.3 MB)
Advised Size........: 128000000 ( 122.1 MB)
Shared memories inside of pool 10
Key: 11 Size: 500000 ( 0.5 MB) Factory calender buffer
Key: 12 Size: 6000000 ( 5.7 MB) TemSe Char-Code convert Buf.
Key: 13 Size: 40500000 ( 38.6 MB) Alert Area
Key: 16 Size: 22400 ( 0.0 MB) Semaphore activity monitoring
Shared memories inside of pool 40
Key: 42 Size: 13920992 ( 13.3 MB) DB TTAB buffer
Key: 43 Size: 34206392 ( 32.6 MB) DB FTAB buffer
Key: 44 Size: 7582392 ( 7.2 MB) DB IREC buffer
Key: 45 Size: 6046392 ( 5.8 MB) DB short nametab buffer
Key: 46 Size: 20480 ( 0.0 MB) DB sync table
Key: 47 Size: 10241024 ( 9.8 MB) DB CUA buffer
Key: 48 Size: 300000 ( 0.3 MB) Number range buffer
Key: 49 Size: 2769392 ( 2.6 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key: 1 Size: 2500 ( 0.0 MB) System administration
Key: 2 Size: 51087068 ( 48.7 MB) Disp. administration tables
Key: 3 Size: 101680000 ( 97.0 MB) Disp. communication areas
Key: 4 Size: 527848 ( 0.5 MB) statistic area
Key: 6 Size: 479232000 ( 457.0 MB) ABAP program buffer
Key: 7 Size: 14838 ( 0.0 MB) Update task administration
Key: 8 Size: 134217828 ( 128.0 MB) Paging buffer
Key: 9 Size: 268435556 ( 256.0 MB) Roll buffer
Key: 14 Size: 20000768 ( 19.1 MB) Presentation buffer
Key: 17 Size: 2774004 ( 2.6 MB) Roll administration
Key: 18 Size: 917604 ( 0.9 MB) Paging adminitration
Key: 19 Size: 78000000 ( 74.4 MB) Table-buffer
Key: 30 Size: 45056 ( 0.0 MB) Taskhandler runtime admin.
Key: 31 Size: 9612000 ( 9.2 MB) Dispatcher request queue
Key: 33 Size: 30720000 ( 29.3 MB) Table buffer, part.buffering
Key: 34 Size: 10240000 ( 9.8 MB) Enqueue table
Key: 41 Size: 25010000 ( 23.9 MB) DB statistics buffer
Key: 51 Size: 18000000 ( 17.2 MB) Extended memory admin.
Key: 52 Size: 180000 ( 0.2 MB) Message Server buffer
Key: 54 Size: 20488192 ( 19.5 MB) Export/Import buffer
Key: 55 Size: 8192 ( 0.0 MB) Spool local printer+joblist
Key: 57 Size: 1572864 ( 1.5 MB) Profilparameter in shared mem
Key: 58 Size: 4096 ( 0.0 MB) Enqueue ID for reset
Key: 62 Size: 85983232 ( 82.0 MB) Memory pipes
Key: 63 Size: 409600 ( 0.4 MB) ICMAN shared memory
Key: 64 Size: 4202496 ( 4.0 MB) Online Text Repository Buf.
Key: 65 Size: 4202496 ( 4.0 MB) Export/Import Shared Memory
Key: 81 Size: 21760 ( 0.0 MB) Security Audit Log
Key: 1002 Size: 400000 ( 0.4 MB) Performance monitoring V01.0
Key: 58900100 Size: 4096 ( 0.0 MB) SCSA area
Nr of operating system shared memory segments: 32
Shared memory resource requirements estimated
================================================================
Total Nr of shared segments required.....: 32
System-imposed number of shared memories.: 512
Shared memory segment size required min..: 479232000 ( 457.0 MB)
Currently available maximum segment size.: 5435817984 (5184.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 1503.0 MB
..in pool 10 92.5 MB, 13% used
..in pool 40 119.3 MB, 89% used
..not in pool: 1285.5 MB
Extended Memory .................: 4096.0 MB
------------------------------------------------
Total, minimum requirement.......: 6104.7 MB
Process local heaps, worst case..: 954.0 MB
Total, worst case requirement....: 7058.7 MB
Errors detected..................: 0
Warnings detected................: 8
Could you please someone help this?
Regards
Raja
root> ./saphostexec -upgrade
Hope it helps
Best regards
Willi Eimler
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
Check SAP Note 1627564 - SAPOSCOL: Clearing Shared Memory and Updating
Saposcol section 2 (Clearing SAPOSCOL Shared Memory Segment:)
saposcol -d (start in dialog
mode)
Collector > clean
Collector > quit
saposcol -k
(stops saposcol)
saposcol -d (before restarting)
Collector >
leave (should get a message Shared memory deleted)
Collector >
quit
cd /usr/sap/tmp
mv coll.put coll.old (rename the file; this stores
the saposcol history data)
cd
saposcol (start saposcol
again)
This will help as it has helped me many time.
Thanks
Manas Behra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manas Behra & RB,
I cleaned Shared Memory Segment and re-started but I am getting again same message,
10:27:13 12.08.2013 LOG: Profile : /usr/sap/hostctrl/exe/host_profile
10:27:13 12.08.2013 LOG: Saposcol Version : [COLL 21.04 720 - V3.0.0 2010-04-07 HP-UX IA64]
10:27:13 12.08.2013 LOG: Working directory : /usr/sap/tmp
10:27:13 12.08.2013 WARNING: Effective user ID of this process is 0 (no root privileges required)
10:27:13 12.08.2013 WARNING: Effective group ID of this process is 0 (no root privileges required)
10:27:13 12.08.2013 LOG: Operating system : [HP-UX riker B.11.31 U ia64 2168845587]
10:27:13 12.08.2013 LOG: Hardware model : [ia64 hp server BL860c]
10:27:13 12.08.2013 LOG: Process Monitoring active.
10:27:13 12.08.2013 LOG: Searching for Process Monitoring Templates in /usr/sap/tmp/procmon
10:27:13 12.08.2013 LOG: INFO: /usr/sap/tmp/procmon does not exist or cannot be opened.
10:27:13 12.08.2013 LOG: INFO: Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.
10:27:13 12.08.2013 LOG: Shared Memory Size: 2045300.
10:27:13 12.08.2013 LOG: Shared Memory was created by process:12259
10:27:13 12.08.2013 LOG: ==== Collector submitted. This is the parent process after fork()=====
10:27:16 12.08.2013 LOG: ==== Collector submitted. This is the child process after fork()=====
10:27:19 12.08.2013 LOG: Connected stderr to log_file
10:27:19 12.08.2013 LOG: Collector daemon started
10:27:19 12.08.2013 LOG: read coll.put Mon Aug 12 10:26:37 2013
10:27:19 12.08.2013 LOG: Collector PID: 12266
======================= LOG: WaitFree: could not set new shared memory status after 15 sec
10:28:35 12.08.2013 WARNING: pfhpux.c 575: WaitFree() failed. No write access to shared memory
Regards
Raja
Hello
The problem is not with the shared segments configured for the SAP system instead it is the shared memory key for the saposcol at the OS level.
Stop the saposcol process from the OS level
Refer to this SAP note
Note 548699 - FAQ: OS collector SAPOSCOL
Clean the shared memory segment for the saposcol as suggested in the note.
Go back to SAP and start saposcol from ST06 and check if that helps.
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a6c40505211d189550000e829fbbd/content.htm
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
8 | |
7 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.