OPLA 3.6 Not Able to Run/Start Full ETL Load, Fails at DBLink Creation Error: ODI-1226: Step odi_int_CREATE_DBLINK fails after 1 attempt(s).

(Doc ID 2355455.1)

Last updated on JANUARY 31, 2018

Applies to:

Oracle Product Lifecycle Analytics - Version 3.6.0 and later
Information in this document applies to any platform.

Symptoms

On : 3.6.0 version, When attempting to run Full ETL the following error occurs.

ERROR
-----------------------
ODI-1226: Step odi_int_CREATE_DBLINK fails after 1 attempt(s).
ODI-1240: Flow odi_int_CREATE_DBLINK fails while performing a Loading operation. This flow loads target table null.
ODI-1228: Task SS_0 (Loading) fails on the target ORACLE connection TRG_ODMCONN_PHYSICAL.
Caused By: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)

ODI-1228: Task SS_0 (Loading) fails on the target ORACLE connection TRG_ODMCONN_PHYSICAL.
Caused By: java.sql.SQLException: ORA-12154: TNS:could not resolve the connect identifier specified
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Upgraded OPLA 3.5 to 3.6
Source Agile Oracle DB is upgraded from 11G to 12C.
The existing oracle DB client in Appserver is installed using 11G.
Using existing 11G DB client for 12C DB server.
Not Able to Run/Start Full ETL Load.

Cause

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 hundreds of Community platforms