More trouble with registering sapccmsr and EYE CATCH error

[Former Member]

Hello all,

I saw that this was a topic in an earlier thread. That thread was very helpful for troubleshooting, but it seems I have everything properly set up and patched, but I am still receiving the dreaded EYE CATCH error. The system is a Unicode dual-stack XI system. Here are the details:

sapccm4x registers with no problems.

sapccmsr results in the following:

<b>LE06201:xitadm 160% ./sapccmsr -j2ee -R pf=/sapmnt/XIT/profile/START_DVEBMGS00_LE06201

INFO: CCMS agent sapccmsr working directory is /usr/sap/ccms/XIT_00/sapccmsr

INFO: CCMS agent sapccmsr config file is /usr/sap/ccms/XIT_00/sapccmsr/csmconf

INFO: Central Monitoring System is [XIT]. (found in config file)

INFO: additional Central Monitoring System is [SLM]. (found in config file)

additional CENTRAL system y/[n] ? :

INFO: found ini file /usr/sap/ccms/XIT_00/sapccmsr/sapccmsr.ini.

INFO: Checking Distributed Statistical Records Library dsrlib.so

INFO: DSR: Path /usr/sap/ccms/dsr for Distributed Statistical Records.

INFO: checking version an Unicodeness of dsrlib.so

INFO: DSR: Dynamic Library dsrlib.so (version 22) successfully loaded.

INFO:

CCMS version 20040229, 64 bit, multithreaded, Unicode

compiled at Jul 7 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text patch collection 2007/4, OSS note 1013331

patchno 191

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

pid 26318

profile /sapmnt/XIT/profile/START_DVEBMGS00_LE06201

ERROR: Cannot open Monitoring Segment 0 rtc = 245

Last reported error: [249] CCMS monitoring segment has wrong EYE CATCH. It seems to be created as non-unicode segment.

This program runs as unicode. Please use non-unicode version

INFO: dsr: dsrlib unloaded.

EXITING with code 1</b>

Based on the information in the earlier thread, I checked that the files are consistent in their Unicodeness:

<b>LE06201:xitadm 35% pwd

/sapmnt/XIT/exe

LE06201:xitadm 165% sapccm4x -v

CCMS version 20040229, 64 bit, multithreaded, Unicode

compiled at Jul 7 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text patch collection 2007/4, OSS note 1013331

patchno 191

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

LE06201:xitadm 166% sapccmsr -v

CCMS version 20040229, 64 bit, multithreaded, Unicode

compiled at Jul 7 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text patch collection 2007/4, OSS note 1013331

patchno 191

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

LE06201:xitadm 167% saposcol -v

SAPOSCOL version COLL 20.94 640 - V3.73 64Bit, 64 bit, single threaded, Non-Unicode

compiled at Jul 7 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text COLL 20.94 640 - V3.73 64Bit

patchno 191

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

LE06201:xitadm 107% disp+work -v | more

-

---

disp+work information

-

---

kernel release 640

kernel make variant 640_REL

DBMS client library OCI_920

DBSL shared library version 640.00

compiled on SunOS 5.8 Generic_117350-38 sun4u

compiled for 64 BIT

compilation mode UNICODE

compile time Oct 29 2006 21:30:34

update level 0

patch number 155

source id 0.155

-

---

supported environment

-

---

database (SAP, table SVERS) 610

620

630

640

DBMS server

ORACLE 9.2.0..

ORACLE 10.1.0..

ORACLE 10.2.0..

operating system

SunOS 5.8

SunOS 5.9

SunOS 5.10

LE06201:xitadm 169% pwd

/sapmnt/XIT/exeU

LE06201:xitadm 170% sapccm4x -v

CCMS version 20040229, 64 bit, multithreaded, Unicode

compiled at Jul 7 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text patch collection 2007/4, OSS note 1013331

patchno 191

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

LE06201:xitadm 171% sapccmsr -v

