Support Questions

Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Data Analytics (CDA) group hub.

Running the oozie job with sqoop command, no results producing

Explorer

Hello

I am running a oozie job with sqoop command in which i am taking data from the sql server and dumping it in the csv file ,having following workflow.xml,

<workflow-app xmlns="uri:oozie:workflow:0.2" name="sqoop-wf">

<start to="sqoop-node"/>

<action name="sqoop-node">

<sqoop xmlns="uri:oozie:sqoop-action:0.2">

<job-tracker>${jobTracker}</job-tracker>

<name-node>${nameNode}</name-node>

<configuration> <property> <name>mapred.job.queue.name</name> <value>${queueName}</value> </property> </configuration>

<command>import --connect jdbc:sqlserver://192.168.12.5:3306/AdventureWorksDW2014 --username sa --password sa123 --table DimCustomer --target-dir /user/root/MsSql/AdventureDB/CustomerTable -m 1

</command>

</sqoop>

<ok to="end"/>

<error to="fail"/> </action> <kill name="fail"> <message>Sqoop failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/>

</workflow-app>

with job properties as follows

  1. nameNode=hdfs://<namenode-host>:8020
  2. jobTracker=<rm-host>:8050
  3. queueName=default
  4. examplesRoot=examples
  5. oozie.use.system.libpath=true
  6. oozie.wf.application.path=${nameNode}/user/${user.name}
  7. oozie.libpat=/user/root

i used the sandbox Workflow Manager to develop this query and while Submitting the workflow i update the job Properties, my workflow is in running state and did'nt stop Also i cannot able to see any output file in the FilesView, Where i am doing wrong, Any help is highly appreciated. Thanks in Advance

2 REPLIES 2

Expert Contributor
@Sana Faraz

You would need to check the Yarn RM UI and see if there was any application launched by oozie. The name of the job would be oozie launcher, you would need to drill in to the task logs to see if there was any exception. By default the launcher job would say succeeded, you can ignore this status and drill down to see the exception trace.

Or you can issue the command: yarn logs -applicationId <applicationId_FromRM_UI>, this would need to be run from command line after login to the sandbox cli.

Explorer

@mbalakrishnan

further i installed the oozie from this site in my sandbox

https://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.0/bk_command-line-installation/content/instal...

but its giving me error at yum installl extjs2.2.1, why?

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.