| Author |
Message
|
| don8324 |
 Posted: Fri Aug 16, 2002 5:54 am Post subject: MQOPEN fails with reason code 2009 |
 |
|
Newbie
Joined: 16 Aug 2002
Posts: 4
Location: Pittsburgh, PA
|
Hi. I am an Oracle DBA. and I am faced with the task of connecting an Oracle Database to MQ Series. Because of security concerns we are attempting to configure the "Oracle Procedural Gateway for MQ Series".
After some work I was able to startup the Gateway sucessfully. I connect to MQ Series OK, but the MQOPEN fails with reason code 2009. My MQ Series Administrator does not see any errors in the MQ logs.
I hope that some one here might be able to help as Oracle Support has been less than helpful with MQSeries Gateway Issues.
Thanks,
Ann Renee Tustin
_________________
ARTustin
US Steel
Pittsburgh, PA |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Fri Aug 16, 2002 7:11 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Are you using MQSeries Client or Server code ???
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| don8324 |
| Posted: Fri Aug 16, 2002 7:22 am Post subject: |
|
|
Newbie
Joined: 16 Aug 2002
Posts: 4
Location: Pittsburgh, PA
|
Client code. The version of the Gateway is the newest: 9.0.1. The database version is 8.1.7.2. The Client / Gateway is running on Solaris and the Queue Manager is located on Compaq Tru64.
Thanks,
Ann Renee
_________________
ARTustin
US Steel
Pittsburgh, PA |
|
| Back to top |
|
|
| mrlinux |
| Posted: Fri Aug 16, 2002 7:41 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
My first guess is that the userid running the mqseries piece doesnt have authority.
For a test change the mcauser on the svrconn channel you are using to mqm and retry, this will confirm quickly if this is a issue.
WARNING do not leave the mcauser as mqm, you will need to add the id
that is running the mq app to the box with the QMGR on it and also
use the setmqaut command to allow the user to have access to the correct queues
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| don8324 |
| Posted: Tue Aug 20, 2002 5:48 am Post subject: |
|
|
Newbie
Joined: 16 Aug 2002
Posts: 4
Location: Pittsburgh, PA
|
I think we have ruled out security as an issue. I can open the queue and put messages from a c-program which does not originate from Oracle.
_________________
ARTustin
US Steel
Pittsburgh, PA |
|
| Back to top |
|
|
| muralihegde |
| Posted: Wed Aug 21, 2002 8:15 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Hi,
The reason code 2009 for an MQOPEN calls means connection is broken.
Usually after a successful MQCONN to the Qmgr, you will get a connection handle which you pass during your subsequent MQOPEN call.
But for some reason if the connectivity established by the program to qmgr breaks before the mqopen call, then you will get this above error.
This happens commonly if you use MQ Client connections. If there is a transient tcp/ip connection outage, or if you connect once and then do multiple mqopen in loops there are more chances that your application has lost contact with the qmgr.
-murali |
|
| Back to top |
|
|
| don8324 |
| Posted: Fri Aug 23, 2002 3:27 am Post subject: |
|
|
Newbie
Joined: 16 Aug 2002
Posts: 4
Location: Pittsburgh, PA
|
I found the problem. There were defaults set by the Oracle Gateway in the mqod and mqpmo structures which were incorrect. Once I corrected the defaults to what they were in the c-program that worked, I was able to put messages to the queue 
Thanks for your help
_________________
ARTustin
US Steel
Pittsburgh, PA |
|
| Back to top |
|
|
|
|
