problem start CCMS monitoring

[Former Member]

Hi, I apply upgrade Kernel 720 in the system 700. Try startup the CCMS agent but show message error:

ERROR: Cannot open Monitoring Segment 0 rtc = 245

Last reported error: [249]  CCMS monitoring segment has wrong EYE CATCH: CCMS monitoring segment belongs to a non-ABAP instance.

SAPCCM4X of release 7.10 is to be used only to monitor ABAP or Double Stack instances of release 7.10.

EXITING with code 1

The run command is:

sapccm4x -R pf=/usr/sap/CD1/SYS/profile/START_DVEBMGS00_cd1ds001

Best Regards,

EDRS

[sunny_pahuja2 · Accepted solution]

Hi,

Check SAP Note 1368389 - Re-activating legacy RFC-communication for CCMS Agents

Thanks

Sunny

[Former Member · Accepted solution]

Hi Sunny, apply the note 1368389 buth show same error.

Best Regards,

EDRS

[former_member4224]

Hello Ramones,

You are using the following command:

sapccm4x -R pf=/usr/sap/CD1/SYS/profile/START_DVEBMGS00_cd1ds001

Note that you should use the instance profile and not the start profile in this command.

The return code 245 is because the shared memory cannot be accessed by the sapccm4x agent. There are too many reasons to this error:

1) agent unicode and shared memory non unicode (or vice-versa);

2) shared memory corrupted or inconsistent;

3) access authorization;

some hints to solve the problem:

1) make sure about the code conversion from SAP and agent;

2) Stop the system and run "clenaipc  <isntance number> remove" if this is a UNIX system (Windows should be an OS restart) in order to cleanup the current shared memory;

3) make sure that no sapccmsr agent is also running at OS level with the same instance profile;

4) as you are running a sapccm4x agent you should disable the agent running integrated with sapstartsrv process. To setup this you should set "ccms/enable_agent = 0"  in the instance profile. With this you will avoid two agents doing the same task (what also can corrupt the memory).

You also should restart the sapstartsrv process after this change.

After these steps you can start up the system again and try to start up the agent.

Regards

Clebio

[Former Member]

Hi,

Try to clean shared memory segment be following command.

sapccm4x -initshm pf=<profile path>

sapccmsr -j2ee -initshm pf=<profile path>

If still problem remain same, please try to stop your sap host agent and start your agent and again start your host agent.

Regards,

Dinesh

[Former Member]

Hello,

"CCMS monitoring segment has wrong EYE CATCH"

Please check Unicod type in system! (System->Status->SAP System data->Unicode System  Yes/No?)

EYE CATCH error: the JMON library creates the segment with Unicode . Then later an agent is installed, but with the other Unicode-type. Then the agent cannot write the segment, because it has different Unicode typke. In this case, no sapccmsr.log is created, because this log can only be created if the agent can be started.

Please check SAP notes:

#1746016 - CCMS: damaged monitoring segment reports eyecatch error

I would like to suggest notes too:

#1081694 - CCMS: Local system missing from "SAP J2EE Monitor Templates"

#1667336 - CCMS Monitoring with Kernel 7.20(DCK)

#1652660 - UnsatisfiedLinkError or InvocationTargetException in JMonAPI

and the online dukumnetation:

-Installing/Registering the CCMS Agents for Experts

http://help.sap.com/saphelp_nw70/helpdata/en/8b/f64352e1bfbd4eb43e432860504a1c/frameset.htm

The sapstartsrv could not connect to the CCMS shared memory segment. That
can mean that:
1) the segment is not created, or
2) the sapstartsrv process is still not able to reconnect to it.

Please implement this note too:
#1652660 - 'UnsatisfiedLinkError or InvocationTargetException in'
This will make sure, that You are using the latest Jmon library, that
still can cause this problem.

After it please execute the cleanipc command *only* when the sapstartsrv
is not running any more (it should be killed befor,check it on OS leve )
else the connection problem will

Please have a look at in how to clean the SHM segment:

-SAPOSCOL: Clearing Shared Memory and Updating Saposcol

http://scn.sap.com/people/brendan.ocallaghan/blog/2011/09/08/saposcol-clearing-shared-memory-and-upd...

BR

T

[Former Member]

We faced this issue because we mistakenly tried to register sapccmsr agent instead of sapccm4x agent.

It was resolved by taking following actions:

1. RZ21 -> Agents for Remote Systems.

2. If you see sapccmsr agent then deregister it.

          sapccmsr -U [-j2ee] pf=<instance profile>

3. RZ21 -> Agents for Remote Systems. Node should not be visible now.

4. cd /usr/sap/<SID>/<INSTANCE>/log

          ls -lrt AL*

          rm AL*

          rm -r sapccmsr sapccm4x

5. Stop SAP application server.

          stopsap

          sapcontrol -nr <instance no.> -function StopService

          cleanipc 01 remove

          ipcs | grep <sidadm>

          ipcrm -m XXXX (NOTE: XXXX represents the “shmid”)

          ipcrm -s XXXX (NOTE: XXXX represents the “semid”)

6. Register sapccm4x agent using instance profile. I see you used start profile earlier.

          sapccm4x -R pf=<instance profile>

7. startsap

8. RZ21 -> Agents for Remote Systems. You should see destination as “SAPCCM4X”.

Let me know this helps.

Regards,

Amol Thorat

[Former Member]

Hello EDRS,

Please check Unicod type in system! (System->Status->SAP System data->Unicode System  Yes/No?)

EYE CATCH error: the JMON library creates the segment with Unicode . Then later an agent is installed, but with the other Unicode-type. Then the agent cannot write the segment, because it has different Unicode typke. In this case, no sapccmsr.log is created, because this log can only be created if the agent can be started.

I would like to suggest note to get more information:

#1746016 - CCMS: damaged monitoring segment reports eyecatch error

Installing/Registering the CCMS Agents for Experts

http://help.sap.com/saphelp_nw70/helpdata/en/8b/f64352e1bfbd4eb43e432860504a1c/frameset.htm

BR

Tamas