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: 
Jlochoa
‎03-24-2022
  • 40 Posts
  • 20 Likes Given
  • 2 Solutions
  • 9 Likes Received

Re: PROC S3 Procedure Questions

by Obsidian | Level 7 in Administration and Deployment
‎06-08-2018 11:41 AM
‎06-08-2018 11:41 AM
Hi Tom,   I created the .ssh directory in my /home/username directory and added the tks3.conf file. Unfortunately, the access denied error message in the log file   ERROR: Could not put file. ERROR: Access Denied ... View more

Re: SAS Studio Status check stuck in Initializing after click "Start"

by Obsidian | Level 7 in SAS Studio
‎06-08-2018 09:25 AM
‎06-08-2018 09:25 AM
Just started yesterday with SAS Studio log-in issue using Chrome version 67. SAS 9.4M4 Linux servers environment. Will open track with SAS Tecg Support. ... View more

Re: PROC S3 Procedure Questions

by Obsidian | Level 7 in Administration and Deployment
‎06-01-2018 12:21 PM
‎06-01-2018 12:21 PM
Hi Jeff,   Is there a way to set server side encryption in the Proc S3 config file or some other way. The S3 bucket requires this encryption.   Thanks, jose ... View more

PROC S3 Procedure Questions

by Obsidian | Level 7 in Administration and Deployment
‎05-30-2018 10:30 AM
‎05-30-2018 10:30 AM
SAS Current version: 9.04.01M4P110916   Is the SAS/ACCESS Interface to Amazon Redshift required to use the PROC S3 procedure to connect to a S3 bucket?    There are several SAS programmers that require access to the S3 bucket. Is there one config file for all SAS programmers or need to add the config file in each SAS programmer /home/username Linux directory? ... View more

Re: LogConfigSweeper tool for automated log and configuration data col...

by Obsidian | Level 7 in Administration and Deployment
‎05-14-2018 01:27 PM
‎05-14-2018 01:27 PM
Hello Everyone,   I installed the LogConfigSweeper utility on a Five Linux SAS Server enviornment that is comprised of the following 1-Metadata Server 2-SASEMTM - Compute Server with "ObjectSpawner" directory located in SAS-configuration-directory/Lev1/ 3-SASAPP - Computer Server with "ObjectSpawner2" directory located in SAS-configuration-directory/Lev1/ 4-SASECCSA - Compute Server with "ObjectSpawner3" directory located in SAS-configuration-directory/Lev1/ 5-WebServer   When executing SAS-configuration-directory/Lev1/LogConfigSweeper.sh objectspawner -output /tooloutput on 2-SASEMTM the zipped file is created with all of the logs located in SAS-configuration-directory/Lev1/ObjectSpawner/Logs directory.   However, executing the LogConfigSweeper utility on 3-SASAPP or 4-SASECCSA for ObjectSpawner files the zip file is empty. It appears the LogConfigSweeper utility does not recognize or find the appropriate logs because of the "ObjectSpawner2" or "ObjectSpawner3" directory names. Does the "logconfigsweeper.jar" executable require modification?   Cheers, Jose     ... View more

Re: Configuring Cloudera ODBC Driver for Impala

by Obsidian | Level 7 in Administration and Deployment
‎01-16-2018 02:35 PM
‎01-16-2018 02:35 PM
Thanks Sam, Peter from SAS Tech Support is providing guidance on the driver configurations.  ... View more

Configuring Cloudera ODBC Driver for Impala

by Obsidian | Level 7 in Administration and Deployment
‎01-12-2018 10:46 AM
‎01-12-2018 10:46 AM
Dear SAS Community, My SAS environment is running on Linux servers (9.4M4). I need to configure SAS to connect to a Cloudera Hadoop data source. I have reviewed the SAS documentation "SAS 9.4 Hadoop Configuration Guide for Base SAS and SAS/ACCESS, 4th Edition". I understand from the documentation that I can use the SAS Deployment Manager to pull the necessary set of Hadoop JAR and configuration files. I plan to follow the instructions to allow the full functionality of the SAS/ACCESS drivers that I have.    However, Is it possible to just download and configure the Cloudera ODBC Driver for Impala without running the SAS Deployment Manager? Will SAS Foundation/BASE interpret the Cloudera ODBC Driver for Impala as a typical ODBC driver connection to Oracle for example? Thanks, Jose ... View more

