|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
XA dll not found but it is not true |
« View previous topic :: View next topic » |
Author |
Message
|
lium |
Posted: Fri Jan 17, 2014 8:47 am Post subject: XA dll not found but it is not true |
|
|
Disciple
Joined: 17 Jul 2002 Posts: 184
|
I am able to configure the xa for oracle successfully with the dll which I created by myself.
However, I also would like to the test the broker shipped dll such as ukora24.dll and ukora26.dll.
I put them both under the
C:\IBM\WebSphere MQ\exits>dir
Volume in drive C has no label.
Volume Serial Number is E0E8-D7AA
Directory of C:\IBM\WebSphere MQ\exits
01/17/2014 03:31 PM <DIR> .
01/17/2014 03:31 PM <DIR> ..
11/14/2013 03:41 AM <DIR> Installation1
01/04/2014 05:19 PM 7,680 oraswit32.dll
01/17/2014 03:31 PM 1,667,072 ukora24.dll
06/20/2013 01:57 AM 1,812,880 ukora26.dll
3 File(s) 3,487,632 bytes
3 Dir(s) 51,470,131,200 bytes free
The oraswit32.dll is working well now.
However, once I changed the qm.ini from oraswit32 to ukora24.dll, I will get such error as following:
1/17/2014 16:16:28 - Process(1996.1) User(michael.liu) Program(amqzxma0.exe)
Host(WIN-JFFTF45GEQM) Installation(Installation1)
VRMF(7.5.0.2) QMgr(BHQM)
AMQ6174: The library 'C:\IBM\WebSphere MQ\exits\ukora26.dll' was not found.
EXPLANATION:
The dynamically loadable library 'C:\IBM\WebSphere MQ\exits\ukora26.dll' was
not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
-------------------------------------------------------------------------------
1/17/2014 16:16:28 - Process(1996.1) User(michael.liu) Program(amqzxma0.exe)
Host(WIN-JFFTF45GEQM) Installation(Installation1)
VRMF(7.5.0.2) QMgr(BHQM)
AMQ7622: WebSphere MQ could not load the XA switch load file for resource
manager 'OracleXA'.
EXPLANATION:
An error has occurred loading XA switch file ukora26. 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.
The error is about:
AMQ6174: The library 'C:\IBM\WebSphere MQ\exits\ukora26.dll' was not found.
However, this is for sure not true.
C:\IBM\WebSphere MQ\exits>dir "C:\IBM\WebSphere MQ\exits\ukora26.dll"
Volume in drive C has no label.
Volume Serial Number is E0E8-D7AA
Directory of C:\IBM\WebSphere MQ\exits
06/20/2013 01:57 AM 1,812,880 ukora26.dll
1 File(s) 1,812,880 bytes
0 Dir(s) 51,470,131,200 bytes free
Could anybody tell me why?
I am also wondering if this is because even though the file is there, however, if the dll is not qualified and not loadable, then the MQ will also yield the "not found" error?
Thanks, |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Jan 17, 2014 9:57 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Could it be that the .dll files that the ukora.dll calls are not on your java classpath (or some other) path? _________________ 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. |
|
Back to top |
|
 |
lium |
Posted: Fri Jan 17, 2014 10:04 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002 Posts: 184
|
It is not that case.
Please check what I posted at very beginning, all 3 dll files are under the same directory exits.
If I change the name to be oraswit32, then it works, if you use ukora24 or ukora26, then it will say not found |
|
Back to top |
|
 |
lium |
Posted: Fri Jan 17, 2014 11:30 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002 Posts: 184
|
If I specify the full path, then it works.
I could not figure out why the different files under the same folder, one has to specify the full path, but the other does not have to
Anyway, it works |
|
Back to top |
|
 |
lium |
Posted: Fri Jan 17, 2014 11:38 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002 Posts: 184
|
Sorry, as a correction, it still does not work.
What it worked was the full path for the oraswit32.dll.
Once I specified the ukora24.dll, then it will run into the same problem, complaining it is not found |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Jan 17, 2014 5:58 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
lium wrote: |
Sorry, as a correction, it still does not work.
What it worked was the full path for the oraswit32.dll.
Once I specified the ukora24.dll, then it will run into the same problem, complaining it is not found |
Well AFAIK the oraswit32.dll comes with the odbc (under <mqinstall>\java\lib\odbc). So obviously it is to be used for the XA bindings in the qm stanza...
ukora24.dll is the generic oracle wire driver for creating the connections, using he wire protocol...
Nothing to do with XA...
Have fun  _________________ MQ & Broker admin |
|
Back to top |
|
 |
