My Oracle Support Banner

"ODI-17523: There Is No Connection For This Logical Schema / Context Pair" Error Received when Executing ODI 12c Mapping Containing a Native Sequence (Doc ID 2345559.1)

Last updated on FEBRUARY 16, 2018

Applies to:

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

Symptoms

When attempting to execute an Oracle Data Integrator (ODI) 12c mapping which contains a Native (database) sequence, the following error stack is received:

ODI-1226: Step Physical_STEP fails after 1 attempt(s).
ODI-1240: Flow Physical_STEP fails while performing a Insert new rows-IKM Oracle Control Append- operation. This flow loads target table <TABLE NAME>.
ODI-1298: Serial task "SERIAL-MAP_MAIN- (10)" failed because child task "<TASK NAME> (20)" is in error.
ODI-1298: Serial task "<TASK NAME> (20)" failed because child task "Insert new rows-IKM Oracle Control Append- (50)" is in error.
Caused By: com.sunopsis.core.SnpsInexistantSchemaException: ODI-17523: There is no connection for this logical schema / context pair: <SCHEMA NAME> / <CONTEXT NAME>.
    at com.sunopsis.dwg.dbobj.SnpConnect.getSnpConnectByLSchemaNameAndContext(SnpConnect.java:315)
    at oracle.odi.query.NativeSequenceNextValueGetter.isValidForSubstitution(NativeSequenceNextValueGetter.java:61)
    at oracle.odi.query.SubstitutionHelper.getSubstitutedText(SubstitutionHelper.java:94)
    at oracle.odi.runtime.agent.execution.cmd.TextCommand.initialize(TextCommand.java:81)
    at oracle.odi.runtime.agent.execution.sql.SQLCommand.initialize(SQLCommand.java:86)
    at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:51)
    at oracle.odi.runtime.agent.execution.SessionTask.processTask(SessionTask.java:206)
    at oracle.odi.runtime.agent.execution.SessionTask.doExecuteTask(SessionTask.java:117)
    at oracle.odi.runtime.agent.execution.AbstractSessionTask.execute(AbstractSessionTask.java:886)
    at oracle.odi.runtime.agent.execution.SessionExecutor$SerialTrain.runTasks(SessionExecutor.java:2225)
    at oracle.odi.runtime.agent.execution.SessionExecutor.executeSession(SessionExecutor.java:610)
    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.StartSessRequestProcessor.access$1400(StartSessRequestProcessor.java:74)
    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:702)
    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.lang.Thread.run(Thread.java:745)

Changes

 Customer has migrated from Oracle Warehouse Builder (OWB) to Oracle Data Integrator (ODI).  Issue can occur even when ODI was not migrated from OWB.

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.