Problem Note 14502: Having maxdecimals set to 18 in Teradata can result in incorrect results
The MaxDecimal flag determines whether the maximum decimal default for
an expression evaluates to 15 or to 18. Selecting a column that has
been defined as a DECIMAL(18) or performing some functions such as
SUM() can result in the wrong value being read from Teradata. The
issue occurs when the variable/function is not the last thing on the
SELECT clause.
The following would result in a problem:
select sum(salary), dept
select dept, sum(salary), avg(salary) - sum would be incorrect but
average would be correct
The following would not assuming that none of the variables are defined
as decimal(18):
select dept,sum(salary)
select sum(salary)
select avg(salary)
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:
http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#014502
For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#014502
A Technical Support hot fix for SAS 9.1.2 (9.1 TS1M2) for this
issue is available at:
http://www.sas.com/techsup/download/hotfix/c9_sbcs_prod_list.html#014502
For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/c9_dbcs_prod_list.html#014502
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Teradata | z/OS | 9.1 TS1M2 | 9.1 TS1M3 SP2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Topic: | Data Management ==> Data Sources ==> External Databases ==> Teradata SAS Reference ==> LIBNAME Engines
|
Date Modified: | 2005-03-16 14:58:59 |
Date Created: | 2005-02-04 13:02:06 |