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 » Unable to start the Admin server - fmcamain

Post new topic  Reply to topic
 Unable to start the Admin server - fmcamain « View previous topic :: View next topic » 
Author Message
ranganathan
PostPosted: Thu Apr 30, 2009 3:08 am    Post subject: Unable to start the Admin server - fmcamain Reply with quote

Centurion

Joined: 03 Jul 2008
Posts: 104

As a part of MQ migration from 5.3 to 7, we have installed the service pack 8 to our workflow 3.6.0 in our AIX box. We have followed the steps from the below link,

http://www-01.ibm.com/support/docview.wss?rs=795&context=SSVLA5&dc=DA400&uid=swg27011598&loc=en_US&cs=UTF-8&lang=en&rss=ct795websphere

After installing MQ 7 we used, fmczqmig to migrate the v 7 queue manager. All were successful without error messages.

We successfully started the QM but when we started the admin server it is failing to start. please find the details below


=======================

$ fmcver
Name: WebSphere MQ Workflow for AIX
Version: 360
ServicePack: 8
Build date: Jan 29 2009, 12:20:08
$ dspmqver
Name: WebSphere MQ
Version: 7.0.0.1
CMVC level: p700-001-090115
BuildType: IKAP - (Production)



=======================
$ strmqm FMCQM

WebSphere MQ queue manager 'FMCQM' starting.
5 log records accessed on queue manager 'FMCQM' during the log replay phase.
Log replay for queue manager 'FMCQM' complete.
Transaction manager state recovered for queue manager 'FMCQM'.
WebSphere MQ queue manager 'FMCQM' started.

$ runmqtrm -q FMCTRIGGER -m FMCQM &
5724-H72 (C) Copyright IBM Corp. 1994, 2008. ALL RIGHTS RESERVED.
04/30/09 16:10:58 : WebSphere MQ trigger monitor started.

__________________________________________________
04/30/09 16:10:58 : Waiting for a trigger message


$ fmcamain
FMC31020E The server could not be started.
FMC31000E A database error occurred. SQL code: -998.
========================

/var/fmc/cfgs/FMC/log/fmcerr.log

WebSphere MQ Workflow 3.6 Error Report

Report creation = 04/30/09 16:11:33
Related message = FMC31020E The server could not be started.


Error location = File=/projects/fmc/drv2/lbld/v360/aix/objopt/db2cs/fmcdbac1/fmcdbsvs.cxx, Line=3651, Function=FmcDatabase::Server::selServerSetting(const long *, const FmcString &, const FmcString &, const FmcString &, FMC_SERVER &, FMC_SYSTEM &, FMC_SYSTEM_GROUP &, FMC_DOMAIN &) const
Error data = 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


WebSphere MQ Workflow 3.6 Error Report

Report creation = 04/30/09 16:11:33
Related message = FMC31000E A database error occurred. SQL code: -998.


Error location = File=/projects/fmc/drv2/lbld/v360/aix/src/fmcssrva.cxx, Line=868, Function=FmcServerAdapter::Init(FmcSFServerCtrl &)
Error data = FmcExtException, MsgID=31000, MsgParam=-998,

==========================
-----------------------------
fmcsys.log

04/30/09 16:11:33 FMC31020E The server could not be started.
04/30/09 16:11:33 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
04/30/09 16:11:33 FMC31000E A database error occurred. SQL code: -998.

===========================

but i was succesfully able to bind the packages to the runtime database (DB2) with out any errors using fmczutil

============

/var/mqm/qmgrs/FMCQM/qm.ini

XAResourceManager:
Name=CUDBCON FMCDB
SwitchFile=db2swit
XAOpenString=DB=FMCDB, toc=t, UID=xyz, PWD=pqr
ThreadOfControl=THREAD

=============
I was able to connect to the database as 'fmc' directly

=============
$ db2 connect to fmcdb user fmc
Enter current password for fmc:

Database Connection Information

Database server = DB2/AIX64 8.2.3
SQL authorization ID = FMC
Local database alias = FMCDB
============

Any help in this regard is much appreciated.

Thanks,
Ranga
Back to top
View user's profile Send private message
Mr Butcher
PostPosted: Thu Apr 30, 2009 4:12 am    Post subject: Reply with quote

Padawan

Joined: 23 May 2005
Posts: 1716

