Full Optimize Problem

[#1]

Hi Guys,

I am getting the following error when doing a full optimize with database compression:"Error message:Arithmetic overflow error converting numeric to data type numeric.

The statement has been terminated."

I am guessing this has a lot to do with the performance issues i am having with system at the moment. Everything is slow at the moment and I am getting SendGovener issues as well.

Any help will be appreciated.

Regards,

AvdB

[sorin_radulescu]

Hi,

It seems you are goindg over of max number into default format.

Sam provide you a right thread.

Actually the sum of your numbers are going over 15 digits which is the maximum into default format and that's the problem.

the format is 25,10 but you can changed into 25, 4 which means will allow you to use max 4 decimals but you will be able to use 21 digits numbers.

Regards

Sorin Radulescu

[Former Member]

Hello,

Please read note 1369160 - Arithmetic overflow error converting nvarchar to data type numeric.

Maybe it could hepls.

We had the same problem here and now it's solved.

Regards

[Former Member]

Hi all,

We are having that same problem and really need to solve it.

So, reading the thread and the note, it seems that we can have that error due to 2 different problems:

1) numbers too big in the fact tables.

2) a wrong entry in the tbl.Defaults table (using a comma notation in a "version" entry instead of a dot notation).

So, we would need help with the following:

1) about tbl.Defaults, in our case we only have values with commas in an entry like this:

UserId        Type        App         KeyID                Value
_GLOBAL     SYSTEM      PARAMETROS    SIGNED_DATA_FORMAT      20,15

All the ones about version look like this:

UserId        Type        App         KeyID          Value
_GLOBAL    VERSION      PARAMETROS                    1.022

So, is the entry about the Key "Signed_Data_Format" supposed to be causing the problem? Should we either change it or erase that entry?

2) we don't have numbers too big in the database (in this case), but how are we suppose to prevent that from happening?

Thank you,

Rafael

[Former Member]

Hi all,

as an update, we solved the problem. It was indeed caused by the SIGNED_DATA entry in the tbl.Defaults table. It was there because we have a parameter created in the "Application Set Parameters" of BPC Administration as SIGNED_DATA_FORMAT (25,10). This caused the error when executing "Modify" over the application. By simply deleting it, everything works fine now.

Still, for the sake of future references, how are we suppose to prevent too big numbers from being inserted in the fact table?

Regards,

Rafael