| Author |
Message
|
| toca |
 Posted: Wed Feb 16, 2011 4:28 am Post subject: DataDirect ODBC Oracle Wire driver for Windows 32 bit? |
 |
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
Anyone know if there exists such driver for WMB 6.1 ?
In the installation i can only find the "none"-wire driver (ver 5.3).
I need this driver in order to connect to multiple oracle data bases with different code sets (UNICODE and none-UNICODE) from one machine.
I have installed the fix pack up to version 8 but no new driver were installed.
Thanks in advance for any help! |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Feb 16, 2011 5:13 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| toca |
| Posted: Wed Feb 16, 2011 5:28 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
Thanks, but I already knew that.
I actually used this trial version to confirm that it solved my problems.
But the thing is that I don't want to purchase this driver from DataDirect if I can get it from IBM. But hours of searching on IBM support pages gives me nothing in this matter.
Hence this topic...
So to clarify, I do know that this driver exists but can it be downloaded from IBM support pages anywhere? |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Feb 16, 2011 5:41 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Quote: |
The DataDirect ODBC drivers supplied with WebSphere Message Broker, and the corresponding sample ODBC .ini files, were updated for all platforms except HP-UX on PA-RISC at Version 6.1.0.2 (Fix Pack 2), and for HP-UX on PA-RISC at Version 6.1.0.3 (Fix Pack 3).
If your current installation is at Version 6.1.0.0 or Version 6.1.0.1 (Fix Pack 1), you must make additional changes to your ODBC connections when you apply Version 6.1.0.2 (Fix Pack 2) or later.
|
http://www-01.ibm.com/support/docview.wss?uid=swg27011222
Did you do this?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| toca |
| Posted: Wed Feb 16, 2011 6:01 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
Yes, that was made when we installed fix pack 2. That's when we changed to this "new" driver as the documentation describe.
I currently have only one oracle ODBC driver installed now and that is the same as metioned in the documentation:
"MQSeries DataDirect Technologies 5.3 32-BIT Oracle"
This driver uses the oracle client installation which is not working for me because I need different NLS_LANG in communication with multiple oracle instances.
Thats why the Wire-driver fits perfectly because it does not use that client settings at all. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Feb 16, 2011 6:04 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Please recheck your compliance with these instructions:
| Quote: |
Oracle
Define a data source for Oracle:
Select the driver WebSphere Message Broker DataDirect Technologies 6.00 32-BIT Oracle Wire Protocol.
The ODBC Oracle Driver Setup dialog box opens.
On the General tab:
Enter the DSN name, description, and host name of the machine where Oracle is running, the port number on which Oracle is listening and the Oracle SID that you want to connect to.
On the Advanced tab:
Select Enable SQLDescribeParam.
Select Procedure Returns Results. The resultant ODBC definition in the Windows registry has a string value called ProcedureRetResults with the value 1.
Select Login Timeout and set the value to 0.
Click OK to close the ODBC Data Source Administrator.
Click Start > Run.
Type REGEDIT in the Open field and click OK.
In the Registry Editor, navigate to the correct location.
On Windows 32–bit editions: HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
On Windows 64–bit editions: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI
Expand that location, and right-click your DSN entry. Select New > String Value.
Specify WorkArounds for the string name.
Right-click WorkArounds.
Select Modify.
Type the data value 536870912.
Close the Registry Editor.
|
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| toca |
| Posted: Wed Feb 16, 2011 6:09 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
I really which I could lancelotinc, but I dont have:
| Code: |
| DataDirect Technologies 6.00 32-BIT Oracle Wire Protocol. |
installed.
And I don't know where (or if) I can get it.
Are you running WMB61? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 16, 2011 6:15 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You need to do a little more research in how to configure the Windows DSN using the presupplied driver to connect using a connection string/SID rather than a ServerName and tnsnames.ora.
Certainly the v6 level of the DD driver is capable of acting either as a wire driver or using a local Oracle client. I'm reasonably positive that the v5.3 is as well - but I'm not going to dig through DD's website to find the documentation on the v5.3 driver that would explain it.
But I don't know that you will resolve your NSL_LANG issue this way. Broker itself can only run with a single NLS_LANG environment variable set. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Feb 16, 2011 6:16 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
DataDirect Technologies 5.30 32-BIT Oracle Wire Protocol comes with 6.1.0.2 Fixpack. DataDirect Technologies 6.00 32-BIT Oracle Wire Protocol comes with 7.0.0.1.
In order to use either, you must carefully follow the instructions, including the registry edit. Did you edit your registry as specified?
If you followed carefully these instructions and you are unable to get the product to work as specified, then open a PMR.
If you open a PMR, please post back the resolution so someone following you with same problem will know what to do. Thanks in advance, Lance.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Feb 16, 2011 6:25 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Here is the manifest for ODBC drivers for 6.1.0.9:
http://www-01.ibm.com/support/docview.wss?uid=swg21372148
Also note that Windows has two ODBC config programs. One is 32-bit and the other is 64-bit. If you are opening the 64-bit version of the ODBC config program, the 32-bit drivers will not be visible, yet they are still installed on the system. WMB only supports 32-bit ODBC drivers on Windows platform.[/quote]
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| toca |
| Posted: Thu Feb 17, 2011 1:30 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
Ok, here is what I did.
1. I removed the WMB installation completly.
2. Installed again.
3. Added fixpack 6.1.0-WS-MB-WINIA32-FP0001.exe and 6.1.0-WS-MB-WINIA32-FP0002.exe.
The only thing that is updated regarding ODBC drivers is that the oracle driver change from UKOR822.DLL to UKOR823.DLL (5.30.00.99).
But in my opinion this is still not the Wire driver?!
Because when I open the ODBC config I get the same view as the last time. The view where you suppose to select oracle client version which as I see it is a proof of that I don't have the correct driver yet.
The ODBC screen after fix pack 2
I tried Workaround 536870912 on created DSN but still the same screen above.
The ODBC screen as it should be (this is from my installation of the driver trial version on another machine):
I'm confused... |
|
| Back to top |
|
|
| toca |
| Posted: Thu Feb 17, 2011 2:15 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
| mqjeff wrote: |
Certainly the v6 level of the DD driver is capable of acting either as a wire driver or using a local Oracle client. I'm reasonably positive that the v5.3 is as well - but I'm not going to dig through DD's website to find the documentation on the v5.3 driver that would explain it.
|
I read the documentation on the DataDirect web page.
It's clearly a distinguised different in the non-Wire and the Wire protocol DSN setup instruction.
Non-wire (page 455)
Wire (page 258)
http://www.datadirect.com/download/docs/odbc/odbcuser/odbcuser.zip
Conclusion: I don't think I can force the non-Wire driver to act like a Wire driver.
But I would be glad if you could proove me wrong! |
|
| Back to top |
|
|
| toca |
| Posted: Fri Feb 18, 2011 8:52 am Post subject: |
|
|
Newbie
Joined: 16 Feb 2011
Posts: 7
Location: Sweden
|
| lancelotlinc wrote: |
| DataDirect Technologies 5.30 32-BIT Oracle Wire Protocol comes with 6.1.0.2 Fixpack. |
Where did you get this info?
I mean I know that the DataDirect 5.3 (non-Wire) comes with a new version in fix pack 2, but not any wire-driver!?
Also I already have a PMR for this. But it gave me nothing. That's why I am tryning with this forum. |
|
| Back to top |
|
|
| Andrew Ford |
| Posted: Wed Apr 13, 2011 12:12 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2011
Posts: 1
|
Just to clarify.
Broker V6.1
On 32 bit windows broker V6.1 uses the V5.3 Data Direct client based driver to access Oracle. This level of broker has not been certified to use the wire protocol driver.
Broker V7.0
For Broker V7.0 the 32 bit V6.0 Data Direct wire protocol drivers are used to access Oracle. Broker V7.0 no longer ships with the 32 bit client based drivers. |
|
| Back to top |
|
|
|
|
