cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
karthic2612
‎04-17-2020
  • 27 Posts
  • 0 Likes Given
  • 0 Solutions
  • 3 Likes Received

How to use bulkload option for SAS/Interface to Snowflake

by Obsidian | Level 7 in SAS Data Management
‎01-16-2020 08:32 AM
2 Likes
‎01-16-2020 08:32 AM
2 Likes
Hi All,   Could someone give sample code snippet to use bulkload option for SAS/Access interface to Snowflake.   I am able to connect to Snow flake successfully using libname statement.   libname bulk sasiosnf dsn='snowflake_dev' user=xxxxxx 74 pwd=XXXXXXXXXXXX schema=xxxxx' role=xxxxx warehouse=xxxxx bulkload=yes 74 ! bulkunload=yes bl_internal_stage="user/test1"; NOTE: Libref BULK was successfully assigned as follows: Engine: SASIOSNF Physical Name: snowflake_dev   proc sql; 74 connect using bulk; 75 PUT file:///data/user_data/hari_thatavarthy/SASTABLE2.csv @~/staged; ___ 180 ERROR 180-322: Statement is not valid or it is used out of proper order.   NOTE: PROC SQL set option NOEXEC and will continue to check the syntax of statements. 76 COPY INTO mytable from @~/staged FILE_FORMAT = (FORMAT_NAME = 'my_csv_format'); ____ 180 ERROR 180-322: Statement is not valid or it is used out of proper order.     Getting above error.   I am not sure , how to use PUT and COpy command. Could someone help me on this for Bulkload. ... View more

Will promotion tool migrate SAS Configuration file from SAS 9.3 to 9.4

by Obsidian | Level 7 in Administration and Deployment
‎11-21-2019 08:47 AM
‎11-21-2019 08:47 AM
Hi All,   We are planning to do migration from SAS 9.3 to SAS 9.4. I could see from the documentation that, if we are using SAS migartion utility, the operating system and SAS architecture should be similar. Still we havent decided with the way to do migration from 9.3 to 9.4. Before that i have a quick question to all.   Will i go by promotion tool, is it possible to migrate all SAS configuration files/contents from SAS 9.3 to 9.4 ?  Could someone give some detailing about the migration that can done using promotion tool with more specific.   Thanks, Vishal ... View more

Re: How to use Filename indata pipe to get the file names in a directo...

by Obsidian | Level 7 in New SAS User
‎07-16-2019 05:13 AM
‎07-16-2019 05:13 AM
Thanks...   It worked for me. By replacing ls with dir and /b option. ... View more

Re: How to use Filename indata pipe to get the file names in a directo...

by Obsidian | Level 7 in New SAS User
‎07-16-2019 03:14 AM
‎07-16-2019 03:14 AM
we can use the DOS command "dir" with the /B option to list only the file names.   Thanks, Vishal ... View more

How to use Filename indata pipe to get the file names in a directory f...

by Obsidian | Level 7 in New SAS User
‎07-16-2019 02:52 AM
‎07-16-2019 02:52 AM
Hi,   Could someone help me to get the file names in a directory from Unix environment   Below code is for Windows,  filename indata pipe 'dir "/home/euqyi/shared_folder/user_data/Vishal/pah/Inflated/Data Month March 2019/pah_dx_??????.txt" /b';   Will it work for Unix environment ?    I am using the below piece of code    filename indata pipe 'dir "/home/eupoq/shared_folder/user_data/Richard/pah/Inflated/Data Month March 2019/pah_dx_??????.txt" /b'; data file_list; length fname $50; infile indata truncover; /* infile statement for file names */ input fname $50.; /* read the file names from the directory */ call symput ('num_files',_n_); /* store the record number in a macro variable */ run;   And getting below error in Output data       fname     1 dir: cannot access /home/euqyi/shared_folder/user_ 2 dir: cannot access /b: No such file or directory   Please help me on this.   Thanks, Vishal ... View more

Re: Not able to login to SAS studio

by Obsidian | Level 7 in Administration and Deployment
‎06-24-2019 06:19 AM
‎06-24-2019 06:19 AM
Yes, we have checked with Quest administartor and resolved the issue.   Quest was in disconnected state for a while. Due to that new passwords are not sync and  was not able to validate the new changed password for users.   Thanks for your help. ... View more

Re: Not able to login to SAS studio

