Cognos Data Size vs. Vertica Table Column Data Type Size
Posted: Fri Jan 27, 2012 9:45 pm
Hi,
We have a column defined in a Vertica table as numeric(12, 5). In this column we can store numbers as large as 9999999.99999. When we query the column in Cognos using the "auto sum" feature we get an error (see attachment). Cognos is apparently sizing the field to display the sum based the table's data type's precision and scale which is too small to hold the sum's larger size. Our solution was to re-size the column making it bigger (i.e. numeric(25, 5)). It worked, but oddly, we do not have the same issue when querying a MySQL database column defined as decimal(12, 5). Is MySQL better? Ha hah, just kidding.
Does any one know of a better solution? Perhaps a Cognos setting? Otherwise, I have to re-size a lot of numeric columns in our Vertica database!
Thanks
We have a column defined in a Vertica table as numeric(12, 5). In this column we can store numbers as large as 9999999.99999. When we query the column in Cognos using the "auto sum" feature we get an error (see attachment). Cognos is apparently sizing the field to display the sum based the table's data type's precision and scale which is too small to hold the sum's larger size. Our solution was to re-size the column making it bigger (i.e. numeric(25, 5)). It worked, but oddly, we do not have the same issue when querying a MySQL database column defined as decimal(12, 5). Is MySQL better? Ha hah, just kidding.
Does any one know of a better solution? Perhaps a Cognos setting? Otherwise, I have to re-size a lot of numeric columns in our Vertica database!
Thanks