"ORA-00904: invalid identifier" Error Received when Running ODI 12c Mapping Using "LKM Hyperion Essbase METADATA to SQL" (Doc ID 2537048.1)

Last updated on APRIL 14, 2021

Applies to:

Symptoms

An Oracle Data Integrator (ODI) environment has been upgraded from 11.1.1.9 to 12.2.1.3.0

When trying to execute a mapping which uses LKM Hyperion Essbase METADATA to SQL, the following error is received:

>ODI-1228: Task Create work table-LKM Hyperion Essbase METADATA to SQL- fails on the target connection <Connection Name>.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier
    at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:495)
    at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:447)
    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1055)
    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:624)
    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:253)
    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:613)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:214)
    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:38)
    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:891)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1194)
    at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1835)
    at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1790)
    at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:301)
    at oracle.odi.runtime.agent.execution.sql.SQLCommand.execute(SQLCommand.java:205)
    at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:142)
    at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:28)
    at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:52)
    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:748)

Changes

Cause

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