My Oracle Support Banner

Error 'ODI-17523: There is no connection for this logical schema / context pair: PRIMAVERA_ANALYTICS_OBIEE_LS' During ODI ETL 'Cache Purge Daily' Process (Doc ID 2515160.1)

Last updated on OCTOBER 02, 2019

Applies to:

Primavera Analytics Cloud Service - Version 18.8 to 18.8 [Release 18.8]
Information in this document applies to any platform.

Symptoms

When using release 18.8 and ODI (Oracle Data Integrator), the ETL log shows the following error for the Cache Purge Daily process.

This error can occur for either/both the P6 and Unifier ETL runs.

Complete load on W_UDF_WBS_HF
Complete calculated project workdown on W_ACTIVITY_WORK_DOWN_HF
Complete calculated project work process on W_WORK_PROCESS_F
  [DONE] PROC_AFTER_LOADING_PKG_SCD
  [DONE] After loading package SCD, duration = 53 seconds
  [DONE] SCEN_OBIEE_PACKAGE
  [ERROR] OBIEE_CACHE_PURGE_DAILY
  [DONE] 0 \-\ VAR_OBIEE_CACHE_PURGE_DAILY
  [DONE] 1 /-/ Variable - VAR_OBIEE_CACHE_PURGE_DAILY - null
  [ERROR] 1 \-\ OBIEE Cache Purge Daily
  [ERROR] 2 /-/ Procedure - OBIEE Cache Purge Daily - OBIEE Cache Purge Daily
  ODI-1280: The Target Logical Schema PRIMAVERA_ANALYTICS_OBIEE_LS and Context PRIMAVERA_ANALYTICS_DS1 of the task OBIEE Cache Purge Daily are not mapped to any Physical Schema. Caused By: com.sunopsis.core.SnpsInexistantSchemaException: ODI-17523: There is no connection for this logical schema / context pair: PRIMAVERA_ANALYTICS_OBIEE_LS / PRIMAVERA_ANALYTICS_DS1. at com.sunopsis.dwg.dbobj.SnpConnect.getSnpConnectByLSchemaNameAndContext(SnpConnect.java:315) at com.sunopsis.dwg.dbobj.SnpConnect.getSnpConnect(SnpConnect.java:272) at oracle.odi.runtime.agent.execution.SessionExecutor.getSnpConnect(SessionExecutor.java:973) at oracle.odi.runtime.agent.execution.SessionExecutor.getSnpConnect(SessionExecutor.java:950) at oracle.odi.runtime.agent.execution.AbstractSessionTask.getTargetDataServer(AbstractSessionTask.java:1628) at oracle.odi.runtime.agent.execution.interpreter.SessionTaskCodeInterpreter.codeInterpretation(SessionTaskCodeInterpreter.java:107) at oracle.odi.runtime.agent.execution.interpreter.SessionTaskCodeInterpreter.codeInterpretation(SessionTaskCodeInterpreter.java:80) at oracle.odi.runtime.agent.execution.SessionTask.createTaskLog(SessionTask.java:350) at oracle.odi.runtime.agent.execution.AbstractSessionTask.execute(AbstractSessionTask.java:843) 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.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)
  [DONE] OBIEE_DUMMY
  [DONE] OBIEE Cache Purge Daily, duration = 3 seconds

 

The issue can be reproduced at will with the following steps:

  1. Log into P6 site.
  2. Select Analytics Administration.
  3. Choose Status or Startetl1 (Status) or Staretl2 (Status).
  4. Review the ETL log file and observe the reported error.

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!


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