| Author |
Message
|
| angelo |
 Posted: Thu Oct 18, 2001 8:55 pm Post subject: |
 |
|
Newbie
Joined: 17 Oct 2001
Posts: 1
|
I already installed MA88 for Windows but when I set up MQSeries for Windows NT (SP5) Version 5.2 to define the switch library:
Switch File = "C:Program FilesIbmMQSeriesJavalibjdbcjdbcora.dll
I got an error:
AMQ6174: The library C:Program FilesIbmMQSeriesJavalibjdbcjdbcora.dll was not found. The queue manager will continue without this module.
Then I checked this file but it's really apparent. Could anyone please suggest, comment and advise us. Thanks in advance !!! |
|
| Back to top |
|
 |
| WilliamZhang |
| Posted: Thu Nov 29, 2001 1:34 am Post subject: |
|
|
Newbie
Joined: 27 Nov 2001
Posts: 6
Location: BeiJing, China
|
I meet the same problem when I load jdbcdb2.dll with the queue manager. Pls someone can help us.Thanks.
(MQ_JAVA_INSTALL_PATH=D:MQSeriesJava
OS: Windows NT 4.0 + SP6a
MQ: version5.2
DB2:version 7.2 + Fix4)
-------------------------------------------------------------------------------
11/29/01 17:42:39
AMQ6174: The library D:MQSeriesJavalibjdbcjdbcdb2.dll was not found. The
queue manager will continue without this module.
EXPLANATION:
The dynamically loadable file D:MQSeriesJavalibjdbcjdbcdb2.dll was not
found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
-------------------------------------------------------------------------------
11/29/01 17:42:39
AMQ7622: MQSeries could not load the XA switch load file for resource manager
'MQBankDB'.
EXPLANATION:
An error has occurred loading XA switch file
D:MQSeriesJavalibjdbcjdbcdb2.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.
-------------------------------------------------------------------------------
[ This Message was edited by: WilliamZhang on 2001-11-29 02:16 ] |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Nov 29, 2001 2:38 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| Just a guess...Is it possible that the dll that you reference is trying to load another dll that the system can't find via the path statement? |
|
| Back to top |
|
|
| WilliamZhang |
| Posted: Tue Dec 04, 2001 9:06 pm Post subject: |
|
|
Newbie
Joined: 27 Nov 2001
Posts: 6
Location: BeiJing, China
|
Thanks. But I can't know which dll files are needed. I have added
D:MQSeriesJavalibjdbc;D:MQSeriesJavaLib;D:MQSeriesJavabin;d:MQSeriesbin;
d:MQSeriestoolscsamplesbin;D:SQLLIBBIN;D:SQLLIBFUNCTION;
D:SQLLIBSAMPLESREPL;D:SQLLIBHELP;D:WebSphereAppServerjavajrebin;
D:WebSphereAppServerjavajrebinclassic;D:WebSphereAppServerlib into the system PATH. Other path needed?
[ This Message was edited by: WilliamZhang on 2001-12-04 21:07 ]
[ This Message was edited by: WilliamZhang on 2001-12-04 21:10 ] |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Sun Apr 14, 2002 10:57 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
Having had similar problems, I tried my hand again at this today:
1. You need to use JDBCDB2.DLL, not a DB2SWIT.DLL.
2. Using MSVC "depends.exe", JDBCDB2.DLL depends on JVM.DLL,
which can be found in the "jdk1.3.1_01jrebinserver"
directory of the JDK 1.3 (and probably JRE) install.
3. Make sure you have the J2EE.JAR from the J2EE kit in the
classpath.
This get's me as far as being able to issue an MQBegin()/MQCommit without
an abend. Within this I haven't issued a JDBC connection or database calls,
but the whole XA thing seems to be hanging together.
|
|
| Back to top |
|
|
| CodeCraft |
| Posted: Mon Apr 15, 2002 2:20 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
P.S. Obviously, if you're using Oracle, use the JDBCORA.DLL ... It probably still depends on JVM.DLL in the same way.
[ This Message was edited by: CodeCraft on 2002-04-15 03:20 ] |
|
| Back to top |
|
|
| CodeCraft |
| Posted: Mon Apr 15, 2002 8:27 am Post subject: |
|
|
Disciple
Joined: 05 Sep 2001
Posts: 195
|
| P.S. Don't forget to PUT the messages under SyncPoint control. |
|
| Back to top |
|
|
| murali_bestha |
| Posted: Thu Feb 12, 2004 5:41 pm Post subject: |
|
|
Novice
Joined: 12 Feb 2004
Posts: 17
|
Hi,
Please help me. Even after doing all that u described in ur mail, I am unable to start the Queue Manager. It still gives the same error message
| Quote: |
Java version "1.4.2_01"
MQ_JAVA_INSTALL_PATH=C:\IBM\Websphere MQ
OS: Windows 2000 Pro
Websphere MQ: version5.3
Oracle 9i
|
-------------------------------------------------------------------------------
2004/02/13 10:34:10
AMQ6174: The library C:\IBM\WebSphere MQ\bin\jdbcora.DLL was not found. The queue manager will continue without this module.
EXPLANATION:
The dynamically loadable file C:\IBM\WebSphere MQ\bin\jdbcora.DLL was not found.
ACTION:
Check that the file exists and is either fully qualified or is in the
appropriate directory.
-------------------------------------------------------------------------------
11/29/01 17:42:39
AMQ7622: MQSeries could not load the XA switch load file for resource manager 'OracleXADB'.
EXPLANATION:
An error has occurred loading XA switch file C:\IBM\WebSphere MQ\bin\jdbcora.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.
-------------------------------------------------------------------------------
I have put the jdbcora.dll and jvm.dll in the C:\IBM\Websphere MQ\bin and added this into both PATH and CLASSPATH. I put the j2ee.jar in the classpath. But still it fails. Please help me in this regard, as this is little urgent.
Thanks and Regards
Murali
| CodeCraft wrote: |
Having had similar problems, I tried my hand again at this today:
1. You need to use JDBCDB2.DLL, not a DB2SWIT.DLL.
2. Using MSVC "depends.exe", JDBCDB2.DLL depends on JVM.DLL,
which can be found in the "jdk1.3.1_01jrebinserver"
directory of the JDK 1.3 (and probably JRE) install.
3. Make sure you have the J2EE.JAR from the J2EE kit in the
classpath.
This get's me as far as being able to issue an MQBegin()/MQCommit without
an abend. Within this I haven't issued a JDBC connection or database calls,
but the whole XA thing seems to be hanging together.
|
|
|
| Back to top |
|
|
|
|
