MQSeries.net :: View topic

sumit · Posted: Thu Jan 17, 2008 5:01 am Post subject:

HI,

I am working on a Linux x86 platform. I had MQ v 6.0 installed on the server and the queue manager was running fine on it. I did an upgrade to install fix packs - 6.0.2-WS-MQ-LinuxX64-FP0002.tar and MQSeriesRuntime-U810178-6.0.2-2.x86_64.rpm.

Now, this was the last thing I could do, as queue manager is dead now. If I am trying to start it, its throwing error as

$ strmqm <qmgr>
WebSphere MQ queue manager '<qmgr>' starting.
AMQ7254: Incompatible WebSphere MQ queue manager '<qmgr>' has not been
allowed to start.

Did mqrc on this and got :

mqrc AMQ7254

29268 0x00007254 lpiRC_Q_MGR_INCOMPATIBLE
536900180 0x20007254 lrcE_S_Q_MGR_INCOMPATIBLE

MESSAGE:
Incompatible WebSphere MQ queue manager '<insert one>' has not been allowed to
start.

EXPLANATION:
An attempt to start a 1111-bit queue manager was made, this was not allowed as
previously this was a 2222-bit queue manager. Migration between the previous
2222-bit version to current 1111-bit version is not possible and would result
in an unrecoverable corrupted queue manager.

ACTION:
Either delete this queue manager or uninstall the current 1111-bit version and
reinstall the previous 2222-bit version.

As the installation was successful, the queue manager version records have been updated to reflect new configuration.

bash-3.00$ dspmqver
Name: WebSphere MQ
Version: 6.0.2.2
CMVC level: p600-202-070801
BuildType: IKAP - (Production)

There is FDCs. Althoug, when I checked the error logs, I got the following error :

-------------------------------------------------------------------------------
17/01/08 02:02:30 - Process(32472.1) User(mqm) Program(amqzxma0)
AMQ7254: Incompatible WebSphere MQ queue manager '<qmgr>' has not been
allowed to start.

EXPLANATION:
An attempt to start a 64-bit queue manager was made, this was not allowed as
previously this was a 32-bit queue manager. Migration between the previous
32-bit version to current 64-bit version is not possible and would result in an
unrecoverable corrupted queue manager.
ACTION:
Either delete this queue manager or uninstall the current 64-bit version and
reinstall the previous 32-bit version.
----- amqzxma0.c : 1937 -------------------------------------------------------
17/01/08 02:15:42 - Process(6508.1) User(mqm) Program(amqzxma0)
AMQ6254: The system could not dynamically load the shared library
'/opt/mqm/lib/amqzfu', library '/opt/mqm/lib64/amqzfu' has been used instead.

EXPLANATION:
This message applies to UNIX systems. The shared library '/opt/mqm/lib/amqzfu'
failed to load as it is probably a 32-bit library, a 64-bit library is
required. Note that MQ has sucessfully located and loaded a 64-bit library
named '/opt/mqm/lib64/amqzfu'.
ACTION:
Supply the name of a 64-bit library or put the library (alternatively a
symbolic link can be used) in the appropriate place: 32-bit libraries in
/var/mqm/exits; 64-bit libraries in /var/mqm/exits64.
-------------------------------------------------------------------------------
17/01/08 02:15:42 - Process(6514.4) User(mqm) Program(amqzmuc0)
AMQ5037: The Queue Manager task 'LOGGER-IO' has started.

EXPLANATION:
The Utility Task Manager, processId(0) type(6514), has started the LOGGER-IO
task.
ACTION:
None.
-------------------------------------------------------------------------------

I googled to check every possible link, checked the quick beginning and got something like :

All WebSphere MQ commands are 64-bit and have a built in path to the WebSphere MQ 64-bit libraries, however, this can be overridden by the use of LIBPATH and thus can cause WebSphere MQ commands to fail to run. The recommended way of using WebSphere MQ commands and your applications is as follows: v Unset LIBPATH and LD_LIBRARY_PATH and build your applications with a built in path to the appropriate WebSphere MQ libraries, this is detailed in the appropriate WebSphere MQ book for your type of WebSphere MQ application. v If you need to set LIBPATH or LD_LIBRARY_PATH, consider not including /usr/lib in the path you specify in the variable. If you need to include /usr/lib in your LIBPATH or LD_LIBRARY_PATH then in order to avoid errors running 64-bit WebSphere MQ applications or WebSphere MQ commands, consider removing the symbolic links from /usr/lib to the 32-bit WebSphere MQ libraries using the dltmqlnk command. The symbolic links can be restored with the crtmqlnk command. You also need to build your applications with a built in path to the appropriate WebSphere MQ libraries. Note that both the dltmqlnk command and the crtmqlnk command are scripts, and take no parameters. v If you cannot use either of the first two options, run your applications in a different environment to the one which issues any WebSphere MQ commands.

Can you suggest if the last option we have is to delete and then recreate the queue manager or something else can be done?
_________________
Regards
Sumit