ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Odd error

Post new topic  Reply to topic
 Odd error « View previous topic :: View next topic » 
Author Message
techRobo
PostPosted: Fri Feb 04, 2011 11:23 am    Post subject: Reply with quote

Newbie

Joined: 03 Feb 2011
Posts: 1

Following is the setup
Operating System Windows 2000 server
DB2 = Version 8 with fix pak 12
IBM MQ Series - Version 5.3.0
IBM Workflow - Version 3.6

When I start IBM MQ series, we get the following warning in event viewer (Not able to find qm.ini)

The XA resource manager 'DB2 FMCDB' was not available when called for xa_open. The queue manager is continuing without this resource manager.

The XA resource manager 'DB2 FMCDB' has indicated that it is not available, by returning XAER_RMERR on an xa_open request or XAER_RMFAIL when called for something else. 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 problem occurred on an xa_open request, and the resource manager should be available, then there may be a configuration problem.

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.
###########################################
Because of this Iam not able to start MQ Workflow service, i get the following error message

FMC31000E A database error occurred. SQL code: -998.
FmcSQLException,Sqlcode=-998, Sqlerrmc=9, Sqler

We also tried to changing the XAResourceManager for FMCQM, the changes are not getting reflected.

Following the fmczccd log
The channel table in the profile is: e:\program files\ibm\websphere mq workflow\chltabs\mqwfchl.tab
The connect name found in the profile : FMC.FMCGRP.FMCSYS,FMCQM
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
You are using the MQSeries Server API for the queue manager communication.

Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Connecting to the queue manager FMCQM was successful.
There are no checks with this utility to verify that the MQSeries Workflow Server is running on your server.

################################################## #############
fmczchk log
FMC34010I: Configuration checker version 3.6.0.118 started.
FMC34119I: No command-line options specified.

FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.6.0 checks.
FMC34101I: The Operating System is Windows 2003 5.2 (Service Pack 1).
FMC34103I: Local time is 2006-07-24 11:27:36.
FMC34104I: Universal time coordinated (UTC) is 2006-07-24 05:57:36.
FMC34301I: WinSock version: WinSock 2.0.
FMC34314I: The local IP address is 172.26.8.189.
FMC34131I: The WebSphere MQ Workflow installation directory is e:\program files\ibm\websphere mq workflow\bin.
FMC34154I: WebSphere MQ Workflow Version 3.6.0.0 is installed.
FMC34143I: The default configuration is 'FMC' (from the general configuration profile).
FMC34121I: The current configuration is 'FMC'.
FMC34145I: The following configurations are available: FMC.
FMC34113I: Language specification is 'ENU' (from the installation profile).
FMC34115I: The message catalog is e:\progra~1\ibm\websph~2\bin\fmckmenu.cat.
FMC34132I: The XPG4 locale is EN_US.IBM-1252.
FMC34133I: The ANSI code page is 1252, the OEM code page is 437.
FMC34134I: The locale file used is e:\progra~1\ibm\websph~2\bin\locale\en_us\ibm-1252.lcl.

FMC34013I: ===> Admin Server found, checks started.
FMC34122I: Environment variable DB2_RR_TO_RS is set to 'YES'.
FMC34500I: ==> Database Manager configuration for DB2.
FMC34508I: Agent stack size is 96.
FMC34508I: Query heap size is 1500.
FMC34501I: ==> Database configuration for FMCDB.
FMC34508I: Log file size is 4095.
FMC34508I: Log primary is 4.
FMC34508I: Log second is 124.
FMC34508I: Database heap is 400.
FMC34508I: Default application heap is 512.
FMC34508I: Number of page cleaners is 2.
FMC34508I: Log buffer size is 16.
FMC34508I: Lock list is 1000.
FMC34502I: ==> Database connection to FMCDB.
FMC34508I: Buffer pool size is 2000.
FMC34515I: Connect to FMCDB was successful (user ID 'EOSCAR').
FMC34510I: The DBMS name is DB2/NT (version 08.02.0005).
FMC34511I: The database driver is db2cli.dll (Version 08.02.0005).
FMC34512I: The database name for alias 'FMCDB' is 'fmcdb'.
FMC34700I: ==> Service Control Manager configuration.
FMC34nnnI: Service DB2NTSECSERVER: Startup automatic, account LocalSystem
FMC34nnnI: Service MQSeriesServices: Startup automatic, account LocalSystem
FMC34535I: Service 'DB2' does not exist, assuming DB2 client installation.
FMC34nnnI: Service MQ Workflow - FMC: Startup automatic, account LocalSystem

FMC34013I: ===> Server message device found, checks started.
FMC34303I: TCP port fmclFMCQM14000 found at number 14000.
FMC34307I: The local listener for port 14000 is not running.
FMC34303I: TCP port fmclFMCQM14001 found at number 14001.
FMC34306I: The local listener for port 14001 is active.
FMC34303I: TCP port fmclFMCQM5010 found at number 5010.
FMC34307I: The local listener for port 5010 is not running.
FMC34404I: The MQSeries Server 5.3.0.0 is installed.
FMC34nnnI: System for FMCQM is FMC.FMCGRP.FMCSYS
FMC34031I: Successfully loaded QM switch file library db2swit.dll.
FMC34nnnI: Settings for FMCQM from Queue manager FMCQM registry
FMC34nnnI: XAResourceManager.XAOpenString = DB=FMCDB, TPM=MQ, toc=t, UID=eOscar, PWD=******
FMC34nnnI: Channels.MaxChannels = <null>
FMC34nnnI: Channels.MaxActiveChannels = <null>
FMC34nnnI: Default queue manager is FMCQM