by Obsidian | Level 7 in Administration and Deployment
‎06-21-2019 07:25 AM
‎06-21-2019 07:25 AM
Please see below for your ask.   Please see below for your ask. [mzvjl@ip-10-61-xxx-xx euqyi]$ sudo grep -i epcnh /var/log/secure Jun 20 20:21:45 ip-10-61-xxx-xx sshd[29146]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sshd> reason: <> Jun 20 20:21:45 ip-10-61-xxx-xx sshd[29146]: Accepted password for EPCNH from 10.74.xxx.xxx port 49898 ssh2 Jun 20 20:21:45 ip-10-61-xxx-xx sshd[29146]: pam_unix(sshd:session): session opened for user epcnh by (uid=0) Jun 20 20:21:52 ip-10-61-xxx-xx sudo:   epcnh : TTY=pts/0 ; PWD=/home/epcnh ; USER=root ; COMMAND=/bin/su - Jun 20 20:21:52 ip-10-61-xxx-xx su[29211]: pam_unix(su-l:session): session opened for user root by epcnh(uid=0) Jun 20 20:24:07 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:08 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:08 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:16 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:16 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:16 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:16 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:16 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:24:16 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:41:33 ip-10-61-xxx-xx su[33447]: pam_unix(su:session): session opened for user mzvjl by epcnh(uid=0) Jun 20 20:42:12 ip-10-61-xxx-xx sshd[33568]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sshd> reason: <> Jun 20 20:42:12 ip-10-61-xxx-xx sshd[33568]: Accepted password for EPCNH from 10.74.xxx.xxx port 51120 ssh2 Jun 20 20:42:12 ip-10-61-xxx-xx sshd[33568]: pam_unix(sshd:session): session opened for user epcnh by (uid=0) Jun 20 20:42:17 ip-10-61-xxx-xx sudo:   epcnh : TTY=pts/2 ; PWD=/home/epcnh ; USER=root ; COMMAND=/bin/su - Jun 20 20:42:17 ip-10-61-xxx-xx su[33640]: pam_unix(su-l:session): session opened for user root by epcnh(uid=0) Jun 20 20:55:59 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:55:59 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:55:59 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:55:59 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:55:59 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:55:59 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:56:00 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:56:00 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 20:56:23 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <Incorrect Password> Jun 20 21:03:57 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:57 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:58 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:58 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:58 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:59 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:59 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:59 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:03:59 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:12:10 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <Incorrect Password> Jun 20 21:13:31 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:31 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:31 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:32 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:32 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:33 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:33 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:33 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:13:33 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:23:31 ip-10-61-xxx-xx sshd[41882]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sshd> reason: <Incorrect Password> Jun 20 21:23:33 ip-10-61-xxx-xx sshd[41882]: Failed password for epcnh from 10.74.xxx.xxx port 53761 ssh2 Jun 20 21:23:46 ip-10-61-xxx-xx sshd[41882]: Accepted password for epcnh from 10.74.xxx.xxx port 53761 ssh2 Jun 20 21:23:46 ip-10-61-xxx-xx sshd[41882]: pam_unix(sshd:session): session opened for user epcnh by (uid=0) Jun 20 21:36:29 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <Incorrect Password> Jun 20 21:36:39 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <Incorrect Password> Jun 20 21:44:06 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:07 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:07 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:07 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:07 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:08 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:08 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:08 ip-10-61-xxx-xx sasauth[25271]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:44:08 ip-10-61-xxx-xx sasauth[32387]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:45:11 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <Incorrect Password> Jun 20 21:45:39 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <succeeded disconnected> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <> Jun 20 21:47:37 ip-10-61-xxx-xx sasauth[31986]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sasauth> reason: <Incorrect Password> Jun 20 23:05:23 ip-10-61-xxx-xx sshd[41882]: pam_unix(sshd:session): session closed for user epcnh Jun 20 23:08:38 ip-10-61-xxx-xx sshd[29146]: pam_unix(sshd:session): session closed for user epcnh Jun 20 23:09:04 ip-10-61-xxx-xx sshd[33568]: pam_unix(sshd:session): session closed for user epcnh Jun 21 04:34:48 ip-10-61-xxx-xx sshd[3485]: pam_vas: Authentication <failed> for <Active Directory> user: <epcnh> account: <AWS\EPCNH> service: <sshd> reason: <Incorrect Password> Jun 21 04:34:50 ip-10-61-xxx-xx sshd[3485]: Failed password for epcnh from 10.85.xx.xxport 52768 ssh2 Jun 21 04:34:59 ip-10-61-xxx-xx sshd[3485]: Accepted password for epcnh from 10.85.xx.xxport 52768 ssh2 Jun 21 04:34:59 ip-10-61-xxx-xx sshd[3485]: pam_unix(sshd:session): session opened for user epcnh by (uid=0) Jun 21 04:45:01 ip-10-61-xxx-xx sshd[3485]: pam_unix(sshd:session): session closed for user epcnh Jun 21 11:03:07 ip-10-61-xxx-xx sudo:   mzvjl : TTY=pts/2 ; PWD=/home/euqyi ; USER=root ; COMMAND=/bin/grep -i epcnh /var/log/secure ... View more

