| Author |
Message
|
| nilayms |
 Posted: Wed Aug 01, 2007 5:20 am Post subject: querry for WBIMB 6.0 connecting with oracle database. |
 |
|
Apprentice
Joined: 01 Jun 2006
Posts: 31
Location: UK
|
We have got a WBIMB 6.0 and a remote oracle server. We need to insert data into the oracle database. I have done the changes in the odbc.ini file accordingly. Our broker user is "wmbdev" whereas we have a separate id for the database access. I want to know whether wmbdev also needs the database access rights for updating the database tables. If yes which command can be used to grant the id the required database rights on the broker. Should I use the "mqsisetdbparms" command??
_________________
Regards,
Nilay. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Aug 01, 2007 5:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
mqsisetdbparms tells broker what userid and password to use when connecting to a particular datasource.
otherwise broker connects using the broker database user.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nilayms |
| Posted: Thu Aug 02, 2007 7:27 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2006
Posts: 31
Location: UK
|
So does that mean i need to give the broker id the required permissions on the database??
OR
I need to use the mqsisetdbparms command and use the existing database userid??
_________________
Regards,
Nilay. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 02, 2007 7:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, those are your choices.
No, I can't help you decide which one to pick.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| nilayms |
| Posted: Thu Aug 02, 2007 8:26 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2006
Posts: 31
Location: UK
|
Also to clarify - we are using a DB2 databse for the broker databse........we now have to connect it to the oracle databse on a remote system.
_________________
Regards,
Nilay. |
|
| Back to top |
|
|
| nilayms |
| Posted: Fri Aug 03, 2007 12:31 am Post subject: |
|
|
Apprentice
Joined: 01 Jun 2006
Posts: 31
Location: UK
|
Thanks for the help buddy.....cheers!!!
_________________
Regards,
Nilay. |
|
| Back to top |
|
|
| dkeister |
| Posted: Fri Aug 03, 2007 6:20 am Post subject: |
|
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
This might be 'cheating' or opening myself up to a security hole, but I configured my ODBC driver on the advanced tab:
Server List -- USR-D;PWD=mypassword
Default User Name -- WHOEVER
I think this overrides the names passed by the broker. As I recall, I did this with 5 because I don't think mqsisetdbparms was available on 5 (but I might be having a senior moment, or just didn't look hard enough). And we didn't have the ability to add the broker database user added to the Oracle systems.
It works in 6.
_________________
Dean Keister |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Aug 03, 2007 7:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That only works for Windows, and for certain ODBC drivers.
mqsisetdbparms was in v5.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| dkeister |
| Posted: Fri Aug 03, 2007 8:43 am Post subject: |
|
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
Thanks.
_________________
Dean Keister |
|
| Back to top |
|
|
|
|
