The SAP System Collector (SAPOSCOL) is a platform-independent standalone program that runs in the background of the OS and uses a variety of applications on the host and segments of shared memory of all SAP instances to create a system Collect information. These information details can be displayed via the front end SAPGUI transaction code ST 06 / OS 06. This is a very useful tool for NetWeaver / Basis administrators and consultants to monitor server performance. Although SAPOSCOL extracts real-time data from the system, it is not automatically updated, but you need to click on & # 39; Update & # 39 ;. Click the button to retrieve the updated data. SAPOSCOL collects and records system data every ten seconds and also records hourly unit prices for the past 24 hours. It autonomously executes one process per host from the SAP instance and gathers data from various operating system resources. Users can use this tool to monitor all servers in the SAP landscape. However, for a remote server (livecache server), the transaction code is OS 07. You can also check the CPU usage, physical and virtual memory usage, pool data / swap size, disk response time, usage rate of physical disk and file system, resource load of running process, LAN data as well from the watch list .
Menu -> Tools -> CCMS -> Control / Monitoring -> Performance -> Operating System -> Local -> Activity
If data is not displayed, it means that the OS collector (SAPOSCOL) is not running (error code: shared memory can not be used). In this situation, your main job is to fix saposcol to run correctly. This usually happens after a new SAP installation or kernel upgrade. If you are new to the SAP system, please refer to the following guidelines to improve the problem of saposcol.
Unix / Linux / AIX / Sun / Solaris system:
First, check the permissions of the saposcol.exe file. 777 (owner is root of group sapsys), the sticky bit needs to be set to 4750. If you want to know the user executing saposcol, it is called "ps - ef | grep saposcol". To change the saposcol file to owner root, group sapsys (mode 4750), log in to the UNIX system as root, execute the following command,
cd / usr / sap // SYS / exe / run
Chap root supplementary school
chgrp sapsys saposcol
chmod 4750 saposcol
To set permissions, you can also execute "saproot.sh" in the exe directory. Next, run saposcol -l as the same owner (root). Please check collector state with saposcol - s. After setting the access right of the file, please click ST06 -> Operating System Collector -> Start & # 39; Run SAPOSCOL.
To stop the OS collector, use saposcol - k. If this command fails to terminate the process, you can run "cleanipc 99 remove" (see SAP note 548699). If this attempt also fails, you need to delete the saposcol shared memory key. Execute the command "ipcs - ma" and write down the shared memory ID on the line containing the saposcol key. Next, execute "ipcrm - m ID" command. The next time you run saposcol, the shared memory key is recreated.
Sometimes using "saposcol - l" will display a message that it is already running, but if you use "ps - ef | grep - i saposcol" to grape a process, the process may not be displayed. In this case, you can use the undocumented parameter "saposcol - f". Here "f" represents to force the process to start. When that begins, use "saposcol - k" to stop the process at the regulated melon and start the process normally using "saposcol - l".
If saposcol is not executed yet, it must be started in dialog mode. Log in with use adm and follow the steps below.
Suppo-school-d
Collector> Clean
Collector> Termination
Execute saposcol - k to stop the collector.
Before restarting
Suppo-school-d
Collector> Vacation (You need to receive a message - Shared memory has been deleted)
Collector> Termination
cd / usr / sap / tmp
mv coll.put coll.put.sav
CD
Supports
"Coll.put" (SAP Note 548699, see point 7) if this file contains old shared memory and needs to be deleted to get a clean start. If erasing shared memory fails, execute the following command and erase the shared memory.
$ saposcol -kc
$ saposcol -f
If this also fails, you need to reboot the system from the OS level. A new version of saposcol is also required (check SAP Note 19227).
IBM iSeries i5 / OS (OS / 400, OS / 390):
- Please check the permissions of the directory & # 39; / usr / sap / tmp & # 39; The file saposcol.exe must be 4755 and the owner must be root in the sapsys group. After assigning privileges, you can run from the OS command line using SAPOSCOL - l. To display the status, click SAPOSCOL-s & # 39; to stop using the SAPOSCOL-s & # 39; process. You can also execute processes by submitting jobs at the OS level.
CALL PGM (SAPOSCOL) PARM (-l)
It submits the job to the job queue QBATCH of the library QGPL.
- On iSeries, analyzing CPU utilization using tcode ST06 / OS06 may cause strange data. Even if you are using multiple CPUs, SAPOSCOL may report only the CPU usage of the first CPU. Also, if the SAP instance is running in a non-upper partition where multiple logical partitions are using a shared processor pool, CPU usage may be reported in excess of 100% at regular intervals. In this case, please confirm that the CPU usage rate reported with CPU number 0 is the average usage rate of all the CPUs used in the system. If you want to display the shared CPU partition information, apply the support package according to SAP Note 994025 including the following patch level
6.40 disp + work package (DW): 182 SAPOSCOL: 69
7.00 disp + work package (DW): 109 SAPOSCOL: 34
By applying these patches and support packages to the system, you can display additional information in two sections, "host system" and "virtual system", using the new transactions OS06N, ST06N, and OS07N . This includes information on the current partition and the partition type in the shared processor pool and the CPU consumed and consumed. Therefore, if SAPOSCOL is not running on an iSeries user, you need to apply the latest kernel and saposcol patch. (SAP Notes 708136 and 753917)
- Another scenario of AS / 400 that saposcol is not running and can not be started from ST 06 / OS 06. There is a problem that the authority list R3ADMAUTL is not accurate. You can solve it in this way,
1) Remove QSECOFR * ALL X
2) * Change PUBLIC from * USE to * EXCLUDE
3) Add R3OWNER * ALL X
You can start saposcol using tcode ST06 / OS06. You can also start the process from the command line,
CALL PGM (/ SAPOSCOL PARM (## - l & # 39;))
If this does not solve the problem, check whether the user R3OWNER (* NOTE: 175852) has * USE authority assigned to both programs QPMLPFRD and QPMWKCOL in library QSYS. Otherwise, you need to execute the following command.
GRTOBJAUT OBJ (QSYS / QPMLPFRD) OBJTYPE (* PGM) user (R3OWNER) AUT (* USE)
GRTOBJAUT OBJ (QSYS / QPMWKCOL) OBJTYPE (* PGM) user (R3OWNER) AUT (* USE)
Next, we need to check whether user R3OWNER is part of authorization list R3ADMAUTL (SAP Note: 637174). After that, if the error "SAPOSCOL not running?" Is displayed, follow the procedure below.
1) Delete the shared memory (coll.put) for each SAP. Note: 189072. coll.put & # 39; The location is & # 39; / usr / sap / tmp.
2) If it is running, quit jobs QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA in QSYSWRK.
3) Delete temporary user space WRKOBJ OBJ (R3400 / PERFMISC *) OBJTYPE (* USRSPC).
4) ENDTCPSVR * MGTC
5) QYPSENDC PARM (& # 39; * PFR & # 39; & # 39; [There are 6 blanks after * PFR and there are 6 blanks making up the second parameter]
6) ENDJOB job (xxxxxx / QSYS / QYPSPFRCOL) OPTION (* IMMED) SPLFILE (* YES) [This command must be run for all QYPSPFRCOL jobs found on the system even if they show with * OUTQ as their status]
7) ENDJOB job (xxxxxx / QSYS / CRTPFRDTA) OPTION (* IMMED) SPLFILE (* YES) [This command must be run for all CRTPFRDTA jobs even if they show with * OUTQ as their status]
8) RNMOBJ OBJ (QUSRSYS / QPFRCOLDTA) OBJTYPE (* USRSPC) NEWOBJ (QPFRCOLDTX)
9) RNMOBJ OBJ (QUSRSYS / QPFRCOLDTA) OBJTYPE (* DTAQ) NEWOBJ (QPFRCOLDTX) [This object may or may not exist at this time]
10) CALL QYPSCOLDTA * note This program creates a new * USRSPC. After the collection service is started, there should be a new * DTAQ.
11) Start the collection service using GO PERFORM, opt 2, and opt 1. Or * QYPSSTRC PARM (* STANDARDP of * PFR "# 39; & # 39; [There are 6 blanks after * PFR and there are 6 blanks making up the second parameter]. Or start the collection service from Operations Navigator.
12) STRTCPSVR * MGTC
13) If it is running, exit Operation Navigator and restart. For more information, see the IBM Certified Program Analysis Report (APAR) SE12188.
14) Start SAPOSCOL from ST06 / OS06.
Windows system:
- Go to the Kernel folder on the command line where saposcol.exe is located. Set full owner authority
For files and folders. Next, execute saposcol - l (saposcol - d in dialog mode)
You can also try starting / stopping the SAPOSCOL service from Control Panel -> Administrative Tools -> Services (services.msc).
If all other attempts fail, please check that the version of SAPOSCOL is correct. Please obtain the latest SAPOSCOL from the SAP Service Marketplace of your OS. Download the SAPOSCOL.SAR file for the kernel and save it in the directory. Then stop SAP & SAPOSCOL. Please check the kernel library lock and do not forget to back up the library. Then execute APYR3FIX, then execute APYSAP. Please check OSS Note 19466.
Since the internal memory quota is small, SAPOSCOL may also end. When this memory is gradually satisfied while running SAPOSCOL, the system writes the data outside of the buffer. As a result, the next buffer is cleared and SAPOSCOL ends with a dump. Please apply the patch above the patch level.
SAP release 640: SAPOSCOL patch level 100 and DW patch level 293
SAP release 700: SAPOSCOL patch level 75 and DW patch level 151
SAP release 701: SAPOSCOL patch level 18 and ILE patch level 53
SAP release 710: SAPOSCOL patch level 36 and ILE patch level 161
SAP release 711: SAPOSCOL patch level 12 and ILE patch level 48
Therefore, if you use a different SAP system with different kernel versions on one server, SAP system functions will work without problems, but SAPOSCOL will face a crisis and will not provide data to all systems. This occurs because you are using a new IBM technology in the EXT kernel, you can not put SAPOSCOL in a single level store (SLS) rather than place it in Teraspace. In this situation, it is clear that if you run the EXT system on a system other than the other EXT, saposcol runs on only one system. To solve this problem, you need to upgrade to EXT Kernel on all SAP systems with the latest patches. Set up the appropriate privileges in the SAPOSCOL file & directory as instructed and resolve problems with the SAP OS collector.
