Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 09-12-2016 03:16 PM
img.pngwe are getting below error/exception while executing sqoop action via oozie .
Error - Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), java.lang.ClassNotFoundException: Class org.apache.oozie.action.hadoop.SqoopMain not found
It seems some jars related to sqoop action not available on oozie share lib path i.e. “/user/oozie/share/lib/lib_20160807001458/sqoop”. We are getting access issues while trying to update the oozie share lib path with required jars.
Created 09-12-2016 05:58 PM
@kishore sanchina: You are getting permission issue because user(which you have used to login) does not have admin role on cluster. So please try with oozie user, you can do sudo to oozie.
sudo su - oozie
or
su oozie
Created 09-12-2016 05:58 PM
@kishore sanchina: You are getting permission issue because user(which you have used to login) does not have admin role on cluster. So please try with oozie user, you can do sudo to oozie.
sudo su - oozie
or
su oozie
Created 09-13-2016 06:59 PM
You are executing an oozie admin command, so you need to be using an oozie admin user. Usually 'oozie' user is configured as admin user in oozie You can take look at the 'adminusers.txt' file under oozie configuration. Once you switch to an oozie admin user, you should be able to update the oozie sharelib. 'sudo su - oozie'
The another error which you have mentioned regarding the 'java.lang.ClassNotFoundException: Class org.apache.oozie.action.hadoop.SqoopMain not found', I guess you did not specify the 'oozie.use.system.libpath=true' into your "job.properties" file. This should resolve both of your issues.
Note: If 'oozie.use.system.libpath=true' property was missing then just add it and submit/run the workflow, you need not to update the oozie share lib.