Skip to Content

Introduction and warning

Some basis consultants faced with the problem described in note 903220 (Dump CONVT_OVERFLOW), and so did I. Unfortunately, the description of the note is out of date and not applicable for many systems. I have written this post to share my experience that possibly can help you. Bear in mind that this post does not substitute the note and it can be used as a clue to the note. I performed actions mentioned further on Solaris SPARC platform and SAP Solution Manager 7.01 SPS30 (Kernel 7.21) and SAP Host Agent v720.3.81, be careful of using this post for another platform, especially for IBM!

Problem description

Job SAP_COLLECTOR_FOR_PERFMONITOR falls with the status “Canceled”. You see many dumps in ST22 with the following text:

Overflow when converting from “-74188727”

The program “RSHOST2M” was started as a background job.

Job Name……. “SAP_COLLECTOR_FOR_PERFMONITOR”

Job Initiator.. “DDIC”

Job Number….. 10001500

The termination is caused because exception “CX_SY_CONVERSION_OVERFLOW” occurred in procedure “LOG_ON_OSMON” “(FORM)”, but it was neither handled locally nor declared in the RAISING clause of its signature.

Using key words from the dump, you have found note 903220, but it is too old for you system and some paths cannot be found.

Let’s get down to business

Logon onto server with user root and change directory to /usr/sap/hostctrl/exe/ , give the command “saposcol -kc” as described in the note.

Download the latest SAP archive with Host Agent for your platform and unpack it.

/wp-content/uploads/2013/03/1_194842.jpg

/wp-content/uploads/2013/03/2_194852.jpg

/wp-content/uploads/2013/03/3_194853.jpg

Remove coll.put file in accordance with the second step of the note.

rm /usr/sap/tmp/coll.put

Then update your Host Agent (Note 1031096) that includes saposcol.

saphostexec -install

/wp-content/uploads/2013/03/4_194855.jpg

Giving the command saposcol –l (step 3 of the note) is unnecessary because it will be started right after Host Agent installation. Check that saposcol is running (ps –ef |grep saposcol)

Go to ABAP-part

Start ST03 tcode. Here you can see that the path from the note is different to the path of your system, i.e. in the note the following path is given:

Goto -> Performance database -> Contents of Database

In fact, the same Content can be found here:

/wp-content/uploads/2013/03/5_194856.jpg

Double-click on the marked point.

/wp-content/uploads/2013/03/6_194857.jpg

Click on the button “Delete RELID” and type “OS”

/wp-content/uploads/2013/03/7_194859.jpg

/wp-content/uploads/2013/03/8_194860.jpg

/wp-content/uploads/2013/03/9_194861.jpg

Confirm deletion

/wp-content/uploads/2013/03/11_194862.jpg

Refresh the list

/wp-content/uploads/2013/03/10_194863.jpg

Set a filter on ID field
/wp-content/uploads/2013/03/12_194864.jpg
The list with the filter must is empty.

Restart SAP_COLLECTOR_FOR_PERFMONITOR job or wait until the scheduled time./wp-content/uploads/2013/03/13_194865.jpg

Summary

This post described main procedure based on Note 903220 and many obvious for basis consultant things were ommited (such as “making a backup”, “granding permissions” and so on). If you are not sure about eliminating the dump in your system, post a question on the forum or create an OSS-message.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply