I had tried this also. I got same error. ... View more

Yes. I tried with different variable name. But no luck. Please see below error.   1 ODBC: AUTOCOMMIT is NO for connection 0 0 1877360424 tkvercn1 0 Submit 2 options sastrace=',,,d' sastraceloc=saslog; 3 libname dlib odbc user="milind" password=XXXXXXXXXXXXXXXXXXXXXX datasrc="RWE_pharmetrics_DSN" 3 ! schema="public"; NOTE: Libref DLIB was successfully assigned as follows: Engine: ODBC Physical Name: RWE_pharmetrics_DSN 4 5 data mtest2(drop=i); 6 length no1 8 no2 8 var1 $8; 7 do i=1 to 10; 8 no1=i; 9 no2=i*i; 10 var1="abc"; 11 output; 12 end; 13 run; NOTE: The data set WORK.MTEST2 has 10 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 0.03 seconds cpu time 0.03 seconds 14 15 16 data dlib.mtest3; 17 set mtest2; 18 run; ODBC: AUTOCOMMIT is NO for connection 1 1 1877360424 tkvercn1 0 DATASTEP ODBC: AUTOCOMMIT turned ON for connection id 1 2 1877360424 tkvercn1 0 DATASTEP 3 1877360424 tkvercn1 0 DATASTEP ODBC_1: Prepared: on connection 1 4 1877360424 tkvercn1 0 DATASTEP SELECT * FROM public.MTEST3 WHERE 0=1 5 1877360424 tkvercn1 0 DATASTEP 6 1877360424 tkvercn1 0 DATASTEP ODBC: AUTOCOMMIT is NO for connection 2 7 1877360424 tkvercn1 0 DATASTEP ERROR: The character variable var1 has too long a value for the DLIB library. NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set DLIB.MTEST3 was only partially opened and will not be saved. ODBC: ROLLBACK performed on connection 2. 8 1877360424 tkvercn1 0 DATASTEP ODBC: COMMIT performed on connection 2. 9 1877360424 tkvercn1 0 DATASTEP WARNING: File deletion failed for DLIB.MTEST3.DATA. NOTE: DATA statement used (Total process time): real time 0.15 seconds cpu time 0.12 seconds ... View more

Please see below log with sastrace option.   171 172  options sastrace=',,,' sastraceloc=saslog; 173  libname dlib odbc user="milind" password=XXXXXXXXXXXXXXXXXXXXXX  datasrc="RWE_pharmetrics_DSN" 173! schema="public"  dbmax_text=32767 ; NOTE: Libref DLIB was successfully assigned as follows:       Engine:        ODBC       Physical Name: RWE_pharmetrics_DSN 174 175  data mtest2(drop=i); 176  length no1 8 no2 8 char $8; 177  do i=1 to 10; 178  no1=i; 179  no2=i*i; 180  char="abc"; 181  output; 182  end; 183  run;   NOTE: The data set WORK.MTEST2 has 10 observations and 3 variables. NOTE: DATA statement used (Total process time):       real time           0.01 seconds       cpu time            0.01 seconds     184 185 186  data dlib.mtest2; 187  set mtest2; 188  run;   ERROR: The character variable char has too long a value for the DLIB library. NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set DLIB.MTEST2 was only partially opened and will not be saved. WARNING: File deletion failed for DLIB.MTEST2.DATA. NOTE: DATA statement used (Total process time):       real time           0.14 seconds       cpu time            0.09 seconds ... View more

I tried the same.    Please see below log for Program1:    106 libname dlib odbc user="milind" password=XXXXXXXXXXXXXXXXXXXXXX datasrc="RWE_pharmetrics_DSN" 106! schema="public"; NOTE: Libref DLIB was successfully assigned as follows: Engine: ODBC Physical Name: RWE_pharmetrics_DSN 107 108 proc sql; 109 create table dlib.mtest2 as 110 select * from mtest2; ERROR: The character variable char has too long a value for the DLIB library. WARNING: File deletion failed for DLIB.MTEST2.DATA. 111 quit; NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 0.15 seconds cpu time 0.12 seconds   Please see below log for Program2:   122 libname dlib odbc user="milind" password=XXXXXXXXXXXXXXXXXXXXXX datasrc="RWE_pharmetrics_DSN" 122! schema="public"; NOTE: Libref DLIB was successfully assigned as follows: Engine: ODBC Physical Name: RWE_pharmetrics_DSN 123 /* 124 proc sql; 125 create table dlib.mtest2 as 126 select * from mtest2; 127 quit; 128 */ 129 /**********************************/ 130 131 proc sql; 132 create table dlib.mtest2 like mtest2; ERROR: The character variable char has too long a value for the DLIB library. WARNING: File deletion failed for DLIB.MTEST2.DATA. 133 insert into dlib.mtest2 134 select * from mtest2 ; ERROR: File DLIB.MTEST2.DATA does not exist. 135 quit; NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 0.20 seconds cpu time 0.12 seconds ... View more

I tried this. It did not work. Please see below log.    88 libname dlib odbc user="milind" password=XXXXXXXXXXXXXXXXXXXXXX datasrc="RWE_pharmetrics_DSN" 88 ! schema="public" dbmax_text=32767 ; NOTE: Libref DLIB was successfully assigned as follows: Engine: ODBC Physical Name: RWE_pharmetrics_DSN 89 90 data mtest2(drop=i); 91 length no1 8 no2 8 char $8; 92 do i=1 to 10; 93 no1=i; 94 no2=i*i; 95 char="abc"; 96 output; 97 end; 98 run; NOTE: The data set WORK.MTEST2 has 10 observations and 3 variables. NOTE: DATA statement used (Total process time): real time 0.00 seconds cpu time 0.00 seconds 99 100 101 data dlib.mtest2; 102 set mtest2; 103 run; ERROR: The character variable char has too long a value for the DLIB library. NOTE: The SAS System stopped processing this step because of errors. WARNING: The data set DLIB.MTEST2 was only partially opened and will not be saved. WARNING: File deletion failed for DLIB.MTEST2.DATA. NOTE: DATA statement used (Total process time): real time 0.17 seconds cpu time 0.14 seconds ... View more

I tried with this option. It did not work. ... View more

We dont have difference access engine.  We have SAS/ACCESS Interface to ODBC license. We have use this product only, (We don't have SAS/ACCESS Interface to Redshift). ... View more

Thank you. I am good with this explanation.  ... View more

Why there is extra cost for SAS/ACCESS Interface to Amazon Redshift? What are the extra features which are present in SAS/ACCESS Interface to Amazon Redshift? We have product SAS/ACCESS Interface to ODBC. There is will be one more component to be introduced in out environment "Amazon Redshift". So if we get SAS/ACCESS Interface to Amazon Redshift, what are the extra features which we will get? ... View more

Why there is extra cost for SAS/ACCESS Interface to Amazon Redshift? What are the extra features which are present in SAS/ACCESS Interface to Amazon Redshift?   We have product SAS/ACCESS Interface to ODBC. There is will be one more component to be introduced  in out environment "Amazon Redshift". So if we get SAS/ACCESS Interface to Amazon Redshift, what are the extra features which we will get? ... View more