Not able to login to SAS studio

by Obsidian | Level 7 in Administration and Deployment
‎06-21-2019 02:09 AM
‎06-21-2019 02:09 AM
Hi Team,   Unfortunately, we are not able to login to SAS studio with new password created for the user. But, user is able to login with their old password. I am not sure what's happening here.   Our environment is SAS 9.4 M5 release and we have configured PAM authentication against LDAP. For 60 days password will expire and users will reset the password from LDAP domain.   NOw, after reset the password, users are not able to logon using their new password. But they are able to login successfully using thier old password.   I have checked the SAS metadata server logs. Please see below for sample error we got. Could someone help on this issue.   2019-06-20T21:47:37,260 TRACE [09362829] :mzvjl - Create Authenticated Token 2019-06-20T21:47:37,260 TRACE [09362829] :mzvjl - Client connection id: 1531489 2019-06-20T21:47:37,260 DEBUG [09362829] :mzvjl - User/Pass authentication for user epcnh 2019-06-20T21:47:37,260 TRACE [09362829] :mzvjl - Calling auth provider... 2019-06-20T21:47:37,260 TRACE [09362829] :mzvjl - Unix OS auth provider called for user epcnh 2019-06-20T21:47:38,732 INFO [09362829] :mzvjl - Access denied. 2019-06-20T21:47:38,732 TRACE [09362829] :mzvjl - bkAuthenticate failed 80BFD100 2019-06-20T21:47:38,732 DEBUG [09362829] :mzvjl - Provider failed: 80bfd100 2019-06-20T21:47:38,732 WARN [09362829] :mzvjl - New client connection (1531489) rejected from server port 8561 for user epcnh. Peer IP address and port are [10.61.xxx.xx]:49326 for APPNAME=Logon Manager 9.4. 2019-06-20T21:47:38,732 INFO [09362829] :mzvjl - Client connection 1531489 closed.   Thanks, Vishal   ... View more

Advantages in upgrading SAS 9.4 m6 from m5 release

by Obsidian | Level 7 in Administration and Deployment
‎03-04-2019 06:30 AM
‎03-04-2019 06:30 AM
Hi All,   We would like to upgrade to the new SAS version to sas 9.4 M6 from SAS 9.4 M5 in our Linux environment. Before proceeding with SAS, we need to know some basic information about the latest release and advantages and disadvantages in it.   Could someone summarize the advantages and disadvantages in upgrading to SAS 9.4 M6 release from m5 release   Have anybody installed and faced any issues with the new version ? .   We have below products installed in our environment (Redhat Linux).    ---Base SAS Software   ---SAS/STAT  ---SAS/GRAPH   ---SAS Integration Technologies  ---SAS/Secure 168-bit   ---SAS Enterprise Guide   ---SAS/ACCESS Interface to PC Files   ---SAS/ACCESS Interface to ODBC   ---SAS Workspace Server for Local Access  ---SAS/ACCESS to Amazon Redshift   ---High Performance Suite ---SAS Search and Indexing Server  ---SAS Web Crawler Server  ---SAS LASR Analytic Server  ---SAS Visual Analytics Hub  ---SAS Visual Analytics Services  ---Advanced Programming for LASR Analytic Server  ---SAS Visual Analytics Server Components  ---SAS Visual Statistics Mid-tier  ---Visual Analytics Explorer    Thanks, Vishal ... View more

How to connect S3 from SAS

by Obsidian | Level 7 in Administration and Deployment
‎09-10-2018 07:10 AM
‎09-10-2018 07:10 AM
Hi All,   Please let me know the procedure to connect S3 bucket from SAS.   We don't create secret key or Access key for id's. In this case, how we can connect S3 bucket from SAS without secret key/Access key for id.   Thanks, Vishal ... View more

Re: Is it possible to connect from sas 9.2 windows client to SAS cloud...

by Obsidian | Level 7 in Administration and Deployment
‎09-04-2018 09:31 AM
‎09-04-2018 09:31 AM
Thanks for the information provided.   Could you please let me know how to connect from SAS 9.2 using SAS/Connect to SAS 9.4 server. Please give me a link or supporting document to use SAS/Connect. I dont have any idea about SAS/Connect.    Thanks, Vishal ... View more

Is it possible to connect from sas 9.2 windows client to SAS cloud ser...

