unable to start SAPCCMSR agent

[Former Member]

Hi Folks,

System details:

Kernel release  is 741 ,patch number is  24 and kernel make variant  is 741_REL

OS is linux x86_64

DB is oracle 11.2.0.3.0 - 64bit

When we try to start the sapccmsr agent  after kernel upgrade to 741 ,we get the below error when we try to start the sapccmsr agent for the host

ERROR: Cannot open monitoring segment 99 rtc = 255

Last reported error: [255]  Attach to shared memory (SAPSYSTEM=99) failed. ShmAlCreate (SHM_ATTACH) returns error 1, errno=13

INFO: dsr: dsrlib unloaded.

Further tried restarting the hostagent too , but still getting the same  above error.

Further i could not get SAP note related to the above error (specifically errno=13)

Please let me know if you have any solutions

Regards

Ram

[Former Member]

Hi All,

The issue is resolved .The ccmsr agent is running fine

The below workarounds were done in the DB host .

Followed the below KBA

1627564 - SAPOSCOL: Clearing Shared Memory and Updating Saposcol

Further gave cleanipc 99 remove

99 belongs to SAPOSCOL

root@xyz # pwd

/usr/sap/XXX/SYS/exe/run

root@#xyz ./cleanipc 99 remove

Regards

Ram

[Former Member]

Dear Ram,

could you please run command:

ps -ef | grep sapccmsr

With best regards,

Alexander

[alwina_enns]

Dear Ram,

in kernel release 7.41 there is always an integrated agent in sapstartsrv started by default. Which sapccmsr you are trying to start, should it monitor a host or a java instance? From SAPSYSTEM=99 I assume, it should monitor host? If SAPHOSTAGENT is running on the server, then it has already started an integrated sapccmsr agent and you will not be able to start the second sapccmsr for the segment 99.

regards,
Alwina

[Former Member]

Hi Ram,

I had the same issue.What i did was stopped the system cleanly with shared memories freed.

Then i started the sapccm4x agent.Once the agent was running, i started the SAP instance.

Thanks

Sabya

[Former Member]

Can you attach full log file?

[former_member188883]

Hi Ram,

The error you face is due to system not able to create shared memory segments.

Could you execute cleanipc <Nr> remove

and then check the results again.

Nr is SAP system instance number.

Hope this helps.

Regards,

Deepak Kori

[Former Member]

'cleanipc' cannot be used while an instance is running because it will cause the application server to crash.

Will run it after apps is taken down !!!

Regards

Ram

[Sriram2009]

Hi Ram

Could you refer the SAP Note

1870449 - Not starting CCMS agents

BR

SS

[Former Member]

Hi Ram,

Please check the following note.

1767151 - CCMS: sapccm4x agent fails after ABAP instance (re-)start

[Former Member]

Hi Adil,

The SAP note did not help  in the above issue

Regards

Ram