BookmarkSubscribeRSS Feed
woo
Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10

We have sas 9.4 on linux with sas/access to impala + sas/access to hadoop

+

we have cloudera impala odbc driver - 2.5.37 version installed

+

we have ODBCINI env. variable set up for all which is pointing to user based odbcini at individual user's home directory,

 

scenario1

when we run below libname statement in interactive mode (sas -nodms) job ran fine either with read only permission OR read+write permission for odbcini file for any user.

 

scenario2

when we run job in batch mode with read only permission for odbcini file - we receive below error

 

LIBNAME hdp impala dsn=xxx schema=xxx user=xxx pw="xxx" ;
ERROR: CLI error trying to establish connection: [unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_HENV failed
ERROR: Error in the LIBNAME statement.

 

however, when we run same test with read+write permission for odbcini file, job runs fine.

 

when we asked cloudera team, they said it should be matter matter what permission odbcini file has.

 

anyone came across same issue before?

4 REPLIES 4
ChrisNZ
Tourmaline | Level 20

1- Does the test with read only permission for odbcini file work from ODBC manager?

2- Does this work?

LIBNAME hdp impala dsn=xxx schema=xxx user=xxx pw="xxx" access=readonly;

woo
Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10

Thank you for your note Chris,

 

didn't understand your first question, have different scenarios so far,

 

odbcini file with read only mode + odbcini env. variable assigned centrally (/etc/profile -> pointing to user's home dir odbcini file) - interactive mode (./sas -nodms) -> job run fine

 

odbcini file with read only mode + odbcini env. variable assigned centrally + assign odbcini env. variable explicitely into user's home dir odbcini file - interactive mode (./sas -nodms) -> job failed

 

odbcini file with read only mode + odbcini env. variable assigned centrally + batch mode (sas job_name.sas) -> job failed

 

odbcini file with read only mode + odbcini env. variable assigned centrally + assign odbcini env. variable explicitely into user's home dir odbcini file - batch mode (sas job_name.sas) -> job run fine

 

 

woo
Lapis Lazuli | Level 10 woo
Lapis Lazuli | Level 10

Also -> job failed with your option#2 (access=readonly) with cli error.

ChrisNZ
Tourmaline | Level 20

 

The important bit was at the end:

 

Does the test with read only permission for odbcini file work from ODBC manager?

 

Not from SAS. There is a "test" button in ODBC manager to test connections.

sas-innovate-2024.png

Join us for SAS Innovate April 16-19 at the Aria in Las Vegas. Bring the team and save big with our group pricing for a limited time only.

Pre-conference courses and tutorials are filling up fast and are always a sellout. Register today to reserve your seat.

 

Register now!

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

Click image to register for webinarClick image to register for webinar

Classroom Training Available!

Select SAS Training centers are offering in-person courses. View upcoming courses for:

View all other training opportunities.

Discussion stats
  • 4 replies
  • 1281 views
  • 0 likes
  • 2 in conversation