The SAP System OS authority (SAPOSCOL) is a stage autonomous remain solitary program that keeps running in OS foundation and gathers the framework data utilizing a portion of the mutual memory for different applications and all SAP cases on a host. These data points of interest can be seen through exchange code ST06/OS06 in frontend SAPGUI. It is an exceptionally valuable device for NetWeaver/Basis Administrators and advisors to screen server execution. SAPOSCOL separates constant information from framework, despite the fact that it doesn't revives consequently, you have to tap the 'Invigorate' catch to get the refreshed information. SAPOSCOL gathers framework information like clockwork and records it, and furthermore records the hourly midpoints throughout the previous 24 hours. It runs self-sufficiently from SAP cases precisely one process for every host and gathers information from different working framework assets. Client can screen every one of the servers under SAP scene with this apparatus. In any case, for remote server (livecache server) the exchange code is OS07. You can check CPU use, Physical and virtual memory use, Pool information/Swap measure, plate reaction time, usage of physical circles and record frameworks, asset stack for running procedures and even LAN information from the observing rundown.
You can explore to this instrument from SAP Menu->Tools->CCMS->Control/Monitoring->Performance->Operating System->Local->Activity.
On the off chance that you can't perceive any information, that implies the OS Collector (SAPOSCOL) isn't running (mistake code: Shared memory not accessible). In this circumstance your fundamental assignment is to settle the saposcol to run appropriately. This for the most part occurs after another SAP establishment or Kernel redesigns. On the off chance that you are new with the SAP Systems the accompanying rule will be useful to overcome the saposcol issue.
Unix/Linux/AIX/Sun/Solaris System:
To begin with, Check the authorization of saposcol.exe record, it ought to be 777 (proprietor is root in aggregate sapsys) and sticky piece ought to be set to 4750. On the off chance that you need to know which client is running saposcol, utilize "ps - ef | grep saposcol". Presently to change the saposcol record to proprietor root, bunch sapsys, mode 4750, sign in as root to your unix framework and execute the orders as underneath,
disc/usr/sap//SYS/exe/run
chown root saposcol
chgrp sapsys saposcol
chmod 4750 saposcol
You can likewise run the "saproot.sh" in the exe dir to set the consents. At that point run saposcol - l as a similar proprietor (root). Check authority status utilizing saposcol - s. Subsequent to setting the document authorizations, you can likewise utilize, ST06 - > Operating System Collector - > Click on 'Begin' to run SAPOSCOL.
To stop the OS authority utilize saposcol - k. In the event that this order neglected to slaughter the procedure, you can execute "cleanipc 99 expel" (Check SAP Note 548699). On the off chance that this endeavor likewise flops, at that point you have to expel the mutual memory key of saposcol. Execute summon "ipcs - mama" and note down Shared Memory ID in the line that contains saposcol key. At that point execute the summon "ipcrm - m ID". Shared memory key will be made again next time when you run saposcol.
Now and again utilizing "saposcol - l" gives a message that it's as of now running, however when you grep the procedure utilizing "ps - ef|grep - I saposcol" it may not demonstrate the procedure. In this circumstance, you can utilize an undocumented parameter "saposcol - f", where "f" remains for beginning the procedure commandingly. When it begins, at that point stop the procedure in direction methon utilizing "saposcol - k" and after that begin it regularly utilizing "saposcol - l".
In the event that saposcol still doesn't run, at that point you have to begin it in discourse mode. Login with utilize adm and take after the means underneath,
saposcol - d
Authority > clean
Authority > quit
saposcol - k to stop the authority.
Before restarting
saposcol - d
Authority > abandon (You ought to get a message-Shared memory erased)
Authority > quit
compact disc/usr/sap/tmp
mv coll.put coll.put.sav
compact disc
saposcol
"coll.put",if this record contains the old shared memory and ought to be erased keeping in mind the end goal to get a new beginning (Check SAP Note 548699, point 7). In the event that you are unsuccessful in clearing shared memory, please attempt the accompanying orders to clear the common memory:
$ saposcol - kc
$ saposcol - f
In the event that this likewise flops, at that point you have to restart the framework from OS level and appears like additionally require another adaptation of saposcol (Check SAP Note 19227).
IBM iSeries i5/(OS/400, OS/390):
- Check consents of index '/usr/sap/tmp' and the record 'saposcol.exe', it ought to be 4755 and proprietor must be root in sapsys gathering. Check SAP Note 790639. In the wake of relegating consents you can keep running from OS order line utilizing 'SAPOSCOL - l'. To demonstrate the status utilize 'SAPOSCOL - s' and to stop the procedure utilize 'SAPOSCOL - k'. You can likewise run the procedure by presenting an occupation in OS level utilizing
CALL PGM(SAPOSCOL) PARM(- l)
It presents the activity in work line QBATCH in library QGPL.
- In iSeries, you may encounter bizarre information while investigating CPU usage utilizing tcode ST06/OS06. Indeed, even you are utilizing various CPU's, SAPOSCOL may just report CPU use for the primary CPU. Additionally once in a while you will discover CPU usages announced over 100% in a few interims, in the event that you are running SAP example in an uncapped segment where different sensible segments are utilizing a mutual processor pool. In this circumstance, make certain that CPU use detailed for CPU number 0 is the normal use for all CPU's being utilized as a part of the framework. On the off chance that you need to see shared CPU parcel data, apply bolster bundles according to SAP Note 994025 including following patch levels
6.40 disp+work bundle (DW): 182 SAPOSCOL: 69
7.00 disp+work bundle (DW): 109 SAPOSCOL: 34
By applying these patches and bolster bundles into the framework, new exchanges, OS06N, ST06N, and OS07N are accessible to see extra data in two segments titled "Host framework" and "Virtual framework". These incorporate data about the segment compose and the accessible and expended CPU in the present segment and also in the common processor pool. In this way, on the off chance that you are an iSeries client and your SAPOSCOL isn't running, most noteworthy likelihood is that you have to put the most recent piece and saposcol fix. (SAP Note 708136 and 753917)
- Another situation in iSeries, when your saposcol isn't running, and you can't begin it from ST06/OS06. Issue may be with the approval list R3ADMAUTL was not precise. You can fathom it by along these lines,
1) Remove QSECOFR *ALL X
2) Change *PUBLIC from *USE to *EXCLUDE
3) Add R3OWNER *ALL X
Presently you can begin saposcol utilizing the tcode ST06/OS06. And furthermore you can begin the procedure from charge line,
CALL PGM(/SAPOSCOL PARM('- l')
On the off chance that this does not take care of the issue check if the two projects QPMLPFRD and QPMWKCOL in library QSYS have *USE-expert allocated for client R3OWNER (SAP Note: 175852). If not then you need to run the accompanying charges:
GRTOBJAUT OBJ(QSYS/QPMLPFRD) OBJTYPE(*PGM) USER(R3OWNER) AUT(*USE)
GRTOBJAUT OBJ(QSYS/QPMWKCOL) OBJTYPE(*PGM) USER(R3OWNER) AUT(*USE)
At that point you ought to confirm if the client R3OWNER is a piece of specialist list R3ADMAUTL (SAP Note: 637174). After this on the off chance that you get the mistake "SAPOSCOL not running? (Shared memory not accessible), at that point take after the means beneath,
1) Remove the mutual memory (coll.put) according to SAP Note: 189072. 'coll.put' area is: '/usr/sap/tmp'.
2) End the occupations QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA in QSYSWRK if running.
3) Delete the brief client space, WRKOBJ OBJ(R3400/PERFMISC*) OBJTYPE(*USRSPC)
4) ENDTCPSVR *MGTC
5) CALL QYPSENDC PARM('*PFR ' ') [There are 6 spaces after *PFR and there are 6 spaces making up the second parameter]
6) ENDJOB JOB(xxxxxx/QSYS/QYPSPFRCOL) OPTION(*IMMED) SPLFILE(*YES) [This summon must be kept running for all QYPSPFRCOL employments found on the framework regardless of whether they appear with *OUTQ as their status]
7) ENDJOB JOB(xxxxxx/QSYS/CRTPFRDTA) OPTION(*IMMED) SPLFILE(*YES) [This summon must be kept running for all CRTPFRDTA employments regardless of whether they appear with *OUTQ as their status]
8) RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*USRSPC) NEWOBJ(QPFRCOLDTX)
9) RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*DTAQ) NEWOBJ(QPFRCOLDTX) [This protest might exist at this time]
10) CALL QYPSCOLDTA *note This program will make another *USRSPC. After accumulation administrations is begun there ought to be another *DTAQ.
11) Start accumulation administrations utilizing GO PERFORM, pick 2, and select 1; OR CALL QYPSSTRC PARM('*PFR ' '*STANDARDP' ' ') [There are 6 spaces after *PFR and there are 6 spaces making up the second parameter]. Or then again, Start gathering administrations from Operations Navigator.
12) STRTCPSVR *MGTC
13) End and restart Operations Navigator if running. See IBM approved program investigation report (APAR) SE12188 for more data.
14) Now begin SAPOSCOL from ST06/OS06.
Windows System:
- Go to the Kernel organizer in charge line where you will discover saposcol.exe. Set full proprietor consent
for the document and organizer. At that point run saposcol - l (saposcol - d in exchange mode)
- You can likewise attempt Start/Stop SAPOSCOL benefit from Control Panel - > Administrative Tools - > Services (services.msc).
On the off chance that every other endeavor flop, at that point ensure you have the right form of SAPOSCOL. Get most recent SAPOSCOL from SAP Service Marketplace for your OS. Download the SAPOSCOL.SAR petition for your Kernel and spare in a registry. At that point STOP SAP and SAPOSCOL. Check for any Kernel library bolts and keep in mind to take library reinforcement. At that point run APYR3FIX and after that APYSAP. Check OSS Note 19466.
SAPOSCOL likewise can be ended because of little measure of interior memory designation. At the point when this memory filled step by step amid the runtime of SAPOSCOL, framework composes information outside the cushion. Subsequently the accompanying cushion is cleared and SAPOSCOL ends with a dump. Apply the accompanying patches with in any event the fix levels determined underneath:
SAP Release 640: SAPOSCOL fix level 100 and DW fix level 293
SAP Release 700: SAPOSCOL fix level 75 and DW fix level 151
SAP Release 701: SAPOSCOL fix level 18 and ILE fix level 53
SAP Release 710: SAPOSCOL fix level 36 and ILE fix level 161
SAP R
You can explore to this instrument from SAP Menu->Tools->CCMS->Control/Monitoring->Performance->Operating System->Local->Activity.
On the off chance that you can't perceive any information, that implies the OS Collector (SAPOSCOL) isn't running (mistake code: Shared memory not accessible). In this circumstance your fundamental assignment is to settle the saposcol to run appropriately. This for the most part occurs after another SAP establishment or Kernel redesigns. On the off chance that you are new with the SAP Systems the accompanying rule will be useful to overcome the saposcol issue.
Unix/Linux/AIX/Sun/Solaris System:
To begin with, Check the authorization of saposcol.exe record, it ought to be 777 (proprietor is root in aggregate sapsys) and sticky piece ought to be set to 4750. On the off chance that you need to know which client is running saposcol, utilize "ps - ef | grep saposcol". Presently to change the saposcol record to proprietor root, bunch sapsys, mode 4750, sign in as root to your unix framework and execute the orders as underneath,
disc/usr/sap//SYS/exe/run
chown root saposcol
chgrp sapsys saposcol
chmod 4750 saposcol
You can likewise run the "saproot.sh" in the exe dir to set the consents. At that point run saposcol - l as a similar proprietor (root). Check authority status utilizing saposcol - s. Subsequent to setting the document authorizations, you can likewise utilize, ST06 - > Operating System Collector - > Click on 'Begin' to run SAPOSCOL.
To stop the OS authority utilize saposcol - k. In the event that this order neglected to slaughter the procedure, you can execute "cleanipc 99 expel" (Check SAP Note 548699). On the off chance that this endeavor likewise flops, at that point you have to expel the mutual memory key of saposcol. Execute summon "ipcs - mama" and note down Shared Memory ID in the line that contains saposcol key. At that point execute the summon "ipcrm - m ID". Shared memory key will be made again next time when you run saposcol.
Now and again utilizing "saposcol - l" gives a message that it's as of now running, however when you grep the procedure utilizing "ps - ef|grep - I saposcol" it may not demonstrate the procedure. In this circumstance, you can utilize an undocumented parameter "saposcol - f", where "f" remains for beginning the procedure commandingly. When it begins, at that point stop the procedure in direction methon utilizing "saposcol - k" and after that begin it regularly utilizing "saposcol - l".
In the event that saposcol still doesn't run, at that point you have to begin it in discourse mode. Login with utilize adm and take after the means underneath,
saposcol - d
Authority > clean
Authority > quit
saposcol - k to stop the authority.
Before restarting
saposcol - d
Authority > abandon (You ought to get a message-Shared memory erased)
Authority > quit
compact disc/usr/sap/tmp
mv coll.put coll.put.sav
compact disc
saposcol
"coll.put",if this record contains the old shared memory and ought to be erased keeping in mind the end goal to get a new beginning (Check SAP Note 548699, point 7). In the event that you are unsuccessful in clearing shared memory, please attempt the accompanying orders to clear the common memory:
$ saposcol - kc
$ saposcol - f
In the event that this likewise flops, at that point you have to restart the framework from OS level and appears like additionally require another adaptation of saposcol (Check SAP Note 19227).
IBM iSeries i5/(OS/400, OS/390):
- Check consents of index '/usr/sap/tmp' and the record 'saposcol.exe', it ought to be 4755 and proprietor must be root in sapsys gathering. Check SAP Note 790639. In the wake of relegating consents you can keep running from OS order line utilizing 'SAPOSCOL - l'. To demonstrate the status utilize 'SAPOSCOL - s' and to stop the procedure utilize 'SAPOSCOL - k'. You can likewise run the procedure by presenting an occupation in OS level utilizing
CALL PGM(SAPOSCOL) PARM(- l)
It presents the activity in work line QBATCH in library QGPL.
- In iSeries, you may encounter bizarre information while investigating CPU usage utilizing tcode ST06/OS06. Indeed, even you are utilizing various CPU's, SAPOSCOL may just report CPU use for the primary CPU. Additionally once in a while you will discover CPU usages announced over 100% in a few interims, in the event that you are running SAP example in an uncapped segment where different sensible segments are utilizing a mutual processor pool. In this circumstance, make certain that CPU use detailed for CPU number 0 is the normal use for all CPU's being utilized as a part of the framework. On the off chance that you need to see shared CPU parcel data, apply bolster bundles according to SAP Note 994025 including following patch levels
6.40 disp+work bundle (DW): 182 SAPOSCOL: 69
7.00 disp+work bundle (DW): 109 SAPOSCOL: 34
By applying these patches and bolster bundles into the framework, new exchanges, OS06N, ST06N, and OS07N are accessible to see extra data in two segments titled "Host framework" and "Virtual framework". These incorporate data about the segment compose and the accessible and expended CPU in the present segment and also in the common processor pool. In this way, on the off chance that you are an iSeries client and your SAPOSCOL isn't running, most noteworthy likelihood is that you have to put the most recent piece and saposcol fix. (SAP Note 708136 and 753917)
- Another situation in iSeries, when your saposcol isn't running, and you can't begin it from ST06/OS06. Issue may be with the approval list R3ADMAUTL was not precise. You can fathom it by along these lines,
1) Remove QSECOFR *ALL X
2) Change *PUBLIC from *USE to *EXCLUDE
3) Add R3OWNER *ALL X
Presently you can begin saposcol utilizing the tcode ST06/OS06. And furthermore you can begin the procedure from charge line,
CALL PGM(/SAPOSCOL PARM('- l')
On the off chance that this does not take care of the issue check if the two projects QPMLPFRD and QPMWKCOL in library QSYS have *USE-expert allocated for client R3OWNER (SAP Note: 175852). If not then you need to run the accompanying charges:
GRTOBJAUT OBJ(QSYS/QPMLPFRD) OBJTYPE(*PGM) USER(R3OWNER) AUT(*USE)
GRTOBJAUT OBJ(QSYS/QPMWKCOL) OBJTYPE(*PGM) USER(R3OWNER) AUT(*USE)
At that point you ought to confirm if the client R3OWNER is a piece of specialist list R3ADMAUTL (SAP Note: 637174). After this on the off chance that you get the mistake "SAPOSCOL not running? (Shared memory not accessible), at that point take after the means beneath,
1) Remove the mutual memory (coll.put) according to SAP Note: 189072. 'coll.put' area is: '/usr/sap/tmp'.
2) End the occupations QPMASERV, QPMACLCT, QYPSPFRCOL and CRTPFRDTA in QSYSWRK if running.
3) Delete the brief client space, WRKOBJ OBJ(R3400/PERFMISC*) OBJTYPE(*USRSPC)
4) ENDTCPSVR *MGTC
5) CALL QYPSENDC PARM('*PFR ' ') [There are 6 spaces after *PFR and there are 6 spaces making up the second parameter]
6) ENDJOB JOB(xxxxxx/QSYS/QYPSPFRCOL) OPTION(*IMMED) SPLFILE(*YES) [This summon must be kept running for all QYPSPFRCOL employments found on the framework regardless of whether they appear with *OUTQ as their status]
7) ENDJOB JOB(xxxxxx/QSYS/CRTPFRDTA) OPTION(*IMMED) SPLFILE(*YES) [This summon must be kept running for all CRTPFRDTA employments regardless of whether they appear with *OUTQ as their status]
8) RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*USRSPC) NEWOBJ(QPFRCOLDTX)
9) RNMOBJ OBJ(QUSRSYS/QPFRCOLDTA) OBJTYPE(*DTAQ) NEWOBJ(QPFRCOLDTX) [This protest might exist at this time]
10) CALL QYPSCOLDTA *note This program will make another *USRSPC. After accumulation administrations is begun there ought to be another *DTAQ.
11) Start accumulation administrations utilizing GO PERFORM, pick 2, and select 1; OR CALL QYPSSTRC PARM('*PFR ' '*STANDARDP' ' ') [There are 6 spaces after *PFR and there are 6 spaces making up the second parameter]. Or then again, Start gathering administrations from Operations Navigator.
12) STRTCPSVR *MGTC
13) End and restart Operations Navigator if running. See IBM approved program investigation report (APAR) SE12188 for more data.
14) Now begin SAPOSCOL from ST06/OS06.
Windows System:
- Go to the Kernel organizer in charge line where you will discover saposcol.exe. Set full proprietor consent
for the document and organizer. At that point run saposcol - l (saposcol - d in exchange mode)
- You can likewise attempt Start/Stop SAPOSCOL benefit from Control Panel - > Administrative Tools - > Services (services.msc).
On the off chance that every other endeavor flop, at that point ensure you have the right form of SAPOSCOL. Get most recent SAPOSCOL from SAP Service Marketplace for your OS. Download the SAPOSCOL.SAR petition for your Kernel and spare in a registry. At that point STOP SAP and SAPOSCOL. Check for any Kernel library bolts and keep in mind to take library reinforcement. At that point run APYR3FIX and after that APYSAP. Check OSS Note 19466.
SAPOSCOL likewise can be ended because of little measure of interior memory designation. At the point when this memory filled step by step amid the runtime of SAPOSCOL, framework composes information outside the cushion. Subsequently the accompanying cushion is cleared and SAPOSCOL ends with a dump. Apply the accompanying patches with in any event the fix levels determined underneath:
SAP Release 640: SAPOSCOL fix level 100 and DW fix level 293
SAP Release 700: SAPOSCOL fix level 75 and DW fix level 151
SAP Release 701: SAPOSCOL fix level 18 and ILE fix level 53
SAP Release 710: SAPOSCOL fix level 36 and ILE fix level 161
SAP R
No comments:
Post a Comment