MQSeries.net :: View topic - Issues in MQ Workflow after MQ upgrade from V5.3 to V6.0

shruthi · Posted: Tue Aug 05, 2008 2:33 am Post subject:

Hi Gurus,
We are having MQ Work flow errors after upgrading MQ to V6.0 from 5.3
Could not start MQ workflow server
our MQ version is 6.0.2.3
WorkFlow is 3.6 Fixpack 4 which uses a 32 bit db2 instance
db2level is DB2 v8.1.1.144

qm.ini for queue Manger is
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#* *#
#* *#
Log:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogPath=/var/mqm/log/FMCQM/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=10
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/mqm/lib/amqzfu
ComponentDataSize=0
XAResourceManager:
Name=db2inst1 FMCDB
# SwitchFile=/usr/lpp/fmc/db2swit/db2swit
SwitchFile=db2swit
XAOpenString=DB=FMCDB, toc=t, UID=fmccfg, PWD=H3@rt
ThreadOfControl=THREAD

---------------------------------------------------------------------------
Errors from Qmanager log is
08/04/08 13:20:41 - Process(319702.1) User(mqm) Program(amqzxma0_nd)
AMQ7624: An exception occurred during an xa_open call to XA resource manager
'db2inst1 FMCDB'.

EXPLANATION:
An exception has been detected during a call to an XA resource manager. The
queue manager will continue after assuming a return code of XAER_RMERR from the
call.
ACTION:
An FFST should have been produced which documents the exception. Use this and
any further FFSTs to try and determine the reason for the failure. A trace of
the problem will be useful to identify the XA flows between the queue manager
and the resource manager concerned. MQ has allocated an RMId of 1 to this
resource manager. Use this to isolate the flows concerned. First contact the
supplier of the resource manager for problem resolution. If however you think
that the problem lies within the queue manager then contact your IBM support
center. Do not discard any information describing the problem until after it
has been resolved.
----- amqtm64a.c : 238 --------------------------------------------------------
08/04/08 13:20:41 - Process(319702.1) User(mqm) Program(amqzxma0_nd)
AMQ7627: The XA resource manager 'db2inst1 FMCDB' was not available when called
for xa_open. The queue manager is continuing without this resource manager.

EXPLANATION:
The XA resource manager 'db2inst1 FMCDB' has indicated that it is not
available, by returning XAER_RMERR on an xa_open request. Normally this
indicates that the resource manager has been shut down. In this case the
resource manager cannot participate in any new transactions. Any in-flight
transactions in which it was involved will be backed out, and any transactions
in which it is in-doubt will only be resolved when contact with the resource
manager is re-established. A further message will be issued when the queue
manager has been able to do this. If the resource manager should be available,
then there may be a configuration problem or another possibility is that you
are using a 32-bit instance of DB2, this is not supported on this platform, as
WebSphere MQ processes are 64-bit and DB2 does not support 64-bit processes
with its 32-bit instances.
ACTION:
Try to establish the reason why the resource manager is unavailable. It may be
that an invalid XAOpenString has been defined for the resource manager in the
'qm.ini' configuration file. If this is the case, stop and then restart the
queue manager so that any change will be picked up. Alternatively, the queue
manager may be reaching a resource constraint with this resource manager. For
example, the resource manager may not be able to accommodate all of the queue
manager processes being connected at one time, you may need to alter one of its
tuning parameters.
----- amqtmrma.c : 911 -------------------------
---------------------------------------------------------------------------------
Error when ran fmcamain

FMC31020E The server could not be started.
FmcSQLException, Sqlcode=-998, Sqlerrmc=9, Sqlerrp=SQLEADDN, Sqlerrd[0]=0, Sqlerrd[1]=9, Sqlerrd[2]=0, Sqlerrd[3]=0, Sqlerrd[4]=0, Sqlerrd[5]=0, Sqlwarn= , Sqlstate=58005
, Origin=File=/projects/fmc/drv2/lbld/v360/aix/objopt/db2cs/fmcdbac1/fmcdbsvs.cxx, Line=3649, Function=FmcDatabase::Server::selServerSetting(const long *, const FmcString &, const FmcString &, const FmcString &, FMC_SERVER &, FMC_SYSTEM &, FMC_SYSTEM_GROUP &, FMC_DOMAIN &) constFMC31020E The server could not be started.

FMC31000E A database error occurred. SQL code: -998.
FmcExtException, MsgID=31000, MsgParam=-998, , , , , , , , Origin=File=/projects/fmc/drv2/lbld/v360/aix/src/fmcssrva.cxx, Line=868, Function=FmcServerAdapter::Init(FmcSFServerCtrl &)