CCMS version 20040229, 64 bit, multithreaded, Unicode

compiled at Jul 7 2007

systemid 370 (Solaris on SPARCV9 CPU)

relno 6400

patch text patch collection 2007/4, OSS note 1013331

patchno 191

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

LE06201:xitadm 172% saposcol -v

SAPOSCOL version COLL 20.88 640 - V3.60 64Bit, 64 bit, single threaded, Non-Unicode

compiled at Apr 16 2005

systemid 370 (SUN on SPARC CPU with Solaris 2.2)

relno 6400

patch text COLL 20.88 640 - V3.60 64Bit

patchno 68

intno 20020600

running on LE06201 SunOS 5.9 Generic_122300-02 sun4us

LE06201:xitadm 111% disp+work -v | more

-

---

disp+work information

-

---

kernel release 640

kernel make variant 640_REL

DBMS client library OCI_920

DBSL shared library version 640.00

compiled on SunOS 5.8 Generic_117350-38 sun4u

compiled for 64 BIT

compilation mode UNICODE

compile time Oct 29 2006 21:30:34

update level 0

patch number 155

source id 0.155

-

---

supported environment

-

---

database (SAP, table SVERS) 610

620

630

640

DBMS server

ORACLE 9.2.0..

ORACLE 10.1.0..

ORACLE 10.2.0..

operating system

SunOS 5.8

SunOS 5.9

SunOS 5.10</b>

Anyone have any ideas why I am unable to register the sapccmsr? Thanks in advance for your help.

Best Regards,

Warren Chirhart

[Former Member · Accepted solution]

Hi,

In the command <b>./sapccmsr -j2ee -R pf=/sapmnt/XIT/profile/START_DVEBMGS00_LE06201</b> you have given the START profile.

Just give the instance profile that will be in the same path with the format <b><SID>_DVEBMGS00_LE06201</b> in the command.

Hope this helps

Do reward points if it helps.

Regards,

Nayana

Message was edited by:

Nayanalakshmi Bhat

[Former Member · Accepted solution]

Hello Nayana,

Thank you for your answer. I gave you some points for the information, but unfortunately the error is exactly the same. BTW, the START profile works just fine with the registration. We have used it for the sapccm4x on several systems. I can't remember which one SAP recommends using, though. I will have to look at the documentation for that.

Best Regards,

Warren

[Former Member]

This issue is resolved. It was the java library. This comes packaged with the SAR file for the CCMS agents, but needs to be placed into the j2ee/os_libs directory. Java has to be stopped before replacing the file. Once that was done, the eye catch problem disappeared.

OSS Note exists (sorry, don't have the number) which stated that the 200701 release of the CMMS patch contained only the non-unicode version of this file for both the Unicode and Non-Unicode SAR packages.

[Former Member]

Hi,

I'd just like to make some additional comments.

The issue comes from the "jmon.dll" library which is non-unicode. You have to download the latest SAR archive of the SAP CCMS agents from the Service Marketplace and update your agents as well as your "jmon.dll" library by replacing the EXE and DLL files.

The agent files are located under:

/usr/sap/<SID>/<INSTNACE>/exe

The "jmon.dll" library is located under:

/usr/sap/<SID>/<INSTNACE>/j2ee/os_libs

Most probably you would have to shut down / restart the instance after you update the library so the changes take effect.

You can find the latest SAP CCMS agents SAR archive in SMP under:

https://websmp109.sap-ag.de/swdc

Then browse to:

/SAP Support Packages/SAP Support Packages and Patches/Entry by Application Group/SAP NetWeaver/SAP NETWEAVER/SAP NETWEAVER <version>/Entry by Component/Application Server ABAP/SAP KERNEL <version> <32-BIT | 64-BIT> UNICODE/<OS>/#Database independent/ccmagent_<agent_version>.sar

Hope this helps.

Kind regards,

Rosen