Author |
Message
|
MadBrocker |
Posted: Thu Sep 29, 2016 12:26 am Post subject: Patch 9.0.0.6 ODBC driver issue ORACLE |
|
|
Newbie
Joined: 29 Sep 2016 Posts: 4
|
Hi! Need help on issue that is connected with an update on Integration Bus ver. 9.0.0.6. The problem with oracle ODBC driver ver. 07.16.0265 (B0299, U0201) (last working version of Oracle ODBC driver is 07.15.0229) that comes with a patch and thus doesn`t work in a proper way: When calling an Oracle PL/SQL procedure out of an Integration Bus, it binds veriables not in a proper sequence.
Example from trace file on the Database level:
Old driver version:
Bind#0
oacdty=01 mxl=32767(32767) mxlc=00 mal=00 scl=00 pre=00
oacflg=01 fl2=1000000 frm=01 csi=171 siz=32767 off=0
kxsbbbfp=700000f67d30690 bln=32767 avl=306 flg=05
value="<Changes_request><document><DOC_NAME>*****</DOC_NAME><OPERATION>******</OPERATION><EXTERNAL_ID>1*****0</EXTERNAL_ID><details><ACKL_NO>****</ACKL_NO><ACKL_NOCT>*******</ACKL_NOCT><ACKL_NOSET>******</ACKL_NOSET><ACKL_NOY>UAH</ACKL_NOY><ACKL_NO_C>*****</ACKL_NO_C><GROUPC"...
Bind#1
oacdty=01 mxl=32767(32767) mxlc=00 mal=00 scl=00 pre=00
oacflg=01 fl2=1000000 frm=01 csi=171 siz=32767 off=0
kxsbbbfp=700000f6fcdf030 bln=32767 avl=00 flg=05
With new driver:
Bind#0
oacdty=01 mxl=32767(32767) mxlc=00 mal=00 scl=00 pre=00
oacflg=01 fl2=1000000 frm=01 csi=171 siz=32767 off=0
kxsbbbfp=700000f67d30690 bln=32767 avl=00 flg=05
Bind#1
oacdty=01 mxl=32767(32767) mxlc=00 mal=00 scl=00 pre=00
oacflg=01 fl2=1000000 frm=01 csi=171 siz=32767 off=0
kxsbbbfp=700000f6fcdf030 bln=32767 avl=667 flg=05
value="<Changes_request><document><DOC_NAME>*******</DOC_NAME><OPERATION>*******</OPERATION><EXTERNAL_ID>********</EXTERNAL_ID><details><CARD>*******</CARD><BASE_SUPP>****</BASE_SUPP><ACKL_NO_SET>***</ACKL_NO_SET><RISK_LEVEL>A</RISK_LEVEL><ACKL_NO_NAME>MADBROCKER"...
Have anyone faced with the same issue? Is there any fix for this issue? |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 29, 2016 5:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Why are you using the Oracle ODBC driver?
That's not supported for Broker. You need to use the correct ODBC driver that comes with Broker. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
MadBrocker |
Posted: Thu Sep 29, 2016 7:04 am Post subject: |
|
|
Newbie
Joined: 29 Sep 2016 Posts: 4
|
We are using ODBC driver that comes with the Broker, but with patch 9.0.0.6, the driver (that comes with a broker) was also updated from version 07.15.0229 to 07.16.0265. And since this update I`am facing issue that was described above.  |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 29, 2016 7:34 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
MadBrocker wrote: |
We are using ODBC driver that comes with the Broker, |
That's not what my DataDirect ODBC driver (albeit in 9.0.0.5) calls itself.
MadBrocker wrote: |
but with patch 9.0.0.6, the driver (that comes with a broker) was also updated from version 07.15.0229 to 07.16.0265. |
And mine doesn't have that numbering scheme.
What OS is this? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
MadBrocker |
Posted: Thu Sep 29, 2016 7:58 am Post subject: |
|
|
Newbie
Joined: 29 Sep 2016 Posts: 4
|
Vitor wrote: |
MadBrocker wrote: |
We are using ODBC driver that comes with the Broker, |
That's not what my DataDirect ODBC driver (albeit in 9.0.0.5) calls itself.
MadBrocker wrote: |
but with patch 9.0.0.6, the driver (that comes with a broker) was also updated from version 07.15.0229 to 07.16.0265. |
And mine doesn't have that numbering scheme.
What OS is this? |
AIX 6.1
Path to the driver - Driver=/usr/opt/IBM/mqsi/9.0/ODBC/V7.0/lib/UKora26.so
Got detailed information about driver using mqsicvp command. (driverVersion parameter) |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 29, 2016 8:15 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
MadBrocker wrote: |
AIX 6.1 |
Weird.  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Sep 29, 2016 1:49 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Hrm.
Is it possible you need to adjust the workarounds parameter of the odbc definition?
The correct value would be shown in the Broker documentation, and would be different than the one you have now.
I'm guessing you've also done nothing to change the code or the database since you updated to the new FP...
If all of those look the same, then probably open a PMR. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
MadBrocker |
Posted: Thu Sep 29, 2016 10:14 pm Post subject: |
|
|
Newbie
Joined: 29 Sep 2016 Posts: 4
|
mqjeff wrote: |
Hrm.
Is it possible you need to adjust the workarounds parameter of the odbc definition?
The correct value would be shown in the Broker documentation, and would be different than the one you have now.
I'm guessing you've also done nothing to change the code or the database since you updated to the new FP...
If all of those look the same, then probably open a PMR. |
ODBC definition is quite like in documention:
Code: |
[SOMEORACLEDB]
Driver=/usr/mqsi/ODBC/V7.0/lib/UKora26.so
Description=DataDirect 5.3 64bit Oracle Wire Protocol
HostName=*******
PortNumber=*******
SID=********
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1 |
I wonder, what may be the cause of an issue? When I try to use driver from the previous installation everything works fine. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Sep 30, 2016 3:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
MadBrocker wrote: |
I wonder, what may be the cause of an issue? When I try to use driver from the previous installation everything works fine. |
It sounds like a defect in the product.
Look for new iFixes, and then open a PMR. _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
|