ERROR: At least one of the columns in this DBMS table has a datatype that is not supported by this engine.

Reply
Contributor
Posts: 44

ERROR: At least one of the columns in this DBMS table has a datatype that is not supported by this engine.

%Let DateToGet = %sysfunc(intnx(day,%sysfunc(today()),-45),yymmdd10.);
%let DateToGet1 =  %str(%'&DateToGet%');
%put &DateToGet1;

%Let DateToGet2 = %sysfunc(today(),yymmdd10.);
%let DateToGet3 =  %str(%'&DateToGet2%');
%put &DateToGet3;

proc sql;
connect to teradata as myconn (
   user="XXXXX@LDAP"
   password=XXXXXXXX 
    SERVER=XXXXX.XXX.com.
    DATABASE=DATA_PRESS_40);
create table  proff_2 as 
SELECT *
FROM connection to myconn (
SELECT Bil_cnt_
FROM DATA_PRESS_40.Pa_til_DY
WHERE ing_tem_Ne in ('FLB'  'MA') and
Pro_esc in ( 'ls' 'Naing'  'ion'  'ion 0-29') and
Bill_Date >  &DateToGet1 and Bill_Date < &DateToGet3;
ORDER BY Bil_cnt_);
quit;

I am trying the above code , and I keep getting an error message:

ERROR: At least one of the columns in this DBMS table has a datatype that is not supported by this engine.

Please assist..

Super User
Posts: 5,388

Re: ERROR: At least one of the columns in this DBMS table has a datatype that is not supported by this engine.

The obvious counter question is what are the data types/lengths in your query?

SAS/ACCESS(R) 9.4 for Relational Databases: Reference, Fifth Edition

"SAS/ACCESS 9 does not support these Teradata data types: GRAPHIC, VARGRAPHIC, and LONG VARGRAPHIC"1

Data never sleeps
Super User
Super User
Posts: 6,849

Re: ERROR: At least one of the columns in this DBMS table has a datatype that is not supported by this engine.

Since you are only selecting one column you know which one has an invalid type.

Try telling Teradata to cast it into a float for SAS.


SELECT cast(Bil_cnt_ as float) as Bil_cnt_


Valued Guide
Posts: 3,208

Re: ERROR: At least one of the columns in this DBMS table has a datatype that is not supported by this engine.

review the sql paas through specifics of TD. SAS/ACCESS(R) 9.4 for Relational Databases: Reference, Fifth Edition is using the execute approach.  This will cause a full isolation of SAS and TD.

Your TD DBA is probably having defined a non supported one  SAS/ACCESS(R) 9.4 for Relational Databases: Reference, Fifth Edition

What you are doing is running the Query in TD and getting those results back to SAS.
If that is intended (network load) that is as it is.  You could have support with in-database procedures and own working storage at the TD site. 

---->-- ja karman --<-----
Ask a Question
Discussion stats
  • 3 replies
  • 2619 views
  • 6 likes
  • 4 in conversation