The Sap principles Os accumulator (Saposcol) is a platform independent stand-alone program that runs in Os background and collects the principles facts using a segment of the shared memory for assorted applications and all Sap instances on a host. These facts details can be viewed straight through transaction code St06/Os06 in frontend Sapgui. It is a very beneficial tool for NetWeaver/Basis Administrators & consultants to monitor server performance. Saposcol extracts real-time data from system, although it does not refreshes automatically, you need to click the 'Refresh' button to get the updated data. Saposcol collects principles data every 10 seconds and records it, and also records the hourly averages for the last 24 hours. It runs autonomously from Sap instances exactly one process per host and collects data from assorted operating principles resources. User can monitor all the servers under Sap landscape with this tool. But for remote server (livecache server) the transaction code is Os07. You can check Cpu utilization, bodily & virtual memory usage, Pool data/Swap size, disk response time, utilization of bodily disks and file systems, resource load for running processes and even Lan data from the monitoring list.
You can navigate to this tool from Sap Menu->Tools->Ccms->Control/Monitoring->Performance->Operating System->Local->Activity.
Remote Control Codes List
If you can't see any data, that means the Os accumulator (Saposcol) is not running (error code: Shared memory not available). In this situation your main task is to fix the saposcol to run properly. This commonly happens after a new Sap factory or Kernel upgrades. If you are new with the Sap Systems the following guideline will be helpful to overcome the saposcol issue.
Logitech Harmony 300 Remote Control 915-000143 Best
Rate This Product :
Logitech Harmony 300 Remote Control 915-000143 Feature
- It controls up to 4 A/V components. It is compatible with 225,000+ devices.
- One placement remote makes it easier for you to control up to 4 A/V components.
- Harmony's constantly updated online database of 225,000+ devices ensures your remote will work with what you own today and add tomorrow
- Turn on and off your TV and cable/satellite box together with just one button press. Choose which device you would like to power on or off.
- Get the commands many other universal remotes are missing, like record TV, List and Live.
- Personalize your remote with shortcuts to your news, sports and on-demand movie channels.
- Turn on and off your TV and cable/satellite box together with just one button press. You can choose which device you would like to power on or off.
Logitech Harmony 300 Remote Control 915-000143 Overview
Simple to set up. Easy enough for anyone to use. Better control of what’s attached to your TV.
Customer Reviews
*** Product Information and Prices Stored: Mar 11, 2012 16:10:40
Unix/Linux/Aix/Sun/Solaris System:
First, Check the permission of saposcol.exe file, it should be 777 (owner is root in group sapsys) and sticky bit should be set to 4750. If you want to know which user is running saposcol, use "ps -ef | grep saposcol". Now to change the saposcol file to owner root, group sapsys, mode 4750, log in as root to your unix principles and execute the commands as below,
cd /usr/sap//Sys/exe/run
chown root saposcol
chgrp sapsys saposcol
chmod 4750 saposcol
You can also run the "saproot.sh" in the exe dir to set the permissions. Then run saposcol -l as the same owner (root). Check accumulator status using saposcol -s. After setting the file permissions, you can also use, St06 -> Operating principles accumulator -> Click on 'Start' to run Saposcol.
To stop the Os accumulator use saposcol -k. If this command failed to kill the process, you can execute "cleanipc 99 remove" (Check Sap Note 548699). If this effort also fails, then you need to remove the shared memory key of saposcol. Execute command "ipcs -ma" and note down Shared Memory Id in the line that contains saposcol key. Then execute the command "ipcrm -m Id". Shared memory key will be created again next time when you run saposcol.
Sometimes using "saposcol -l" gives a message that it's already running, but when you grep the process using "ps -ef|grep -i saposcol" it may not show the process. In this situation, you can use a undocumented parameter "saposcol -f", where "f" stands for beginning the process forcefully. When it starts, then stop the process in regulation methon using "saposcol -k" and then start it commonly using "saposcol -l".
If saposcol still doesn't run, then you need to start it in dialog mode. Login with use adm and result the steps below,
saposcol -d
Collector > clean
Collector > quit
saposcol -k to stop the collector.
Before restarting
saposcol -d
Collector > leave (You should get a message- Shared memory deleted)
Collector > quit
cd /usr/sap/tmp
mv coll.put coll.put.sav
cd
saposcol
"coll.put",if this file contains the old shared memory and should be deleted in order to get a clean start (Check Sap Note 548699, point 7). If you are unsuccessful in clearing shared memory, please try the following commands to clear the shared memory:
$ saposcol -kc
$ saposcol -f
If this also fails, then you need to restart the principles from Os level and seems like also need a new version of saposcol (Check Sap Note 19227).
Ibm iSeries i5/Os (Os/400, Os/390):
- Check permissions of directory '/usr/sap/tmp' and the file 'saposcol.exe', it should be 4755 and owner must be root in sapsys group. Check Sap Note 790639. After assigning permissions you can run from Os command line using 'Saposcol -l'. To show the status use 'Saposcol -s' and to stop the process use 'Saposcol -k'. You can also run the process by submitting a job in Os level using
Call Pgm(Saposcol) Parm(-l)
It submits the job in job queue Qbatch in library Qgpl.
- In iSeries, you might touch strange data when analyzing Cpu utilization using tcode St06/Os06. Even you are using manifold Cpu's, Saposcol might only narrative Cpu usage for the first Cpu. Also sometimes you will find Cpu utilizations reported above 100% in some intervals, if you are running Sap instance in an uncapped partition where manifold logical partitions are using a shared processor pool. In this situation, be sure that Cpu usage reported for Cpu number 0 is the mean usage for all Cpu's being used in the system. If you want to view shared Cpu partition information, apply retain packages as per Sap Note 994025 along with following patch levels
6.40 disp+work package (Dw): 182 Saposcol: 69
7.00 disp+work package (Dw): 109 Saposcol: 34
By applying these patches and retain packages into the system, new transactions, Os06N, St06N, and Os07N are ready to view further facts in two sections titled "Host system" and "Virtual system". These include facts about the partition type and the ready and consumed Cpu in the current partition as well as in the shared processor pool. So, if you are a iSeries user and your Saposcol is not running, highest probability is that you need to put the most recent kernel & saposcol patch. (Sap Note 708136 & 753917)
- Another scenario in iSeries, when your saposcol is not running, and you cannot start it from St06/Os06. Qoute might be with the authorization list R3Admautl was not accurate. You can solve it by this way,
1) remove Qsecofr *All X
2) change *Public from *Use to *Exclude
3) Add R3Owner *All X
Now you can start saposcol using the tcode St06/Os06. And also you can start the process from command line,
Call Pgm(/Saposcol Parm('-l')
If this does not solve the Qoute check if both programs Qpmlpfrd and Qpmwkcol in library Qsys have *Use- authority assigned for user R3Owner (Sap Note: 175852). If not then you have to run the following commands:
Grtobjaut Obj(Qsys/Qpmlpfrd) Objtype(*Pgm) User(R3Owner) Aut(*Use)
Grtobjaut Obj(Qsys/Qpmwkcol) Objtype(*Pgm) User(R3Owner) Aut(*Use)
Then you should verify if the user R3Owner is part of authority list R3Admautl (Sap Note: 637174). After this if you receive the error "Saposcol not running? (Shared memory not available), then result the steps below,
1) Remove the shared memory (coll.put) as per Sap Note: 189072. 'coll.put' location is: '/usr/sap/tmp'.
2) End the jobs Qpmaserv, Qpmaclct, Qypspfrcol and Crtpfrdta in Qsyswrk if running.
3) Delete the temporary user space, Wrkobj Obj(R3400/Perfmisc*) Objtype(*Usrspc)
4) Endtcpsvr *Mgtc
5) Call Qypsendc Parm('*Pfr ' ' ') [There are 6 blanks after *Pfr and there are 6 blanks manufacture 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 principles 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 will create a new *Usrspc. After variety services is started there should be a new *Dtaq.
11) Start variety services using Go Perform, opt 2, and opt 1; Or Call Qypsstrc Parm('*Pfr ' '*Standardp' ' ') [There are 6 blanks after *Pfr and there are 6 blanks manufacture up the second parameter]. Or, Start variety services from Operations Navigator.
12) Strtcpsvr *Mgtc
13) End and restart Operations Navigator if running. See Ibm authorized program prognosis narrative (Apar) Se12188 for more information.
14) Now start Saposcol from St06/Os06.
Windows System:
- Go to the Kernel briefcase in command line where you will find saposcol.exe. Set full owner permission
for the file & folder. Then run saposcol -l (saposcol -d in dialog mode)
- You can also try Start/Stop Saposcol assistance from Control Panel -> menagerial Tools -> Services (services.msc).
If all other attempts fail, then make sure you have the accurate version of Saposcol. Get most recent Saposcol from Sap assistance Marketplace for your Os. Download the Saposcol.Sar file for your Kernel and save in a directory. Then Stop Sap & Saposcol. Check for any Kernel library locks and don't forget to take library backup. Then run Apyr3Fix and then Apysap. Check Oss Note 19466.
Saposcol also can be ended due to small number of internal memory allocation. When this memory filled slowly while the runtime of Saposcol, principles writes data outside the buffer. As a result the following buffer is cleared and Saposcol terminates with a dump. Apply the following patches with at least the patch levels specified below:
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
So, it's unavoidable that if we use separate Sap Systems in one server with incompatible aggregate of Kernel versions, Saposcol will face crisis and will not furnish data for all systems, though Sap principles functions will run without any trouble. This happens because we are using new Ibm technology with Ext Kernels, so it will not allow Saposcol to reside in particular level store (Sls), rather than put it to Teraspace. In this situation it's unavoidable that if you run an Ext principles with some other non-Ext systems, saposcol will run only in one system. To overcome this issue you need to upgrade to Ext Kernel for all Sap systems with most recent patches. Then set allowable authorization for Saposcol file & directory as guided which will solve any Qoute linked to Sap Os Collector.
The Sap theory Os accumulator - Saposcol in a Nutshell
No comments:
Post a Comment