Re: Script Server Validation

by Obsidian | Level 7 in Administration and Deployment
‎08-17-2017 10:53 AM
‎08-17-2017 10:53 AM
I followed the example in the post to create a script that verifies the servers in my two SAS enviornments. What is the purpose for the following option?   -serverparms "<parms>" (or -sp "<parms>") Consists of name/value pairs of server/connection attributes for the server to be validated. e.g. <parms>: "code=XXX contentlocation=XXX"  The example implies code and code directory path location that is executed by the server. Is this the case?   Cheers, jose  ... View more

Re: SMC Scheduler Manager - not saving email info on Properties tab in...

by Obsidian | Level 7 in Administration and Deployment
‎07-19-2017 04:36 PM
‎07-19-2017 04:36 PM
My title may have been auto-entered when I was searching previous topics and I found one that looked like a match.     ... View more

SMC Scheduler Manager - not saving email info on Properties tab in Flo...

by Obsidian | Level 7 in Administration and Deployment
‎07-19-2017 02:30 PM
‎07-19-2017 02:30 PM
Using SMC Schedule Manager, there is an exiting deployed job in a Flow that runs every day. A change was made to the source SAS program from which the exisitng deployed job was created from. I need to update the deployed job with the new revised SAS program. Is it as simple as just saving the new SAS program into the directory /SAS/config/Lev1/SASApp/SASEnvironment/SASCode/Jobs without having to use SMC Schedule Manager? ... View more

Re: CLI ERROR - SAS/ACCESS to Amazon Redshift

by Obsidian | Level 7 in SAS Procedures
‎10-28-2016 01:06 PM
‎10-28-2016 01:06 PM
Solution was installing a missing DLL file, which is usually included with SAS/SECURE.   Editor's note: including a few more debugging tips from SAS support.  This led to the discovery of the missing DLL. This typically indicates that SSL is not configured for use outside of SAS. Please note SSL needs to be configured for use outside of SAS per Amazons directions for an ODBC connection. Amazon documentation for this can be seen here: http://docs.aws.amazon.com/redshift/latest/mgmt/connecting-ssl-support.html   Additionally you could try setting the EncryptionMethod to 6. This uses SSL if it is available per the drivers documentation found here: https://documentation.progress.com/output/DataDirect/odbcredshifthelp/index.html#page/odbcredshifthelp/encryption-method.html#wwconnect_header   ... View more

CLI ERROR - SAS/ACCESS to Amazon Redshift

by Obsidian | Level 7 in SAS Procedures
‎10-18-2016 10:14 AM
‎10-18-2016 10:14 AM
Dear SAS Community Friends,   I recently installed the SAS/ACCESS to Amazon Redshift driver engine and I'm unsuccessful connecting to the AWS Redshift DB. Below is the code and log snippet (with altered sensitive info).   I was hoping I can get some guidance what the error means and troubleshotting tips.   Thanks in advance for your help.   LIBNAME redshift sasiorst SERVER="myserver.na-west-1.redshift.amazonaws.com" DB=prod_data USER=lab_readonly PWD="XXXXXXXXXXXX";   ERROR: CLI error trying to establish connection: [SAS][ODBC Redshift Wire Protocol driver]Socket closed. : [SAS][ODBC Redshift Wire Protocol driver]Socket closed. : [SAS][ODBC Redshift Wire Protocol driver][Redshift]FATAL: no pg_hba.conf entry for host "xx.xx.x.xxx", user "lab_readonly", database "prod_data", SSL off(File /home/rdsdb/padb/src/pg/src/backend/libpq/auth.c; Line 454; Routine ClientAuthentication; )   Current version: 9.04.01M3P062415 Operating System: WX64_WKS. Product expiration dates: ---Base SAS Software 14JAN2017 ---SAS/STAT 14JAN2017 ---SAS/GRAPH 14JAN2017 ---SAS/ETS 14JAN2017 ---SAS/OR 14JAN2017 ---SAS/IML 14JAN2017 ---SAS/QC 14JAN2017 ---SAS/Secure 168-bit 14JAN2017 ---SAS/Secure Windows 14JAN2017 ---SAS Enterprise Guide 14JAN2017 ---OR OPT 14JAN2017 ---OR PRS 14JAN2017 ---OR IVS 14JAN2017 ---OR LSO 14JAN2017 ---SAS/ACCESS Interface to Oracle 14JAN2017 ---SAS/ACCESS Interface to PC Files 14JAN2017 ---SAS/ACCESS Interface to OLE DB 14JAN2017 ---SAS/IML Studio 14JAN2017 ---SAS Workspace Server for Local Access 14JAN2017 ---SAS/ACCESS Reserved Slot 568 30SEP2016 ---High Performance Suite 14JAN2017 ... View more

