Posted: Mon Jan 24, 2005 8:03 am Post subject: WMQ as XA transaction manager (Oracle DB): Cannot start QM
Newbie
Joined: 20 Jan 2005 Posts: 8
Hi,
I'm trying to configure Oracle as an XA Resource Manager, with WMQ acting as the transaction co-ordinator. I'm using a JDBC switch file (jdbcora9.dll).
I've followed the steps in the WMQ System Administration Guide to configure the WMQ Resources, and a DBA has carried out the relevant Oracle setup. Attempting to start the Queue Manager results in an error (see below).
Versions:
Windows 2000 SP3
WMQ 5.3 CSD07 (local MQServer installation)
Oracle 9i Client (which talks to Oracle Server 9.2.0.4 on a remote server)
JRE 1.4.1_03 (J2SE)
jdbcora9.dll (which I reference using the fully qualified path)
The service was unable to start TEST/Queue Manager. The error message reported was as follows: AMQ7626: XA resource manager initialization failure. Refer to error log for more information.
Error Log:
24/01/2005 15:35:44
AMQ6175: The system could not dynamically load the library C:\Program
Files\IBM\WebSphere MQ\Java\lib\jdbc\jdbcora9.dll. The system return code was
5. The queue manager will continue without this module.
EXPLANATION:
This message applies to Windows NT and Windows 2000 systems only. The
dynamically loadable file C:\Program Files\IBM\WebSphere
MQ\Java\lib\jdbc\jdbcora9.dll failed to load correctly due to an internal
error. The MQ error recording routine has been called.
ACTION:
Check that the file has not been corrupted then use the standard facilities
supplied with your system to record the problem identifier, and to save the
generated output files. Contact your IBM support center. Do not discard these
files until the problem has been resolved.
----- amqxufnn.c : 410 --------------------------------------------------------
24/01/2005 15:35:44
AMQ7622: WebSphere MQ could not load the XA switch load file for resource
manager 'Oracle LZDEV1'.
EXPLANATION:
An error has occurred loading XA switch file C:\Program Files\IBM\WebSphere
MQ\Java\lib\jdbc\jdbcora9.dll. If the error occurred during startup then the
queue manager will terminate. At all other times the queue manager will
continue without this resource manager meaning that it will no longer be able
to participate in global transactions. The queue manager will also retry the
load of the switch file at regular intervals so that the resource manager will
be able to participate again should the load problem be resolved.
ACTION:
Look for a previous message outlining the reason for the load failure. Message
AMQ6175 is issued if the load failed because of a system error. If this is the
case then follow the guidance given in message AMQ6175 to resolve the problem.
In the absence of prior messages or FFST information related to this problem
check that the name of the switch load file is correct and that it is present
in a directory from which it can be dynamically loaded by the queue manager.
The easiest method of doing this is to define the switch load file as a
fully-qualified name. Note that if the queue manager is still running it will
need to be restarted in order that any changes made to its configuration data
can be picked up.
----- amqtrmca.c : 256 --------------------------------------------------------
Eventually got it working - was a problem related to access control. Our local WMQ services run under a domain user account - this user required extra priveleges (beyond the usual domain-wmq ones it seems) for it to work (execute code?).
Temporary workaround was adding domain user to local admins group.
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