it took me 3 seconds to ask google and to find this:

http://www-01.ibm.com/support/docview.wss?uid=swg21051001

could this be your issue?

if not, there are additional hits in google when searching for "FmcSQLException, Sqlcode=-998"
_________________
Regards, Butcher
Back to top
View user's profile Send private message
ranganathan
PostPosted: Thu Apr 30, 2009 4:30 am    Post subject: Reply with quote

Centurion

Joined: 03 Jul 2008
Posts: 104

Thanks for the reply, Mr. Butcher... but i have already checked this link and confirmed with the DB team that TP_MON_NAME is set to mqmax... and most of the hits are not relevant to my problem.
Back to top
View user's profile Send private message
hos
PostPosted: Sun May 03, 2009 11:24 pm    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi,

this is most probably a 32 Bit / 64 Bit mixup in your LIBPATH for the DB2 switch libraries. Check that your LIBPATH is a clean 32 Bit or 64 Bit environment. See step 6 and step 7 in the referenced documend or chapter 3.6.3 in the MQWF readme file.
Back to top
View user's profile Send private message
ranganathan
PostPosted: Mon May 04, 2009 12:51 am    Post subject: Reply with quote

Centurion

Joined: 03 Jul 2008
Posts: 104

hos wrote:
Hi,

this is most probably a 32 Bit / 64 Bit mixup in your LIBPATH for the DB2 switch libraries. Check that your LIBPATH is a clean 32 Bit or 64 Bit environment. See step 6 and step 7 in the referenced documend or chapter 3.6.3 in the MQWF readme file.


Thanks for the reply hos, as per the doc we have followed the below setup.,

===================
#Saving the LIBPATHs to avoid a mixture of 32 and 64 libraries for the Workflow libs

SAVE_LIBPATH=$LIBPATH
SAVE_LD_LIBRARY_PATH=$LD_LIBRARY_PATH

. /home/~/sqllib/db2profile

#undo the modifications db2 profile did to the LIBPATHs

LIBPATH=$SAVE_LIBPATH
LD_LIBRARY_PATH=$SAVE_LD_LIBRARY_PATH
=====================

When i use fmczutil to bind the packages with the runtime DB, it is successfully executed. I want to know, How fmczutil is connecting to DB when fmcamain is not ?!

Thanks,
Ranga
Back to top
View user's profile Send private message
hos
PostPosted: Tue May 05, 2009 12:46 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Quote:
When i use fmczutil to bind the packages with the runtime DB, it is successfully executed. I want to know, How fmczutil is connecting to DB when fmcamain is not ?!


fmczutil is a pure DB utility while MQ as the resource manager comes into the game when fmcamain is started. MQ needs to handle the two phase commit and therefore needs control over the DB (via the switch file).
I suggest to contact IBM support if you cannot resolve your problems.
Back to top
View user's profile Send private message
ranganathan
PostPosted: Wed May 06, 2009 4:32 am    Post subject: Reply with quote

Centurion

Joined: 03 Jul 2008
Posts: 104

This issue is resolved... there were some incorrect soft links to 32 bit libraries in DB2 client. We removed them and linked it to the correct 64 bit DB2 libraries, verified that the DB2 client is 64 bit, restarted workflow and the admin server started workiing.

I have already raised a PMR for this issue... but got to know from IBM that MQWF 3.6 with MQv7 is not a certified combination and if certification is required we need to raise a request in FTIS database.
Back to top
View user's profile Send private message
studclot
PostPosted: Thu Jan 06, 2011 4:29 am    Post subject: Reply with quote

Newbie

Joined: 06 Jan 2011
Posts: 1

could any one guide me how to resolve the above issue on Windows 2008 OS with 64 bit
Back to top
View user's profile Send private message
hos
PostPosted: Fri Jan 07, 2011 3:12 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470

Hi, did you follow the instructions in the readme:

If you want to use Microsoft Windows 7 Professional or Microsoft Windows Server 2008 you need to retrieve a full install image of IBM WebSphere MQ Workflow 3.6 SP9 and follow the install instructions in Readme.1st.

The full installation image is available via Passport Advantage.
http://www.ibm.com/software/passportadvantage
Back to top
View user's profile Send private message
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 » Unable to start the Admin server - fmcamain
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.