ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB 8 Windows Oracle ODBC issue

Post new topic  Reply to topic
 WMB 8 Windows Oracle ODBC issue « View previous topic :: View next topic » 
Author Message
msnyder
PostPosted: Wed May 02, 2012 5:34 am    Post subject: WMB 8 Windows Oracle ODBC issue Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

I opened a PMR on this but was wondering if anyone else was having this issue. Oracle stored proc calls that were working in 7 are getting the following exception in WMB 8:

    General error.Procedure name too long
I shortened the stored proc names just to see if that would help but to no avail. The data source is setup using the instructions in WMB 8 help including adding the WorkArounds value to the DSN registry entry.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Wed May 02, 2012 5:39 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

You need to update your Oracle driver.

Posting a general distress call like this is not helpful. What versions of everything are you running? 8.0.0.0 for WMB ? What about Oracle driver? What OS and OS version are you running? What is the exact error message, the one you posted is too short.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
msnyder
PostPosted: Thu May 03, 2012 10:50 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

Sorry, I assumed the prefix was implied . . .

The exact error message is:

    [IBM][ODBC Oracle Wire Protocol driver]General error.Procedure Name Too Long'


running under Windows 7 Enterprise Service Pack 1 64-bit with a 64-bit eg using the Oracle ODBC driver that shipped with WMB 8 configured per the documentation.

The same workstation executes the same stored proc call under WMB 7.0.0.3 using the same DSN utilizing the same WMB 8 Oracle ODBC driver.[/list]
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Thu May 03, 2012 11:01 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

You may inadvertantly be using the 32-bit Oracle driver. Turn on ODBC trace. Post the trace output here in [c od e ] tags.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
msnyder
PostPosted: Fri May 04, 2012 6:17 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

Unfortunately, I am not able to get an ODBC trace - no matter what I do. The SQL.LOG file gets created but without any trace entries. A service trace shows that the eg is using ukora24.dll and the registry's fully-qualified path is to the copy in the WMB 8 path.

Configuration wise, the DSN is configured using the 64 bit ODBC data source diaglog as opposed to the 32 bit version which doesn't list any WMB-related drivers.

The registry path is the same as the WMB doc mentions for 64 bit windows running 64 bit egs.

However, something that does seem strange is the references to 32 bit in the odbc.ini entry - I'm not even sure if it is actually being used:

    [ODBC 32 bit Data Sources]
    PTC_PTL_DSN=WebSphere Message Broker (8.0.0.0) - DataDirect Technologies 6.0 64-BIT Oracle Wire Protocol (32 bit)
    [PTC_PTL_DSN]
    Driver32=C:\Program Files\IBM\MQSI\8.0.0.0\bin\UKORA24.DLL


And the most puzzling part, is that this DSN works as-is on the same machine in WMB 7 with 64 bit egs, i.e. using the Oracle driver shipped with WMB 8. I thought it might be a path issue but that doesn't seem to be the case. Any ideas would be welcomed. Thanks.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri May 04, 2012 6:43 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

msnyder wrote:
Unfortunately, I am not able to get an ODBC trace - no matter what I do. The SQL.LOG file gets created but without any trace entries. A service trace shows that the eg is using ukora24.dll and the registry's fully-qualified path is to the copy in the WMB 8 path.

Configuration wise, the DSN is configured using the 64 bit ODBC data source diaglog as opposed to the 32 bit version which doesn't list any WMB-related drivers.

The registry path is the same as the WMB doc mentions for 64 bit windows running 64 bit egs.

However, something that does seem strange is the references to 32 bit in the odbc.ini entry - I'm not even sure if it is actually being used:

    [ODBC 32 bit Data Sources]
    PTC_PTL_DSN=WebSphere Message Broker (8.0.0.0) - DataDirect Technologies 6.0 64-BIT Oracle Wire Protocol (32 bit)
    [PTC_PTL_DSN]
    Driver32=C:\Program Files\IBM\MQSI\8.0.0.0\bin\UKORA24.DLL


And the most puzzling part, is that this DSN works as-is on the same machine in WMB 7 with 64 bit egs, i.e. using the Oracle driver shipped with WMB 8. I thought it might be a path issue but that doesn't seem to be the case. Any ideas would be welcomed. Thanks.


ukora24.dll is a 32-bit driver.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
msnyder
PostPosted: Fri May 04, 2012 6:54 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

Any idea what the 64 bit driver name is? I tried to find it without success. Thanks.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri May 04, 2012 7:01 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

msnyder wrote:
Any idea what the 64 bit driver name is? I tried to find it without success. Thanks.


You'll have to wait for your PMR to complete. They can provide you with the supported configurations. In the mean time, you might start collecting MustGather documentation.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
msnyder
PostPosted: Fri May 04, 2012 7:13 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

In the 64 bit ODBC Data Source dialog the driver is described as

    WebSphere Message Broker (8.0.0.0) - DataDirect Technologies 6.0 64-BIT Oracle Wire Protocol
with a file name of UKORA24.DLL.
Back to top
View user's profile Send private message
lancelotlinc
PostPosted: Fri May 04, 2012 7:22 am    Post subject: Reply with quote

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

msnyder wrote:
In the 64 bit ODBC Data Source dialog the driver is described as

    WebSphere Message Broker (8.0.0.0) - DataDirect Technologies 6.0 64-BIT Oracle Wire Protocol
with a file name of UKORA24.DLL.


Thats great. but your using it as a 32-bit driver:

Quote:
[ODBC 32 bit Data Sources]
PTC_PTL_DSN=WebSphere Message Broker (8.0.0.0) - DataDirect Technologies 6.0 64-BIT Oracle Wire Protocol (32 bit)
[PTC_PTL_DSN]
Driver32=C:\Program Files\IBM\MQSI\8.0.0.0\bin\UKORA24.DLL

_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Back to top
View user's profile Send private message Send e-mail
msnyder
PostPosted: Thu May 10, 2012 5:07 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

Turns out that the driver and ODBC setup were fine. The problem was fixed after replacing ImbRdl.pdb and ImbRdl.dll with fixed versions.
Back to top
View user's profile Send private message
vishBroker
PostPosted: Fri May 18, 2012 7:06 am    Post subject: Reply with quote

Centurion

Joined: 08 Dec 2010
Posts: 135

Hi,
How you changed to 'fixed versions'. Can you provide more details.
Back to top
View user's profile Send private message
msnyder
PostPosted: Fri May 18, 2012 9:04 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 32
Location: Jacksonville, FL

You'll need to open a PMR to get the fixes or wait until the 1st fix pack becomes available which should be very soon.
Back to top
View user's profile Send private message
vishBroker
PostPosted: Fri May 18, 2012 9:26 am    Post subject: Reply with quote

Centurion

Joined: 08 Dec 2010
Posts: 135

Well, the reason, I asked for some details is - I had faced same issue earlier and have opened PMR.
But we found work around.

Check below for more details-(end part)

http://www.mqseries.net/phpBB2/viewtopic.php?t=61134&sid=8bc1212c716db80cd6e0f69750962013
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMB 8 Windows Oracle ODBC issue
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.