MQSeries.net :: View topic - Oracle 11g client on Win 2008 server MB v7

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Oracle 11g client on Win 2008 server MB v7

Goto page 1, 2 Next

Oracle 11g client on Win 2008 server MB v7

« View previous topic :: View next topic »

Author

Message

ydsk

Posted: Wed Dec 01, 2010 11:23 am Post subject: Oracle 11g client on Win 2008 server MB v7

Chevalier

Joined: 23 May 2005
Posts: 410

We have a MB v7 instance on Windows 2008 server. We need to use a Oracle client to connect to a remote Oracle 10g database, thru an Oracle client version 11.01.x

We have the Oracle client installed already but need to configure the ODBC system DSN names for 2 remote user databases..

The broker documentation says Windows supports only 32-bit ODBC connections. But the environment is all 64 bit, including the OS, MB v7, MQ v7, etc

Which ODBC driver should I select when creating the DSN on the broker box ?

"Websphere Message Broker DataDirect Technologies 6.0 64-bit Oracle Wire Protocol" is the only oracle driver available in the options. There is NO 32-bit driver available as opposed to what the documentation says.

Please help.

Thanks
ydsk

Last edited by ydsk on Tue Mar 01, 2011 8:26 pm; edited 1 time in total

smdavies99

Posted: Wed Dec 01, 2010 11:34 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Have you tried the DataDirect 64bit Driver and configured a flow to do something non destructive like a read of 'dual'?

It could be as something as simple as the docs are wrong?
64Bit Windoes EG's are pretty recent.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

ydsk

Posted: Wed Dec 01, 2010 12:50 pm Post subject:

Chevalier

Joined: 23 May 2005
Posts: 410

Thank you smdavies. I checked that the msgflow we tested worked fine using the ODBC connection.

I am really curious to know if the broker version 7 we have is 64 bit or 32 bit.

A consultant we hired had said our broker v7 is 32 bit only, but I feel it is 64 bit but not sure of it. Two questions:

1) How / where can we check that the broker version 7 (on MQ version 7) we have on Windows 2008 R2 server is 64 or 32 bit ? I know the OS is 64-bit, but not sure if the broker is.

