CCMS MOnitoring for SAP 3.1i

[Former Member]

HI experts,

I am getting error while registering sapcm3x agent in 3.1i systems.

Can anyone help me who has experiance in installing sapcm3x ....

dev

Edited by: Dev S on May 26, 2010 11:10 PM

Edited by: Dev S on May 26, 2010 11:10 PM

[Former Member]

Problem not resolved but i leave this monitoring

[Former Member]

Here is the complete log

Wed May 26 12:07:32 2010

ERROR: OS monitoring: Error-254 Can not create MTE: no more space: no more PERFORMANCE slots available

ERROR: OS monitoring: Error-102 number range 0 not allowed for TID [<invalid TID>: Monitoring Context].

Here is the complete log

ind the log:

Tue May 25 16:15:29 2010

INFO: managed component: SMV (SAPSYSTEM=100),managed by central system SMV

INFO: trying to start

sapcm3x -DCCMS

INFO: parent exits.

Tue May 25 16:15:30 2010

INFO: CCMS Agent is registered at the following central systems:

INFO: **********************************************************

INFO: ********************* SMV **********************

INFO: **********************************************************

Semaphore handling enabled.

INFO:

CCMS version 20040229, 64 bit, single threaded, Non-Unicode

compiled at Sep 4 2006

systemid 370 (SUN on SPARC CPU with Solaris 2.2)

relno 4640

patch text patch collection 2006/4, OSS note 914721

patchno 2273

intno 0

running on sun109 SunOS 5.9 Generic_122300-19 sun4u

pid 9329

INFO: Reconnected to Monitoring Segment [SAP_CCMS_sun109_local]

INFO: updating shared memory runtime information of sapcm3x

INFO: Loading static lib rfcoslib with trace level 0.

RFCOSLIB: INFO: current trace level is 1

RFCOSLIB: INFO: initialize Semaphore Handling...

RFCOSLIB: INFO: ...successful...

RFCOSLIB: searching for Process Monitoring configuration in /usr/sap/tmp/dev_proc

RFCOSLIB: searching for Process Monitoring Templates in /usr/sap/tmp/procmon/

RFCOSLIB: INFO: OS monitoring: Can not open configuration Directory /usr/sap/tmp/procmon for reading

/usr/sap/tmp/procmon does not exist or cannot be opened.

Files for Process Monitoring in /usr/sap/tmp/procmon are ignored.

RFCOSLIB: INFO: Trying to Register Objects

RFCOSLIB: INFO: Operating System Version: SunOS sun109 5.9 Generic_122300-19 sun4u

ERROR: OS monitoring: Error-254 Can not create MTE: no more space: no more PERFORMANCE slots available

ERROR: OS monitoring: Error-102 number range 0 not allowed for TID [<invalid TID>: Monitoring Context].

RFCOSLIB: INFO: OS monitoring: Operating System Tree created

INFO: Loading static lib rfcoslibOS07 with trace level 0.

Tue May 25 16:15:30 2010

RFCOSLIB: INFO: current trace level is 1

INFO: Use of static lib nwaglib suppressed

INFO: Loading static lib ccmctlib with trace level 0.

INFO: Loading static lib alloglib with trace level 0.

ALLOGLIB: INFO: Reading logsave.bin

ALLOGLIB: INFO: Reading sapccmsr.ini

ALLOGLIB: INFO: ok, no configuration for Logfile Monitoring. No entry LogFile <file_name> in configuration file sapccmsr.ini found

ALLOGLIB: INFO: using template directory /usr/sap/tmp/logmon for log file monitoring.

INFO: Working directory is /usr/sap/tmp/sapcm3x

INFO: Configuration file sapccmsr.ini opened.

INFO: PlugIn: ok, no Dynamic Libraries defined as PlugIn in sapccmsr.ini

INFO: PlugIn manager initialized successfully.

INFO: RFC service -DCCMS registered at SMV gateway sapgw28 on host sapsmvv

Tue May 25 16:15:30 2010

CCMCTRL: INFO: CcmcntrlInitFilePermission read the following Path List

CCMCTRL: ListLength 0

CCMCTRL: INFO: current trace level is 1

Tue May 25 16:16:30 2010

INFO: [SMV:100:CSMREG] connected to SMV, host sapsmvv, System Nr. 28, traceflag [ ]

INFO: SMV release is 701 , (kernel release 701 ), CCMS version 20060508

INFO: Central ICT-based monitoring cache not configured in SMV on server sapsmvv.

INFO: Pushing data into ICT-Cache disabled.

INFO: Switch on ICT-Cache in SMV with profile parameter alert/cache/size_MB.

Tue May 25 16:19:31 2010

ERROR: OS monitoring: Error-254 Can not create MTE: no more space: no more PERFORMANCE slots available

ERROR: OS monitoring: Error-102 number range 0 not allowed for TID [&lt;invalid TID&gt;: Monitoring Context].

Can you help connected to SMV, host sapsmvv, System Nr. 28, traceflag [ ]

INFO: SMV release is 701 , (kernel release 701 ), CCMS version 20060508

INFO: Central ICT-based monitoring cache not configured in SMV on server sapsmvv.

INFO: Pushing data into ICT-Cache disabled.

INFO: Switch on ICT-Cache in SMV with profile parameter alert/cache/size_MB.

Tue May 25 16:19:31 2010

ERROR: OS monitoring: Error-254 Can not create MTE: no more space: no more PERFORMANCE slots available

ERROR: OS monitoring: Error-102 number range 0 not allowed for TID [<invalid TID>: Monitoring Context].

[cris_hansen]

Hi Dev S,

I hope this is not too late...

For the error message "Error-254 Can not create MTE: no more space" you have to increase the agent monitoring segment by increasing the value of the instance profile parameter alert/MONI_SEGM_SIZE, as described in SAP note 731165.

After this you have to stop and start the CCMS agent again.

Best regards,

Cristiano

[Former Member]

Hi Chris,

It looks like the problem is somewhere else.

I have increased the parameter alert/MONI_SEGM_SIZE in my CEN but still getting the same error.

I also tried putting this parameter in my satellite system whihc is 3.1i system and then reinstalled the agent but still same error.

so finally restarted the systems both CEN and satellite....but agian same result.

can you suggest anythng with this ? I really need to resolve this soon.

here is the log again :

Fri Jun 4 19:54:36 2010

CCMCTRL: ERROR: CcmShowFile: fopen() failed

Fri Jun 4 19:57:45 2010

ERROR: OS monitoring: Error-254 Can not create MTE: no more space: no more slots available

ERROR: OS monitoring: Error-102 TID <PERF>:SMV :MoniInfra_sun109_local:5:16244:0:0 not found in monitoring segment.

Thanks for helping .

Dev

[former_member4224]

Hi Dev S ,

The Error-102 can be related to the actual shared memory.

Make a backup of AL* files in /usr/sap/<SID>/<instance>/log/.

Stop the instance, remove these files from this directory, start the

instance and try start the agent again.

The AL* files must be deleted before instance start in order

the original state of the shared memor is not restored.

The Error-254 is related to space segment at parameter alert/MONI_SEGM_SIZE.

cheers, Clebio