PH18716: "ERROR WHILE RUNNING THE SQOOP JOB. SEE JOB LOG FILES" MESSAGE SEEN INTERMITTENTLY WITH A LOAD STATEMENT

APAR status

• Closed as fixed if next.

Error description

• Error in Terminal session when running LOAD statement:
  
  [IBM][CLI Driver][DB2/LINUXX8664] SQL5105N The statement failed
  because a Big SQL component encountered an error. Component
  receiving the error: "DDL FMP". Component returning the error:
  "DDL FMP". Log entry identifier: "[BSL-0-6270d7adb]".
  SQLSTATE=58040 SQLCODE=-5105
  
  From bigsql.log
  
  ERROR com.ibm.biginsights.biga.udf.SqlReturn [Thread-311608] :
  [BSL-0-6270d7adb]: Internal error: Error while running the Sqoop
  job. See job log files.
  Error while running the Sqoop job. See job log files.
   at
  com.ibm.biginsights.ie.db.DBImportImpl.importData(DBImportImpl.j
  ava:183)
   at
  com.ibm.biginsights.ie.impl.ImporterImpl.executeImport(ImporterI
  mpl.java:569)
   at
  com.ibm.biginsights.ie.impl.ImporterImpl.executePerformImport(Im
  porterImpl.java:423)
   at
  com.ibm.biginsights.ie.impl.ImporterImpl.performImport(ImporterI
  mpl.java:266)
   at
  com.ibm.biginsights.biga.udf.LoadTool.performImport(LoadTool.jav
  a:240)
   at
  com.ibm.biginsights.biga.udf.BIGSQL_DDL.performLoad(BIGSQL_DDL.j
  ava:1556)
   at
  com.ibm.biginsights.biga.udf.BIGSQL_DDL.doLoadStatement(BIGSQL_D
  DL.java:1397)
   at
  com.ibm.biginsights.biga.udf.BIGSQL_DDL.processDDL(BIGSQL_DDL.ja
  va:256)
  
  After turning additional sqoop logging on we see
  
  DEBUG org.apache.sqoop.Sqoop [Thread-311608] : must specify
  longopt
  java.lang.IllegalArgumentException: must specify longopt
      at
  org.apache.commons.cli.OptionBuilder.create(OptionBuilder.java:3
  30)
      at
  org.apache.sqoop.tool.BaseSqoopTool.getCommonOptions(BaseSqoopTo
  ol.java:456)
      at
  org.apache.sqoop.tool.ImportTool.configureOptions(ImportTool.jav
  a:849)
      at
  org.apache.sqoop.tool.SqoopTool.parseArguments(SqoopTool.java:43
  1)
      at org.apache.sqoop.Sqoop.run(Sqoop.java:138)
      at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
      at org.apache.sqoop.Sqoop.runSqoop(Sqoop.java:186)
      at
  com.ibm.biginsights.ie.db.SqoopUtils.runSqoopTool(SqoopUtils.jav
  a:146)
      at
  com.ibm.biginsights.ie.db.DBImportImpl.importData(DBImportImpl.j
  ava:178)
      at
  com.ibm.biginsights.ie.impl.ImporterImpl.executeImport(ImporterI
  mpl.java:569)
      at
  com.ibm.biginsights.ie.impl.ImporterImpl.executePerformImport(Im
  porterImpl.java:423)
      at
  com.ibm.biginsights.ie.impl.ImporterImpl.performImport(ImporterI
  mpl.java:266)
      at
  com.ibm.biginsights.biga.udf.LoadTool.performImport(LoadTool.jav
  a:240)
      at
  com.ibm.biginsights.biga.udf.BIGSQL_DDL.performLoad(BIGSQL_DDL.j
  ava:1556)
      at
  com.ibm.biginsights.biga.udf.BIGSQL_DDL.doLoadStatement(BIGSQL_D
  DL.java:1397)
      at
  com.ibm.biginsights.biga.udf.BIGSQL_DDL.processDDL(BIGSQL_DDL.ja
  va:256)
  .
  The issue is with intermittent failures occurring in Sqoop
  before the MapReduce job is submitted to Yarn resulting in the
  Load job failing.  In the case where Sqoop connectors are used
  with a JDBC source, we can retry the Sqoop call if a failure
  happens early, to allow for the Load job to succeed if the Sqoop
  failures are intermittent.
  .
  As part of the fix, two properties have been added to Big SQL.
  The default values are:
  .
  bigsql.sqoop.retry.num=3
  The number of times sqoop will be retried.
  .
  bigsql.sqoop.retry.enabled=true
  When enabled the retry will be attempted.
  .
  These defaults can be changed by adding these properties to the
  bigsql-conf.xml file and recycling the Big SQL service.
  

Local fix

• Rerunning the LOAD completes successfully
  

Problem summary

• Please see problem discription.
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels