My Oracle Support Banner

ODI 12c Receives "ODI-40449: File Not Found" when Accessing a File on a Windows Mapped Drive (Doc ID 2465145.1)

Last updated on MARCH 12, 2021

Applies to:

Oracle Data Integrator - Version 12.2.1.2.6 and later
Microsoft Windows x64 (64-bit)
Microsoft Windows (32-bit)

Symptoms

When attempting to execute a job that accesses a file located in a Windows mapped directory thru an Oracle Data Integrator (ODI) 12c Standalone Agent,  the following error occurs:

[2018-10-19T19:03:07.134+02:00] [odi] [ERROR] [ODI-1217] [oracle.odi.agent]... [oracle.odi.runtime.AgentName: StandaloneAgent] [oracle.odi.runtime.ExecPhase: ExecuteTask] [oracle.odi.runtime.OdiUser: <USER>] [oracle.odi.runtime.WrepName: <WORKREP>] [oracle.odi.runtime.ScenarioName: <SCENARIO>] [oracle.odi.runtime.ScenarioVer: <VERSION>] [oracle.odi.runtime.EntityGuid: <GUID>] [oracle.odi.runtime.SessName: <SESSION>] [oracle.odi.runtime.SessId: <ID>] [oracle.odi.runtime.SessStep: 10/<Physical_STEP>/1] [oracle.odi.runtime.SessTask: 10.60/Truncate,IKM SQL to File Append,null]

[oracle.odi.runtime.ExecHierarchy: 2/16] Session <SESSION> fails with return code

ODI-1298.[[
ODI-1217: Session <SESSION> fails with return code ODI-1298.
ODI-1226: Step <Physical_STEP> fails after 1 attempt(s).
ODI-1240: Flow <Physical_STEP> fails while performing a Truncate-IKM SQL to File Append- operation. This flow loads target table null.
ODI-1298: Serial task "SERIAL-MAP_MAIN-<TASK>" failed because child task "SERIAL-<TASK2>" is in error.
ODI-1298: Serial task "SERIAL-<TASK2>" failed because child task "Truncate-IKM SQL to File Append- (<ID>)" is in error.
ODI-1228: Task Truncate-IKM SQL to File Append- fails on the target connection <CONNECTION>.
Caused By: java.sql.SQLException:

ODI-40449: File not found: \\<remote_servername>\<directory_name>/<FILE>
  at com.sunopsis.jdbc.driver.file.FileTruncator.truncateFile(FileTruncator.java:40)
  at com.sunopsis.jdbc.driver.file.impl.commands.CommandTruncate.execute(CommandTruncate.java:39)
  at com.sunopsis.jdbc.driver.file.CommandExecutor.executeCommand(CommandExecutor.java:34)
  at com.sunopsis.jdbc.driver.file.FileStatement.execute(FileStatement.java:83)
  at oracle.odi.runtime.agent.execution.sql.SQLCommand.execute(SQLCommand.java:205)
  at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:142)

Changes

 

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
Changes
Cause
Solution
References


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