My Oracle Support Banner

Wrong Date Format Passed In Parameter in ODI Console (Doc ID 2579310.1)

Last updated on AUGUST 27, 2019

Applies to:

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

Symptoms

When attempting to run a scenario that uses a date variable in ODI Console, the below error occurs:

ODI-1217: Session <SESSION_NAME> (<NUMBER>) fails with return code 7000.
Caused By: oracle.odi.core.exception.OdiRuntimeException: ODI-1022: The variable value Tue Apr 16 16:47:11 EEST 2019 for variable <VARIABLE_NAME> is not compatible with the variable type D
at oracle.odi.runtime.agent.execution.SessionExecutor.updateVarWithSessVar(SessionExecutor.java:1494)
at oracle.odi.runtime.agent.execution.SessionExecutor.treatSessVariables(SessionExecutor.java:1447)
at oracle.odi.runtime.agent.execution.SessionExecutor.initSessVariables(SessionExecutor.java:1437)
at oracle.odi.runtime.agent.execution.SessionExecutor.initSession(SessionExecutor.java:1194)
at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:603)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:718)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor$1.doAction(TaskExecutorAgentRequestProcessor.java:611)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:203)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doProcessStartAgentTask(TaskExecutorAgentRequestProcessor.java:800)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.access$2700(StartScenRequestProcessor.java:85)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:917)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:180)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:108)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at oracle.odi.runtime.agent.execution.job.OdiJob.call(OdiJob.java:73)
at oracle.odi.runtime.agent.execution.job.OdiJob.call(OdiJob.java:73)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.text.ParseException: Unparseable date: "Tue Apr 16 16:47:11 EEST 2019"
at java.text.DateFormat.parse(DateFormat.java:366)
at oracle.odi.runtime.agent.invocation.request.support.OdiDateFormat.parse(OdiDateFormat.java:47)
at com.sunopsis.dwg.dbobj.SnpVarSess.setValue(SnpVarSess.java:980)
at com.sunopsis.dwg.dbobj.SnpVarSess.setValue(SnpVarSess.java:739)
at oracle.odi.runtime.agent.execution.SessionExecutor.updateVarWithSessVar(SessionExecutor.java:1487)
... 19 more


The issue can be reproduced at will with the following steps:
1. Create a package that uses a date variable and generate a scenario from it.
2. Run the scenario in ODI Studio.
3. Run the scenario in ODI Console.

There appears to be a difference in the date format passed to the variable in ODI Console and ODI Studio.

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
References


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