2) And how about the ODBC connection ? How do we know whether it is 32- or 64-bit ? Based on the name of the Oracle driver(that's the only driver available in the list), can we say for sure the ODBC connection is 64-bit ?

Thanks
ydsk.

smdavies99

Posted: Wed Dec 01, 2010 10:58 pm Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

ydsk wrote:

A consultant we hired had said our broker v7 is 32 bit only, but I feel it is 64 bit but not sure of it. Two questions:

your consultant is a bit behind the times then. I'd not hire him again.

There is a way to find out if the EG is 64 or 32 bit. There was a post here some time ago but I can't find it at the moment.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

ydsk

Posted: Thu Dec 02, 2010 8:03 am Post subject:

Chevalier

Joined: 23 May 2005
Posts: 410

I know all our EGs are 64 bit, by default. Here is the command to see that:

mqsibrowse <broker_name> -t BROKERAAEG

But, is it possible that the EGs are 64 bit, but the rest of the internal broker components are 32 bit ?

Thanks
ydsk.

smdavies99

Posted: Thu Dec 02, 2010 10:41 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

ydsk wrote:

But, is it possible that the EGs are 64 bit, but the rest of the internal broker components are 32 bit ?

Does it matter? Especially in V7 with the removal of the need for DB2/Oracle etc to act as a Broker DB.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

ydsk

Posted: Thu Dec 02, 2010 11:24 am Post subject:

Chevalier

Joined: 23 May 2005
Posts: 410

We need to kick start some processes from within the broker or otherwise.

We want to know if they should be running within the broker or run outside, after they are started (based on whether the broker is 32 or 64 bit).

Those processes deal with huge files, of the order of more than a 100 MB.
Broker being 32 or 64 bit makes a huge difference because of the amount of memory it can access on the host machine in our case.

That's the point of this whole thread.

I hope IBM updates the WMB v7 Info Center with Windows 64 bit stuff. Everything now says windows is all 32 bit.

thanks
ydsk.

Last edited by ydsk on Thu Dec 02, 2010 11:34 am; edited 1 time in total

Vitor

Posted: Thu Dec 02, 2010 11:29 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

ydsk wrote:

I hope IBM updates the WMB v7 Info Center with Windows 64 bit stuff. Everything now says windows is all 32 bit.

Hope is useful. The Feedback link on the bottom of the relevent InfoCenter page(s) is potentially more useful...

(It's the squeaking wheel that gets greased)
_________________
Honesty is the best policy.
Insanity is the best defence.

mqjeff

Posted: Thu Dec 02, 2010 11:34 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

ydsk wrote:

I hope IBM updates the WMB v7 Info Center with Windows 64 bit stuff. Everything now says windows is all 32 bit.

Uhm.

No.

ydsk

Posted: Tue Mar 01, 2011 8:23 pm Post subject:

Chevalier

Joined: 23 May 2005
Posts: 410

I had given my feedback earlier via the Infocenter as Vitor suggested, and somebody from IBM contacted me then via e-mail. I replied explaining to them what the issue was, and forgot the matter then.

But I just saw that the infocenter is now updated with Windows 64-bit ODBC driver configuration.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ah14442_.htm

The section for Oracle says we need to specify workarounds = 536870912 in the registry.

I never understood what this parameter does exactly. Can someone please explain what it is for ?

We didn't set this parameter so far ( because the documentation wasn't available when we started working ) and still things worked fine so far. We finished UAT and are going live today.

Since we didn't test the parameter till now, we are reluctant to "try" it in production directly.

Appreciate any thoughts on the parameter.

Thanks.

ydsk

Posted: Wed Mar 02, 2011 11:28 am Post subject:

Chevalier

Joined: 23 May 2005
Posts: 410

Hursley guys on the forum, can you please explain what the parameter WorkArounds does ? What if we don't set it ?

Thanks

smdavies99

Posted: Wed Mar 02, 2011 12:35 pm Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

4mins with your friend google gives:-

http://media.datadirect.com/download/docs/odbc/readme/95ntread.htm

This is from the horses mouth as datadirect supply the drivers.
This workaround does not only apply for broker. Powerbuilder and even some JDBC connections can take advantage of it.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

ydsk

Posted: Thu Mar 03, 2011 8:57 pm Post subject:

Chevalier

Joined: 23 May 2005
Posts: 410

Thank you smdavies.

I saw the Datadirect reference manual at http://media.datadirect.com/download/docs/odbc/allodbc/wwhelp/wwhimpl/js/html/wwhelp.htm#href=reference/workarounds.html

and found the setting/value that I was looking for:

WorkArounds=536870912. Enabling this option allows re-binding of parameters after calling SQLExecute for prepared statements.

It's too late as we have already gone to production and I don't know how to take this parameter setting to production.

I think we need to delete/redefine the DSNs, and use mqsisetdbparms, and then restart broker. Not sure how I 'd convince the powers that be of this change.

I wish IBM had published this info in time. What a mess !

And instead of leaving it to the reader to figure out the right Datadirect manuals (version) via google, it'd be a lot better if the infocenter has a link or two to the relevant Datadirect documentation. I guess I need to give them some feedback through the "same" infocenter again.

Thanks.

gbbailey

Posted: Tue Mar 29, 2011 4:46 am Post subject:

Apprentice

Joined: 12 May 2006
Posts: 27
Location: London, UK

I am experiencing a similar problem to @ydsk on a new customer site.

The customer has just installed 64-bit WMB v7.0.0.2 on a Windows Server 2008 R2 box. They want to connect to an Oracle instance (I'm not yet sure what version). I believe this is the same set up as @ydsk.

From my reading of the supported databases page this combination is not supported. Is this true?

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ah10030_.htm

I've tried following the instructions to set up the ODBC. Despite the page Enabling ODBC connections to the databases claiming that "Windows provides only 32-bit support" the page it links to provides guidance for 32-bit and 64-bit data flow engines.

http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ah14442_.htm

My understanding is that you can only create 64-bit DFEs with a 64-bit broker. However when I access the 64-bit ODBC there are no options for Oracle Drivers. When I access the 32-bit ODBC there is an option for "WebSphere Message Broker DataDirect Technologies 6.00 64-BIT Oracle Wire Protocol".

However, the instructions for Oracle refer to "WebSphere Message Broker DataDirect Technologies 6.00 32-BIT Oracle Wire Protocol".

So in summary - can I even connect to this database? If so:
* Why can I only see a 64-bit driver under the 32-bit ODBC link?
* Why can't I see any Oracle drivers under the 64-bit ODBC?

Is there anything I can do here? Reinstalling the 32-bit version of broker is an option at this stage.

lancelotlinc

Posted: Tue Mar 29, 2011 4:58 am Post subject:

Jedi Knight

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

gbbailey wrote:

When looking at performance, you may like to advise your client about 64-bit Linux. You get 20 percent more throughput on 64-bit Linux than 64-bit Windows.

You'll have some ODBC setup challenges in both Windows and Linux. But you get more bang-for-your-buck on Linux.

If you are going to reinstall anyway, why not go for the better performing environment?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

Display posts from previous:

Goto page 1, 2 Next

Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Oracle 11g client on Win 2008 server MB v7

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