Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Querying iSeries DB2 internal error number too big

mhutcheson
6 - Meteoroid

Hi all,

 

I'm using Alteryx version 2018.1.4.44311 (64bit)

 

I'm querying a table held in an iSeries DB2 DB but keep receiving the error:

 

'Internal Error in_getNumericAttribute:number too big'

 

I've tried using a WHERE clause to limit records but still no avail.

 

Any ideas?

 

Thanks,

 

Michael

 

 

5 REPLIES 5
mhutcheson
6 - Meteoroid

Looks like a memory issue - doesn't work on my client (8GB RAM), but does work on server (32 GB)

jorlicz
5 - Atom

How can I fix this?

 

Error.PNG

mhutcheson
6 - Meteoroid

If you are running DB2, execute a SQL statement against the table - what result do you get?

kelvin_law1
9 - Comet

Hi jorlicz, I am having the same issue now, getting "Internal Error in _getNumericAttribute: number too big" error.

We found that this only happen when getting nchar type variables, but decimal type variables work fine.

We are using the "iSeries Access ODBC Driver" version 11.64.

Do you know how to fix it now?

sbutoliy
5 - Atom

I am getting the same error when I run the InDatabase Alteryx workflows. The data is sourced in Redhshift. The workflows usually throws error in the FOrmula tool or the Union tool. Any ideas why would that happen?

 

Error2.jpgError.jpg

Labels