11-30-2010 04:33 PM
01-15-2015 06:09 PM
SAS/Access to Teradata does not support BIGINT data, and it is usually the offending data type. However, other data types are supported but still may cause data truncation and errors. For example, DECIMAL(38,15) is supported by SAS/Access, but it has an invalid SAS format, so it creates a runtime format error in SAS.
An easy way to find BIGINT or other unsupported data is to do a Proc Contents on the table using the libname access method. The erroneous columns will be in the SAS log. You can also look in the listing for DECIMAL values where they are longer than 15 digits -- you may want to query the max and min for those columns before you cast them to something that SAS can read.
SAS only represent 15 digits with exact precision in 64-bit operating systems. You need to cast those bigger decimal types as DECIMAL(15) if they are in bounds, or CHARACTER(20) (or larger) if they are not. Note that character keys are discouraged because they are slow to access in joins and they take up more space.
06-12-2017 11:53 AM
I'm facing the same issue and i wanted to ask you how did you solve it? I'm doing a query over a table that has one column not supported and even if i'm not selecting it, it's giving me this error.
Thanks in advance!
06-13-2017 10:54 AM