lium |
Posted: Sun Jan 19, 2014 6:24 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002 Posts: 184
|
Right now, I am able to start teh queue manager, it seems working well:
ORACLE XA: Version 11.2.0.1.0. RM name = 'Oracle_XA'.
141916.3404:4736.4736.257:
xaoopen: xa_info=Oracle_XA+DB=ORCL+SQLNET=ORCL+Acc=P/prodeval/password+SesTm=100+threads=true+DbgFl=0x7+LogDir=C:\\IBM\\WebSphere MQ\\errors,rmid=257,flags=0x0
141916.3404:4736.4736.257:
xaolgn_help: version#: 185597952 banner: Oracle Database 11g Release 11.1.0.0.0 - Production
141916.3404:4736.4736.257:
xaolgn: sqlxrc/sqlxss completed
141916.3404:4736.4736.257:
xaolgn: return XA_OK
141916.3404:4736.4736.257:
xaoopen: xaolgn completed
141916.3404:4736.4736.257:
xaoopen: return 0
141916.3404:4736.4736.257:
xaorecover: rmid=257, flags=0x1000000
141916.3404:4736.4736.257:
xaorecover: xids=0x18f7c8, count=5, rmid=257, flags=0x1000000
141916.3404:4736.4736.257:
xaofetch: fetchcb->xaorfrfs=2
141916.3404:4736.4736.257:
OCIStmtPrepare: Attempting
141916.3404:4736.4736.257:
OCIStmtPrepare: Succeeded
141916.3404:4736.4736.257:
OCIStmtExecute: Attempting
141916.3404:4736.4736.257:
OCIStmtExecute: Succeeded
141916.3404:4736.4736.257:
OCIStmtFetch: Attempting
141916.3404:4736.4736.257:
xaofetch: fetchcb->xaorfrfs=2
141916.3404:4736.4736.257:
OCIStmtPrepare: Attempting
141916.3404:4736.4736.257:
OCIStmtPrepare: Succeeded
141916.3404:4736.4736.257:
OCIStmtExecute: Attempting
141916.3404:4736.4736.257:
OCIStmtExecute: Succeeded
141916.3404:4736.4736.257:
OCIStmtFetch: Attempting
141916.3404:4736.4736.257:
xaoclrfb: cno=0, rmptr=0xd99ee0
141916.3404:4736.4736.257:
xaoclrfb: cno=0, rmptr=0xd99ee0
141916.3404:4736.4736.257:
xaoclrec: return (void)
141916.3404:4736.4736.257:
xaorecover: rtn 0
141916.3404:4736.4736.257:
xaoclose: xa_info=, rmid=257, flags=0x0
141916.3404:4736.4736.257:
OCIServerDetach: Attempting
141916.3404:4736.4736.257:
OCIServerDetach: Succeeded
141916.3404:4736.4736.257:
xaoclose: rtn 0
However, when I started the broker, from teh trace file, it has error as:
2014-01-19 14:20:08.758500 3600 Error BIP2633W: Warning when starting transaction coordinated by WebSphere MQ; MQBEGIN failed: MQCC=1; MQRC=2122; node 'StaffTransactionHandler.STAFFIN'.
The message flow attribute 'coordinatedTransaction' was specified as 'yes'. However, when the broker attempted to start the coordinated transaction in node 'StaffTransactionHandler.STAFFIN', the MQBEGIN function returned a warning as indicated by the WebSphere MQ reason code. The message flow continues, but the transaction may not be being coordinated as expected, and this may cause subsequent errors or unpredictable results.
Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application Programming Reference manual to establish the cause of the error, taking any appropriate action. It may be necessary to restart the message broker after you have performed this recovery action.
2014-01-19 14:20:08.758543 3600 UserTrace BIP11514W: Warning when starting coordinated transaction. Reason code ''2122''.
Warning when starting transaction coordinated by WebSphere MQ The message flow ''StaffTransactionHandler'' continues, but the transaction may not be being coordinated as expected, and this may cause subsequent errors or unpredictable results.
And it keeps generating
-------------------------------------------------------------------------------
1/19/2014 14:23:36 - Process(4892.4) User(Administrator) Program(taFlowEngine.exe)
Host(WIN-JFFTF45GEQM) Installation(Installation1)
VRMF(7.5.0.2) QMgr(BHQM)
AMQ6174: The library 'C:\IBM\WebSphere MQ\exits64\oraswit.dll' was not found.
EXPLANATION:
The dynamically loadable library 'C:\IBM\WebSphere MQ\exits64\oraswit.dll' was
not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|