Hi Jeff,   Thanks, I actually forgot to post the solution.   I'm not a Hadoop expert....so this is my understanding. At our site we cannot connect directly to Hive. We connect to Hive via ZooKeeper, hence the need for the URI option. The HA topic has never come up, so I would assume it's not that.   The cause of the problem, was the credentials I connect to Hadoop with. This site uses Kerberos. If I generate the TGT with my user in upper case, all is ok and I can see the Hive database. If I generate my TGT in lowercase, it fails with the above error. It's bizarre. For some reason Hadoop only authorises my when I'm uppercase, but will authenticate me either way. Funny enough, Ambari doesn't care how I sign on and I can see all resources I have been granted access to. ... View more

Thanks Chris, will do. ... View more

If you haven't already, start keeping a very detailed user inventory, with things like: - Contact details - Computer name(s) - Licensed for PC SAS ? Y - N - N/A - Maiden names (...I kid you not) - HR reporting details - Org structure - Etc. - Etc.   Make it an ingrained practice to keep this list 110% updated. When you start dealing with hundreds of users on enterprise level, it's like herding cats without this information. I used to run a SAS shop for a major bank with ~500 users and I can honestly tell you this will be one of your biggest assets. Without this, you are running around in the dark. ... View more

Thanks Chris,   Yes, that is exactly what I need, but not under SAS/Access to Haddop, but rather just a generic JDBC connection (engine). So imagine something like SAS/Access to JDBC where you can specify your own JDBC URI in the libname. For example ....   LIBNAME mylib JDBC URI="<< my custom JDBC connection string>>"; RUN;   ... View more

This is actually a great discussion starter....   You are correct, SAS is a vast and broad field and I seriously doubt if there is a single silver bullet answer to this. However, I can (and I'm sure our fellow community members would too) share with you some personal experiences to help you on this journey.....and I specifically say 'journey'   For me personally, troubleshooting is a field of interest. Most of what I have learnt from SAS has come from sitting and hacking away at  problems until solved. This process then let's you discover all sorts of wierd and wonderful things, in- and outside of the SAS world. If you've ever watch House MD on TV.....it's similar to that.   Also, I was very fortunate to have worked for SAS Institute for some years, which was a great experience. An employer of choice by far !! ... View more

You will place you Oracle variables in sasenv_local. If you have users that will use the Oracle utilities OUTSIDE of SAS, then yes, those values will need to be in their .profile scripts as well. It's unlikely since your users will probably want to connect to Oracle from SAS, but possible. ... View more

I agree with @LinusH. This is an usual use case. Its like Enterprise Guide calling itself in a way. I would also reconsider. "Usually" X commands are used to call commands, etc. ouside of SAS e.g. OS commands, custome UNIX scripts, etc. Any SAS code you need to run can run from that same session that is running the X command. But again, there are many use cases out there in the real world...so let's see. ... View more