by Obsidian | Level 7 in Administration and Deployment
‎09-04-2018 08:01 AM
‎09-04-2018 08:01 AM
Hi All,   I have installed SAS 9.4 cloud server in our environment.   My ask is   Some of the users in our business have installed SAS 9.2 for windows client. So, they don't want to install SAS enterprise guide to connect with SAS 9.4 cloud server. They need to use SAS 9.2 for windows client to connect with SAS 9.4 server.   Is it possible to connect from SAS 9.2 windows client to SAS 9.4 server. If it is possible, could you please provide the steps to connect from SAS 9.2 windows client to SAS 9.4 cloud server   Thanks, Vishal ... View more

Re: Facing issue while Configuring SAS/Access interface to Redshift

by Obsidian | Level 7 in Administration and Deployment
‎08-21-2018 05:09 AM
‎08-21-2018 05:09 AM
Hi Simon, As per your advice, I have setup the LD_LIBRARY_PATH to load libodbc.so from inside the Redshift installation directory. :/usr/lib64/libodbcinst.so:/app/sashome/AccessClients/9.4/Redshift/lib/:/app/sashome/AccessClients/9.4/Redshift/lib/S0rsft27.so:/app/sashome/AccessClients/9.4/Redshift/:/app/sashome/AccessClients/9.4/Redshift/lib:/usr/lib64:/app/sashome/AccessClients/9.4/Redshift/lib/libodbc.so   Default path for the drivers (odbcinst and odbc.ini) [sas@ip-xx-xx-xx-xx odbc_shared]$ odbcinst -j unixODBC 2.3.1 DRIVERS............: /app/SAS_Software_Depot/odbc_shared/odbcinst.ini SYSTEM DATA SOURCES: /app/SAS_Software_Depot/odbc_shared/odbc.ini FILE DATA SOURCES..: /app/SAS_Software_Depot/odbc_shared/ODBCDataSources USER DATA SOURCES..: /app/SAS_Software_Depot/odbc_shared/odbc.ini SQLULEN Size.......: 8 SQLLEN Size........: 8 SQLSETPOSIROW Size.: 8   I am confused by using both SAS Access interface to Amazon redshift and ODBC engine. Could you please give me a clarity to use SAS/Access interface to Amazon redshift for Redshift data source connections. Do i need to use 2 separate odbc.ini file for ODBC engine and Redshift interface. Or we can use it as single odbc.ini and feed all the connection details in single odbc.ini for both odbc and Redshift native interface.   Thanks, Vishal ... View more

Facing issue while Configuring SAS/Access interface to Redshift

by Obsidian | Level 7 in Administration and Deployment
‎08-20-2018 03:17 AM
‎08-20-2018 03:17 AM
Hi All,   I have licensed SAS/Access interface to Amazon redshift. I have installed in our environment.   Allso I have configured Teradata using odbc drivers. and for that I have installed unixODBC driver manager. I am able to connect Successfully   My doubt is, where i need to update the Data source name and connection details for Redshift. Is it in common odbc.ini file where I used for Teradata connection details or do i need to update in SAS Access Redshift driver install path. for ex /sas/sashome/Accessclients/9.4/Redshift under that I have odbc.ini.   I have updated all the connection details of Teradata and Redshift in single odbc.ini file and configured.   Tried to execute Libname statement for those connection entries. For teradata it is successfull. but for Redshift I am receiving Libname statement error. Please see the libname statement error below   libname redshift sasiorst server="redshiftserver.us-east-1.redshift.aws.com" DB=database name user=username password=pass;   ERROR: CLI error trying to establish connection: 523 630 ERROR: Error in the LIBNAME statement.   I think above error indicates that I am missing to set environment variable. I couldnt figure out the root cause of the issue.   [sas@ip-10-61-100-9 Redshift]$ echo $LD_LIBRARY_PATH :/usr/lib64/libodbcinst.so:/app/sashome/AccessClients/9.4/Redshift/lib/:/app/sashome/AccessClients/9.4/Redshift/lib/S0rsft27.so:/app/sashome/AccessClients/9.4/Redshift/:/app/sashome/AccessClients/9.4/Redshift/lib:/usr/lib64 [sas@ip-10-61-100-9 Redshift]$   Someone please help me to figure out the issue.    ... View more

Re: Issue while updating existing configuration using SAS Deployment m...

by Obsidian | Level 7 in Administration and Deployment
‎08-17-2018 03:00 AM
‎08-17-2018 03:00 AM
Hi, To answer for your this   Create a separate software depot for every software order (site number), and run the SDW from that depot; don't mix things up. --->Yes I have used a separate Software depot for installing a new product. And I have ran SDW from that depot.   Thanks ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎04-17-2020 03:02 AM
Likes from
View All
Quick links