Re: SAS & Windows Task Scheduler Error

by Obsidian | Level 7 in SAS Programming
‎02-17-2016 04:41 PM
‎02-17-2016 04:41 PM
Found another LIBNAME statement workaround. Interesting how there are multiple ways of creating LIBNAME statements. libname ship oledb INIT_STRING="PROVIDER=OraOLEDB.Oracle.1;Data Source=//RDBP.com:1521/RDBP.na.com; Password=zzzzzz;User ID=yyyyy;Persist Security Info=True" SCHEMA=VAL_DW dbmax_text=12000;  Source:  Oracle Call Interface Programmer's Guide Database Connection Strings for OCI Instant Client The OCI Instant Client can make remote database connections in all the ways that ordinary SQL clients can. However because the Instant Client does not have the ORACLE_HOME environment and directory structure some of the database naming methods will require additional configuration steps.   All Oracle net naming methods that do not require use of ORACLE_HOME or TNS_ADMIN (to locate configuration files such as tnsnames.ora or sqlnet.ora) work in the Instant Client mode. In particular, the connect_identifier in the OCIServerAttach() call can be specified in the following formats: ■ A SQL Connect URL string of the form: //host:port/service name such as: //dlsun242:5521/bjava21 ■ As an Oracle Net connect descriptor. For example: "(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=dlsun242) (PORT=5521)) (CONNECT_DATA=(SERVICE_NAME=bjava21)))"   ... View more

Re: SAS & Windows Task Scheduler Error

by Obsidian | Level 7 in SAS Programming
‎02-17-2016 12:00 PM
‎02-17-2016 12:00 PM
I figured out a work around by changing the Libname statement.   Old versions that did not work with Task Scheduler   libname ship oledb OLEDB_SERVICES=NO REQUIRED=YES COMPLETE=YES init_string="Provider=OraOLEDB.Oracle.1;Password=xxxxx;Persist Security Info=True;User ID=yyyyy;Data Source=RDBP" schema=VAL_DW;   libname ship oledb user='xxxxxx' password='yyyyy' datasource='RDBP' provider='OraOLEDB.Oracle.1' schema='VAL_DW';   LIBNAME ship OLEDB PROVIDER="OraOLEDB.Oracle.1" PROPERTIES=( "user id"=xxxxx password=yyyyy "data source"=RDBP schema=VAL_DW   New version that works with Task Scheduler   libname ship oledb INIT_STRING="PROVIDER=OraOLEDB.Oracle.1;Data Source=(DESCRIPTION=(SDU=16384)(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=DBP.com)(PORT=1521))) (CONNECT_DATA=(SERVICE_NAME=RDBP.com))); Password=xxxxx;User ID=yyyyy;Persist Security Info=True" SCHEMA=VAL_DW  dbmax_text=12000;   I still curious why the old versions don’t work with Task Scheduler.  ... View more

Re: SAS & Windows Task Scheduler Error

by Obsidian | Level 7 in SAS Programming
‎02-17-2016 08:34 AM
‎02-17-2016 08:34 AM
Are the environment variables set as part of the LIBNAME statement as options and/or property settings? ... View more
Contact Me
Online Status
Offline
Date Last Visited
‎03-24-2022 04:55 PM
Group Hubs for Jlochoa
View All
Likes given to
View All
Likes from
Quick links