These permissions should be enough for the oozie user on Oracle: GRANT SELECT_CATALOG_ROLE TO <OOZIE USER>; GRANT CONNECT, RESOURCE TO <OOZIE USER>; For the other databases MySQL and PostgresQL I agree with @David Streever that the permission needs to be set to just Oozie database. Additionally we want to limit the access from just the oozie host. On MySQL this can be: GRANT ALL PRIVILEGES ON <OOZIE DB>.* TO '<OOZIE USER>'@'<OOZIE HOST>' ... View more

Look at the Oozie coordinator documentation, the timezone value will be "America/New_York" and start would be something like "2015-10-12T08:00Z". Alternatively you can do a cron like thing, see the example in the following blog. Based on that it can be something like: <coordinator-app name="weekdays-at-eight-pm" frequency="0 20 * * 2-6" start="${start}" end="${end}" timezone="America/New_York" xmlns="uri:oozie:coordinator:0.2"> ... </coordinator-app> ... View more

Check out http://sqoop.apache.org/docs/1.4.2/SqoopUserGuide.html#_large_objects ... View more

One thing to check is if they are using tez. If they are, it could be possible that they do not have any capacity on their YARN cluster to launch AM. So the Hive CLI waits indefinitely to launch an AM. One thing they can do to alleviate this is to launch hive cli as "hive -hiveconf hive.execution.engine=mr". ... View more