on 07-03-2014 5:41 AM
Dear colleagues,
I have a development SAP ERP 60 EHP7 instance up and running. We would like the ST06 in the developemnt instance to report previous hours and history data. The only way to get this information is getting the CCMS agent installed. The operating system is HP-UX 11.31 so we should use sapccm4x. When I run sapccm4x -r pf=<path to profile> and enter all the info required I got the following error:
please enter password for [DEV:000:CSMREG]: *********
Try to connect ...
INFO: [DEV:000:CSMREG] connected to DEV, host saperpdefa, System Nr. 00, traceflag [ ]
INFO: DEV release is 740 , (kernel release 741 ), CCMS version 20060508
INFO: RFC logon info for [DEV:000:CSMREG] can be updated at any time with -R option:
sapccm4x -R <params>
INFO: Updated saprfc.ini in agent work directory /usr/sap/DEV/DVEBMGS00/log/sapccm4x
ERROR: Monitoring segment belongs to central system DEV
CCMS agent SAPCCM4X may only be run for remote segments
that do not belong to central system DEV
Therefore exiting....
I have installed this development instance for a customer and they want historical performance data. At the moment, they do not want to implement a CEN system to gather all the performance information for the SAP landscape. How should I do to get historical performance data for the development instance if I can not install the sapccm4x agent?.
I would appreciate your help.
Luis.
Hi,
Saposcol collects information on the 40 processes with the highest CPU load as well as other operating system data and displays a list sorted according to CPU load in transaction ST06 (OS07).
As of Saposcol version 20.75 (saposcol - version), it is possible to permanently collect information for certain processes, regardless of whether they are in the top 40 of the CPU list. However, to be able to use all of the functions, you have to install Saposcol Version 20.86 or higher.
A CCMS agent (sapccmsr or sapccm4x) is used to transfer the data collected by Saposcol to the CCMS monitor architecture (transaction RZ20) and display it under the 'Operating System' subtree ('Monitored Processes').
In this case, the CCMS agent also takes account of the Saposcol configuration files. Therefore, the configuration files (in addition to the name patterns) may still contain additional information that is relevant for the monitoring tree display (such as MTE classes, attribute groups and node names, for example).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
I just checked saposcol version and got this:
***********************************************************************
* This is Saposcol Version COLL 22.10 720 - V3.1.1 2014-02-07 HP-UX IA64
This saposcol version is newer than 20.86, but I can't get previous hours or history in st06. Also, have a look at the errors I get when saposcol is starting:
---------------------------------------------------------------------------------------------
SAPOSCOL version COLL 22.10 720 - V3.1.1 2014-02-07 HP-UX IA64, 64 bit, single threaded, Non-Unicode
compiled at May 27 2014
systemid 274 (HP (IA-64) with HP-UX)
relno 7200
patch text COLL 22.10 720 - V3.1.1 2014-02-07 HP-UX IA64
patchno 615
intno 20020600
running on saperpde HP-UX B.11.31 U ia64
chgno(local) 1496667
chgno(global) 1499300
PATCHES
DATE CHANGELIST PLATFORM PATCHTEXT
20081211 --- ALL Option -w support. Removed SizeOfRecord warning rt 130.
20090114 --- UNIX Log file permissions: 664.
20090203 --- UNIX Add. single instance check.
20090210 --- ALL Continue after EWA HW XML generation failure.
20090324 --- ALL Fix dynamic trace level switch.
20090512 --- ALL Usage of DIR_HOME as working dir.
20090512 1064069 UNIX Hardware XML permissions 660.
20090613 --- ALL Async HW info generation.
20090909 --- UNIX DIR_PERF, DIR_HOME, /var/tmp, ...
20090909 --- UNIX Group sapsys and smarter permissions of files
20091105 --- WINDOWS New Monitoring for VMware
20091210 --- ALL Performance improvement 'saposcol -xml'.
20100723 --- LINUX New Monitoring for VMware
20100812 --- ALL Improved kill option (-k).
20110111 --- UNIX col.put permissions: 664.
20110322 1235461 SUN Showing size for filesystem >2TB problem fixed.
20110502 --- WINDOWS Initial Monitoring for XEN
20110504 --- WINDOWS Monitoring for Hyper-V Dynamic Memory
20110509 --- ALL Renamed MTE trees to be consistent with CCMS agents.
20110525 1250238 IBM i CPU time, disk service & wait time, system values.
20110706 1607341 WINDOWS saposcol: determination of saposcol-directory (PerfDir)
20110713 --- SUN Reporting negative or 0 CPU utilization fixed.
20110916 --- WINDOWS Initial Monitoring for KVM
20110922 1630624 IBM i Patch collection September 2011.
20111011 1280958 LINUX Build-in vm-dump-metrics
20111020 --- WINDOWS Improved Monitoring for KVM/Xen
20111021 1282052 LINUX Amazon Monitoring: First Steps
20120320 --- WINDOWS Monitoring for Amazon Cloud
20120803 1744043 IBM i Patch collection August 2012.
20120830 --- WINDOWS Multiple fixes for Hyper-V and Amazon monitoring
20121114 --- LINUX Support Amazon data collector monitoring
20121115 1366862 WINDOWS Amazon monitoring for AWS Data Provider
20121204 1380761 IBM i Patch collection December 2012.
20121219 1376949 ALL Added -ignorebackup option to skip reading coll.put
20121119 1376982 ALL Added -tr[lines] option for configuring trace level auto-lowering
20130213 --- WINDOWS Amazon storage throughput metric issue fixed
20130430 --- LINUX Added missing VMware metrics
20130718 --- WINDOWS Improved virtualization detection
20130806 --- ALL New memory reporting as part of CCM metrics (version 22.10)
20130815 --- WINDOWS Termination by high PIDs fixed
20131015 --- WINDOWS Windows Server 2012 R2 Hyper-V
20131127 --- WINDOWS Windows Server 2012 R2 guest OS
20131218 --- LINUX Unisys Partitions, Linux Container
20140417 --- WINDOWS Patch Collection 04/2014
---------------------------------------------------------------------------------------------
13:55:35 01.07.2014 LOG: Profile : /usr/sap/hostctrl/exe/host_profile
13:55:35 01.07.2014 LOG: Saposcol Version : [COLL 22.10 720 - V3.1.1 2014-02-07 HP-UX IA64]
13:55:35 01.07.2014 LOG: Working directory : /usr/sap/tmp
13:55:35 01.07.2014 LOG: Operating system : [HP-UX saperpde B.11.31 U ia64 0630281136]
13:55:35 01.07.2014 LOG: Hardware model : [ia64 hp Integrity Virtual Partition]
13:55:35 01.07.2014 LOG: Process Monitoring active.
13:55:35 01.07.2014 LOG: Searching for Process Monitoring Templates in /usr/sap/tmp/procmon
13:55:35 01.07.2014 LOG: The following processes will be monitored:
13:55:35 01.07.2014 ERROR: pfhpuxvirt.c 227: HPVMGuestLib_UpdateInfo(): return code 6
13:55:35 01.07.2014 LOG: Shared Memory Size: 2051872.
13:55:35 01.07.2014 LOG: Shared Memory was created by process:23222
13:55:35 01.07.2014 LOG: ==== Collector submitted. This is the child process after fork()=====
13:55:35 01.07.2014 LOG: Connected stderr to log_file
13:55:35 01.07.2014 LOG: Collector daemon started
13:55:36 01.07.2014 LOG: read coll.put Thu May 29 15:34:55 2014
13:55:36 01.07.2014 LOG: Collector PID: 23224
Failed to open dynamic memory driver, error: No such file or directory.
13:56:36 01.07.2014 ERROR: pfhpuxvirt.c 227: HPVMGuestLib_UpdateInfo(): return code 6
We are using vPar's not HPVM.
I'd appreciate your help.
Luis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.