CCMS monitoring segment has wrong eyecatch

[Former Member]

Hello Gurus,

in our BI dual-stack system (ABAP 7.01 SP12, Kernel 7.20 SP300) we have ccms monitoring enabled with ccms agents.

After the upgrade of solution manager to 7.1 we get the following errors from the ccms agents.

sapccm4x

ERROR: Cannot open monitoring segment 1 rtc = 245

Last reported error: [249]  CCMS monitoring segment has wrong eyecatch: CCMS monitoring segment belongs to a non-ABAP instance.
In current SAP Kernel release SAPCCM4X must be used to monitor ABAP or Double Stack instance only.

sapccmsr

ERROR: Cannot open monitoring segment 1 rtc = 245

Last reported error: [249]  CCMS monitoring segment has wrong eyecatch. Possible causes:
     a. CCMS monitoring segment belongs to an ABAP or Double Stack instance.
     b. CCMS monitoring segment was created by a release other then 7200.

We used ccms agents 7.20 SP413, tried UC and NU.

It is not possible to reregister the agents.

We tried, unicode, non-unicode, delete agent at solman, but we get always the same error.

has someone a suggestion?

Following notes we checked without success: 1163719, 1029770, 1013331

[former_member191911 · Accepted solution]

Hi Christian,

Please have a look at this note: Note 1746016 - CCMS: damaged monitoring segment reports eyecatch error

Kind regards,

Mark

[Former Member · Accepted solution]

Hi,

the Note 1746016 was the sopution for sapccm4x agents. But the sapccmsr agent get still the following error:

ERROR: Cannot open Monitoring Segment 1 rtc = 245

Last reported error: [249]  CCMS monitoring segment has wrong eyecatch. Possible causes:
     a. CCMS monitoring segment belongs to an ABAP or Double Stack instance.
     b. CCMS monitoring segment was created by a release other then 7200.

We are now at kernel 7.20 401. sapccm4x agent run fine.

Do we need the sapccmsr agent, too? BI is a dual-stack.

regards

Chris.

[former_member191911 · Accepted solution]

Hi Chris,

Since you get this message: monitoring segment was created by a release other then 7200

I think it's good to have the sapccmsr agent updated as well to a 7.20 release.

Kind regards,

Mark

[Former Member · Accepted solution]

sapccmsr is 7.20, thats the point

CCMS version  20060508, 64 bit, multithreaded, Non-Unicode

      compiled at   Jan 15 2013

      systemid      324 (IBM RS/6000 with AIX)

      relno         7200

      patch text    patch collection 2012/1, OSS note 1453112, PL 401

INFO Runtime:

      running on    swe130029 AIX 1 6 00F6180D4C00

      running without profile

[Former Member · Accepted solution]

Please read carefuly the following notes:

Note 1667336 - CCMS Monitoring with Kernel 7.20 (DCK)

Note 1119735 - CCMS agents: Upgrade of monitored systems from 7.0 to 7.1

Regards,

Roman

[bin_sun · Accepted solution]

As you are using Solman 7.1,

I think you'd better use integrated CCMS agent,

but not old type sapccm4x.

[former_member206552]

Hi Christian,

we had the same problem where by we did a kernel upgrade and afterwards the sapccm4x agent did not start anymore, we recieved the same error.

when you check the logs of smicm you should see

errors in smicm are:

ERROR => IcmAlReportData: AlReportPerfValue failed (rc=102)

[icxxalrt_mt.

1412]

ERROR => Alerting error 102: TID [<invalid TID>: Monitoring Context]

notfound in monitoring segment. [icxx

Note 1652660 - UnsatisfiedLinkError or InvocationTargetException in JMonAPI

if this is the same problem implement the corrections above

best regards

marius