SQL 8115 : Arithmetic overflow error when running index analysis

[former_member211576]

Hi experts,

  I got an error: "SQL 8115 : Arithmetic overflow error converting float to data type numeric

row 1, col -1 [WP3 ] [sap_index_recommend:BUILD_N_E", please help.

[Former Member]

Hi Dennis,

do you have an S-User and the possibility to open an R/3 or WTS service connection for SAP? If so, it makes sense to open an incident for it with SAP.

Usually this error comes up when the underlying monitoring procedure has to handle higher numbers than expected and then the datatype in use is overflowing - I consider such an error a bug if the stored procedure which causes this is an SAP stored procedure. In your case it is.

Of course, with access to the system, one can trace back the problem to its root and _could_ adjust the stored procedure - but as it's delivered by SAP you shouldn't do so yourself even if you're able to identify the root cause.

Regards,

Beate

[Former Member]

Hello,

It is better you open a OSS message in marketplace.

Best regards

Joao Vagarinho

[former_member211576]

Hi João,

  It has been done.

[former_member195792]

Hi,

Did you ever got a response from SAP with the answer to this issue?

Best regards,

Menno

[former_member211576]

Hi Monno,

The problem occurred long time ago and I did not remember. I think I open service connection and SAP modify T-SQL script and fix it, FYI.

---

2014/03/13 - 16:47:11 UTC+8 - Reply by SAP
Dear Customer, Our developer took a look at this problem. He says the problem is in the following place decimal(nn,yy) He have attached a script where the decimal(nn,yy) was replaced by decimal(15,yy) in sap_index_recommend storage procedure. Can you please apply the script change *after* the error occurs(if the error occurs next time), and see if it fixes the problem? Run MSSPROCS, find the script, edit and replace the contents with the text I attached.  As soon as it is saved, the change takes effect, there is no need to execute mssprocs. Afterwards the problem should be solved.

[former_member195792]

Thanks Dennis !

If it's a bug in the stored procedure then I can copy it from another system where it is running fine.

Thanks for your help !

[luisdarui]

Hi Menno,

There was an error in the stored procedure that was fixed back in march of 2014.

I created an article with the solution and a fixed script is attached that you can replace:

2269960 - SQL 8115: Arithmetic overflow error when running index analysis in DBACockpit

To access the KBA it is required a S-user and you must be logged in SMP.

Best Regards,

Luis Darui

[former_member195792]

Hi Luis,

Thats even better!

Thank you very much!

For some reason I did not find this note when I searched for the SQL 8115 error.

Best regards,

Menno

[former_member195792]

Hi Luis,

I just downloaded and replaced the script.
But When I execute in SA38 MSPROCS , I get an error in the new script:

SQL error                                                   1-: COUNT field incorrect or syntax error

Message no. SMMSS_ANALYZE000

The database is SQLserver 2005.

Any ideas?

Best regards,

Menno

[luisdarui]

Hi Menno,

I tested replacing this script in SAP_BASIS 702, 730, 731 and 740. This is the same script for all databases as of march of 2014 for the above releases, even SAP_BASIS 750 has the same script.

Are you running one of the above SAP_BASIS releases?

In case yes, I would ask you to open a SAP incident and ask to assign to Luis Darui (you can even link this thread and the KBA 2269960 in the incident. I'll gladly take over this.

Best Regards,

Luis Darui

[former_member195792]

we are on 700, think thats why it might not be working.

[luisdarui]

Hi Menno,

Please open the support incident with SAP with the R/3 connection already opened (to a QA system where we can reproduce it) and the credentials necessary. Check SAP Note #1027512 for the authorizations to DBACockpit that we'll need.

It might require a different fix to SAP_BASIS 700, I'll check it myself. Do me a favor, ask in the incident to be assigned to me (Luis Darui), my colleagues will do it.

Best Regards,

Luis Darui

[former_member188883]

Hi Dennis,

Could you check SAP note #429805

Hope this helps.

Regards,

Deepak Kori

[Sriram2009]

Hi Lee

Just restart the full system and then check the same

and what is your DB size?

Regards

Sriram