DSXchange

Dear All,

One of the Datastage job was accessing Oracle DB through ODBC connector stage. It is Oracle 11g version. Now as per new requirement we should switch to new Oracle DB that is 12C version. DB team kept user name and password same as old DB. We have updated existing Oracle DB entry of odbc.ini and change the hostname and port number entry for new DB as follows

--------------------------------

[XXXXX]
Driver=/opt/IBM/InformationServer/Server/branded_odbc/lib/VMora25.so
Description=DataDirect Oracle Wire Protocol
ApplicationUsingThreads=1
ArraySize=60000
CachedCursorLimit=32
CachedDescLimit=0
CatalogIncludesSynonyms=1
CatalogOptions=0
DefaultLongDataBuffLen=1024
DescribeAtPrepare=0
EnableDescribeParam=0
EnableNcharSupport=0
EnableScrollableCursors=1
EnableStaticCursorsForLongData=0
EnableTimestampWithTimeZone=0
HostName=XX.XX.XXX.XXX
LocalTimeZoneOffset=
LockTimeOut=220
LogonID=xxxx
Password=xxxx
PortNumber=1531
ProcedureRetResults=0
ServiceName=edhprod
UseCurrentSchema=0

------------------------------------------

We are facing following error on job run

"
PKG_CHANGE: ODBC function "SQLConnect" reported: SQLSTATE = HY000: Native Error Code = 28,040: Msg = [IBM(DataDirect OEM)][ODBC Oracle Wire Protocol driver][Oracle]ORA-28040: No matching authentication protocol (CC_OdbcConnection::connect, file CC_OdbcConnection.cpp, line 598)


"

Please let me know how to fix it.

Thanks,

Have you validated that the version of Branded ODBC driver that you are using is blessed for that version of Oracle?

BTW: now would be a good time to transition to Connector stages, also... time to upgrade your release level of DataStage still using 8.x? tsk tsk

Thanks Paul for your response. As you mentioned about validation of branded odbc. Please elaborate it further how should I do this.

Thanks,

You look at the version you have installed on your hosts, then you consult the documentation to see if Oracle version 11g is supported.

(google the driver version). But most likely if you are still using DataStage 8.x, you might not have updated your ODBC drivers in some time... and you got pinched with this compatibility issue.

(ask the developers to change the job to use a Connector stage and see if that works better for you)

Dear Paul,

I have looked into fix Central and found odbc driver as follows

---------------------------------------
interim fix: is_ddodbc_7.1.4_server_aix

DataDirect (OEM) 7.1.4 ODBC Drivers, for InfoSphere Information Server

The following files implement this fix.
---------------------------------------------

If we install this odbc driver will it fix our issue.



Thanks,

That would be a question for IBM Support. Oh, wait... 8.x? Never mind.

Try it, let us know.

Why are you using ODBC rather than native connectivity?