My Oracle Support Banner

Execution Of ODI Mappings / Integration Interfaces Using "LKM File to Oracle (SQLLDR)" Fails On Unix / Linux Operating System (Doc ID 424112.1)

Last updated on JANUARY 14, 2019

Applies to:

Oracle Data Integrator - Version 10.1.3.2.0 and later
Information in this document applies to any platform.

Symptoms

An Oracle Data Integrator (ODI) 12c Mapping / 11g Integration Interface loading a file into an Oracle table using SQL*Loader fails when executed on Unix / Linux systems and following message is signaled:

org.apache.bsf.BSFException: exception from Jython: Traceback (innermost last):
File "", line 3, in ?
OS command has signalled errors

  at org.apache.bsf.engines.jython.JythonEngine.exec(Unknown Source)
  at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
  at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
  at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
  at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
  at com.sunopsis.dwg.cmd.e.i(e.java)
  at com.sunopsis.dwg.cmd.h.y(h.java)
  at com.sunopsis.dwg.cmd.e.run(e.java)
  at java.lang.Thread.run(Thread.java:534)

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
 1. Verify that the Unix / Linux user has appropriate access to SQLLDR...
 2. Verify that the Unix / Linux user has appropriate privileges to the files to process...
 3. Delete the Jython cache...
 4. Adjust the LKM (if the issue persists)...
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.