Oracle 12c supported?

[peep]

[ Split from this topic]

Installed IIS v11.3.1 , Oracle client 12c and Server as well

Able to connect to oracle database from export->table definitions-->ODBCtable definitions (ODBC.ini ) file.

but when I try to connect from oracle connector stage
There is option to define oracle version (we defined 12c) --> error says 12c is invalid version.

When version set to 10 or 11 -->error message -->Error loading connector library lobccora10g.so,libclntsh.so.10.1 : can not open shared object file:No such file or directory .

Here are my dsenv entries

#######Oracle DB Configuration#####
ORACLE_HOME=/opt/app/oracle/product/ora12c/client
export ORACLE_HOME
TNS_ADMIN=$ORACLE_HOME/network/admin
export TNS_ADMIN
export PATH=$ORACLE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH


Please let me know if I am missing any thing in dsenv

[fridge]

Have a very similar issue. Installed the 12c client version to use with 12c dbase. Could get round it by creating symbolic link from the libraries that cannot be found, to the 12c equivalent libraries.
Did some more digging however and it seems that IBM only support upto 11gR2 client version with 12c dbase but this should work without any manual intervention. So we installed the 11gR2 client. We still however get the same error message.

If you search on 'JR51297' you will find more information about the Oracle connector stage & DS 11.3.

[chulett]

Could get round it by creating symbolic link from the libraries that cannot be found

I've done the same thing in the past but that was in the 9i/10g world.

[asorrell]

To be clear - the variant setting in the Oracle connector stage is used to select the variant of the Oracle client on your DataStage server, not the version of the target database. So you should install the 11gR2 client, use the 11g libraries in your Oracle environment variables, and then set the connector variant to 11, even when accessing a 12c database.

Oracle supports the 11gR2 client accessing a 12c database, so that should work.

Note: As of 11.3.1 I don't believe you can use Oracle 12c for the internal (XMETA) repository. Though some of the online documentation states that there are setup scripts for 12c, they aren't actually present on the base Linux install (I've submitted a PMR to correct the documentation).

[abc123]

What is a "variant" of the Oracle client ?

[chulett]

Version.

[rkashyap]

While investigating a similar issue on DataStage 9.12, we had found that dsenv requires Bourne shell convention; i.e. you cannot set an environment value within the context of an export command.

Try replacing

Code: Select all

export PATH=$ORACLE_HOME/bin:$PATH 
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:$LD_LIBRARY_PATH 

with

Code: Select all

PATH=$ORACLE_HOME/bin:$PATH; export PATH
ORACLE_HOME/lib:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH

Subsequently restart Node agents and DSEngine.

[ray.wurlod]

Don't you hate the way Oracle, and Oracle practitioners, put the Oracle entries at the beginning of PATH and LD_LIBRARY_PATH, as if they were the only software worth considering.

This has caused problems in the past. For DataStage, you should ensure that the DataStage libraries, etc., are found before those of any database client.

Code: Select all

PATH=$PATH:$ORACLE_HOME/bin ; export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib ; export LD_LIBRARY_PATH

[qt_ky]

Agreed!