[NCR][ODBC Teradata Driver][Teradata RDBMS] Numeric overflow

kool · Principal Member Joined: 15 Apr 2005 Posts: 340

[NCR][ODBC Teradata Driver][Teradata RDBMS] Numeric overflow occurred during computation. -2616 ??

bdouglas

That's pretty straightforward - the result of the query is too big for a numeric field... We usually only see that if an application has entered a value in error, usually via money conversion.

If you take that same SQL (from your report View SQL), it should give the same error in Queryman, whatever SQL Tool you have - look for any numbers that are cast to a length (float 10,2) and check the underlying data.

Good luck,
B

kool · Principal Member Joined: 15 Apr 2005 Posts: 340

What is the Solution ??? Wht should i do ?

bdouglas

There are really only 2 options - if the data is incorrect, it must be corrected in the database; if it is correct, the displayed field has to be adjusted to display this value. That means a universe change.

I'd check the object that isn't displaying - if it's set to be 10 digits wide, try 15 and see if you get data.

This may take some SQL outside of BO to resolve, good luck.

B

kool · Principal Member Joined: 15 Apr 2005 Posts: 340

Why universe Change? it was running fine Until friday.
when i used Queryman to run the SQL it is saying no more spool space for my userid.

and "I'd check the object that isn't displaying - if it's set to be 10 digits wide, try 15 and see if you get data." what is this mean? and where can i find this.

kool · Principal Member Joined: 15 Apr 2005 Posts: 340

Thanks bdouglas.
Problem solved and thanks for your prompt Reply. but i am still confused what that object format mean. is that mean going to object format and formating the numeric value. like #,###0.00
i removed SUM from the SQL and rerun the report.

bdouglas

Can you post the SQL - with our without the SUM()?

I might be able to point out what was causing this problem better that way.....

Thanks,
B

kool · Principal Member Joined: 15 Apr 2005 Posts: 340

Actually the data should be in the thousands but it was in millions. thats why it was throwing that error. i have sent email to the DBA and he will work on that.

bdouglas

That's exactly the kind of thing that will throw this error - just not enough digits to hold the answers....

Good luck,
Brent