FMC34013I: ===> Execution Server found, checks started.

FMC34013I: ===> Client message layer (server API) found, checks started.
FMC34nnnI: FMLConnectName is 'FMC.FMCGRP.FMCSYS,FMCQM'
FMC34nnnI: Channel definition file is e:\program files\ibm\websphere mq workflow\chltabs\mqwfchl.tab
FMC34410I: Channel table e:\program files\ibm\websphere mq workflow\chltabs\mqwfchl.tab has 2 entries.
FMC34411I: 0: Active; Queue Manager FMCQM connecting to TDBANKDEV2(14001) through TCP.
FMC34411I: 1: Active; Queue Manager FMCQM connecting to TDBANKDEV2(14001) through TCP.
FMC34nnnI: This client can connect to an OS/390 server

FMC34013I: ===> Client message layer (client API) found, checks started.

FMC34013I: ===> WebSphere MQ Workflow C/C++ API found, checks started.
FMC34nnnI: API will use queue manager 'FMCQM' (queue prefix FMC)
FMC34324I: Ping TDBANKDEV2 successful.
FMC34324I: Ping TDBANKDEV2 successful.

FMC34013I: ===> Java API found, checks started.
FMC34nnnI: CLASSPATH='E:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;E:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;.;E:\PROGRA~1\IBM\SQLLI B\java\db2java.zip;E:\PROGRA~1\IBM\SQLLIB\java\db2 jcc.jar;E:\PROGRA~1\IBM\SQLLIB\java\sqlj.zip;E:\PR OGRA~1\IBM\SQLLIB\bin;E:\PROGRA~1\IBM\SQLLIB\java\ common.jar;E:\PROGRA~1\IBM\SQLLIB\java\db2jcc_lice nse_cisuz.jar;E:\PROGRA~1\IBM\SQLLIB\java\db2jcc_l icense_cu.jar'

FMC34013I: ===> Buildtime found, checks started.
FMC34130I: The default font for the graphical user interface is 'MS Shell Dlg'.
FMC34129I: The screen resolution is set to 1152x864.
FMC34nnnI: B/T help file is e:\program files\ibm\websphere mq workflow\bin\fmcbhenu.hlp
FMC34nnnI: HTML template file is e:\program files\ibm\websphere mq workflow\bin\fmcfdhtm.tem
FMC34031I: Successfully loaded BT resource library fmcbrenu.dll.
FMC34502I: ==> Database connection to FMCBDB1.
FMC34515I: Connect to FMCBDB1 was successful (user ID 'EOSCAR').
FMC34510I: The DBMS name is DB2/NT (version 08.02.0005).
FMC34511I: The database driver is db2cli.dll (Version 08.02.0005).
FMC34512I: The database name for alias 'FMCBDB1' is 'fmcbdb1'.
FMC34nnnI: Unified logon for 'eOscar' not possible
FMC34523I: DB2 Enterprise Server Edition 8.1.12 has fixpack WR21368 installed.
FMC34519I: QueryTimeoutInterval is '<null>' in the Common section of e:\program files\ibm\sqllib\db2cli.ini.
FMC34531I: DB2 authentication is through the server.

FMC34013I: ===> Runtime Client found, checks started.
FMC34110E: Typelib for fmcn6cc.ocx not found at {901B8104-FC29-11D0-A7FE-0020AF00F853}.
FMC34110E: Typelib for fmcn6fc.ocx not found at {901B8141-FC29-11D0-A7FE-0020AF00F853}.
FMC34031I: Successfully loaded Runtime Client resource library fmcn6enu.dll.
FMC34nnnI: Runtime Client help file is e:\program files\ibm\websphere mq workflow\bin\fmcn6enu.hlp

FMC34100I: Messages have been written to e:\fmczchk.log.
FMC34998I: See fmczchk.htm for more information on the messages.
FMC34999I: Configuration checker ended: 2 error(s), 0 warning(s), rc = 0.
##########################################

After registering fmcn6cc.ocx - the above two error were fixed...

But the problem stil persists... Please let us know, if anybody has the solution... Not able to figure out what went wrong.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Feb 04, 2011 11:52 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

techRobo wrote:
When I start IBM MQ series, we get the following warning in event viewer (Not able to find qm.ini)


On Windows, you won't.

techRobo wrote:
The XA resource manager 'DB2 FMCDB' was not available when called for xa_open. The queue manager is continuing without this resource manager.


Seems clear enough.

techRobo wrote:
Please let us know, if anybody has the solution


Fix the XA resource manager
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Feb 04, 2011 8:35 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Quote:
Following is the setup
Operating System Windows 2000 server
DB2 = Version 8 with fix pak 12
IBM MQ Series - Version 5.3.0
IBM Workflow - Version 3.6

Don't know much about workflow but shouldn't you have upgraded somewhere along the way? AFAIK MQ 5.3 has been out of support for at least 2 years and MQ 6 is going out of support end of September...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Sat Feb 05, 2011 6:53 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Workflow is also out of support, or getting there fast...
Back to top
View user's profile Send private message
jmac
PostPosted: Sun Feb 06, 2011 9:15 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Here is a link to the current supported environments.

http://www-01.ibm.com/software/integration/wmqwf/requirements/windows-details.html

What level of MQWF are you running?

Did you search this forum? I seem to recall seeing and solving this issue several times over the years.

With a little more information we can probably get you by this.

In addition to level of MQWF you are running, what did you do just before this issue occurred? Is this a new installation? If so, why use MQ 5.3?
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Odd error
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.