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 » General Discussion » Problem with Using SQL Server as Broker Database

Post new topic  Reply to topic
 Problem with Using SQL Server as Broker Database « View previous topic :: View next topic » 
Author Message
bhupa_sri
PostPosted: Wed Jul 27, 2005 10:19 am    Post subject: Problem with Using SQL Server as Broker Database Reply with quote

Apprentice

Joined: 30 Dec 2004
Posts: 30
Location: India

hi,
I need to use SQL Server as a Message Broker Database. so,w't is the procedure to configure SQl Server to Broker.

We have done in this way.

1. Create Datasource name.
2. configure the broker to SqlServer using mqsisetdbparms command

But the problem is we are getting errors in accessing the database
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jul 27, 2005 10:25 am    Post subject: Re: Problem with Using SQL Server as Broker Database Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

bhupa_sri wrote:
hi,
I need to use SQL Server as a Message Broker Database. so,w't is the procedure to configure SQl Server to Broker.

You create the database, authorize the broker database user to that database and specify the database when you run mqsicreatebroker.

bhupa_sri wrote:
We have done in this way.

1. Create Datasource name.

Pointing at what?

bhupa_sri wrote:
2. configure the broker to SqlServer using mqsisetdbparms command

Why? Clearly,
WBIMB Info Center wrote:
Note: The mqsisetdbparms command does not apply to the configuration repository or broker databases.

So mqsisetdbparms isn't going to help.

bhupa_sri wrote:
But the problem is we are getting errors in accessing the database


And those error messages don't tell you what the problem is? Are you sure?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
bhupa_sri
PostPosted: Wed Jul 27, 2005 10:44 am    Post subject: Reply with quote

Apprentice

Joined: 30 Dec 2004
Posts: 30
Location: India

Hi jeff,

The Broker is Configured to DB2 database while installtion. but our Requirement is we need to access tables in SQL Server so, w't is the procedure you suggest for this..
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jul 27, 2005 10:51 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

bhupa_sri wrote:
Hi jeff,

The Broker is Configured to DB2 database while installtion. but our Requirement is we need to access tables in SQL Server so, w't is the procedure you suggest for this..


AH.

Okay.

So, then,
Create the database.

Authorize a user to that database.

Create an ODBC connection at the system level.

Use mqsisetdbparms to authorize the broker to that ODBC using the user you want.

Enter the ODBC name in your message flow nodes.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
JT
PostPosted: Wed Jul 27, 2005 10:51 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Quote:
But the problem is we are getting errors in accessing the database

Post the error messages.

Did you......
Quote:
Microsoft SQL Server
When you define a data source for Microsoft SQL Server you must choose the driver named SQL Server. The driver level must be Version 3.60 or later. Specify a name and description, and select the correct server from the drop-down list.
Back to top
View user's profile Send private message
bhupa_sri
PostPosted: Wed Jul 27, 2005 11:01 am    Post subject: Reply with quote

Apprentice

Joined: 30 Dec 2004
Posts: 30
Location: India

Hi Jeff&JT,

we are done same but error is Error:: UnSupportedSQL Type

The driver level is 3.85 and SQL Server 2000 SP3
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Jul 27, 2005 11:06 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

There's got to be more information in the error message.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
bhupa_sri
PostPosted: Wed Jul 27, 2005 11:31 am    Post subject: Reply with quote

Apprentice

Joined: 30 Dec 2004
Posts: 30
Location: India

Jeff

I have only that error message and PROCEDURE_CAT.
When the i/p message reach compute node, throws this DatabaseException with out entering the ESQL Logic in compute node.

Thanks for quick reply
Back to top
View user's profile Send private message
JT
PostPosted: Wed Jul 27, 2005 3:48 pm    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Quote:
.....throws this DatabaseException

Then post the entire ExceptionList tree.
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 » General Discussion » Problem with Using SQL Server as Broker Database
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.