| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FMC31020E Error |
« View previous topic :: View next topic » |
| Author |
Message
|
| pingwf |
 Posted: Wed Feb 05, 2003 7:41 am Post subject: FMC31020E Error |
 |
|
Novice
Joined: 09 Dec 2002
Posts: 23
|
Hi All,
I am not able to start the WF Server on AIX ( when i am giving command fmcamain). When I run fmczchk to check the configuration it does not says any proplem.
The following is the fmcsys.log msg:
02/05/03 19:54:59 FMC31020E The server could not be started.
02/05/03 19:54:59 FmcSQLException, Sqlcode=-998, Sqlerrmc=9, Sqlerrp=SQL07021, Sqlerrd[0]=0, Sqlerrd[1]=9, Sqlerrd[2]=0, Sqler
rd[3]=0, Sqlerrd[4]=0, Sqlerrd[5]=0, Sqlwarn= , Sqlstate=58005
02/05/03 19:54:59 FMC31000E A database error occurred. SQL code: -998.
02/05/03 19:54:59 FMC31000E A database error occurred. SQL code: -998.
I ran trace and tried to track the error following is part of output of trace log where the RT DB connection fails:
2003-02-05, 19:29:49.069, fmccdmrg.cxx( 232) (01,Fl,FM), fmcamain(76894- 1), FmcDeviceMgrRegistry::Enable(), <exit
2003-02-05, 19:29:49.188, fmcdbsvs.cxx( 3619) (01,Er,DB), fmcamain(76894- 1), FmcDatabase::Server::selServerSetting(), THROW_SQL, FmcSQLException, Sqlcode=-998, Sqlerrmc=9, Sqlerrp=SQL07021, 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/drvs/lbld/v330/objopt/db2cs/fmcdbac1/fmcdbsvs.cxx, Line=3619, Function=FmcDatabase::Server::selServerSetting(const long*,const FmcString&,const FmcString&,const FmcString&,FMC_SERVER&,FMC_SYSTEM&,FMC_SYSTEM_GROUP&,FMC_DOMAIN&) const
I have checked all the log files of DB2 there is not error msg from DB2 side. I am able to connect to FMCDB database by db2 client.
Can any body tell me whats wrong ...
Thanks in advance.
DKP |
|
| Back to top |
|
 |
| yaakovd |
| Posted: Wed Feb 05, 2003 8:47 am Post subject: |
|
|
Partisan
Joined: 20 Jan 2003
Posts: 319
Location: Israel
|
FMC31000E with SQLCode -998 (SQL0998N) indicates a database error occurred during XA transaction processing. Here are a list of probable causes for this error.
(UNIX only) Userid environment problems with ID used to start the queue manager. This is accompanied by message AMQ7604 in the AMQERR01.LOG file for the queue manager (/var/mqm/qmgrs/FMCQM/errors).
Always start the queue manager with the same ID, e.g. fmc. Enter "ps -flu fmc | grep amq" and verify the amq* processes are displayed. If not, the queue manager was started with a different ID.
(DB2 only) Prior to starting the queue manager, DB2INSTANCE must be set by running db2profile. This is best accomplished by adding the line . /home/db2inst1/sqllib/db2profile to the fmc's .profile.
(DB2 only) Test existence of db2instance by entering "echo $DB2INSTANCE". This should return the instance name.
Login as fmc rather than "su" for two reasons. One is to validate the password and the second is to run the .profile. Running "su fmc" as root bypasses both and another reason for sql0998n is an expired password.
Userid must be in the mqm and the (db2 only) db2iadm1 groups.
(DB2 only) TP_MON_NAME not set in database configuration.
On unix enter "db2 get dbm cfg | grep TP_MON_NAME."
On Windows enter "db2 get dmb cfg | more."
Verify the entry TP_MON_NAME exists and is set to mqmax.
If not, enter "db2 upd dmb cfg using TP_MON_NAME mqmax" to set it and then stop and start DB2.
XAResource Manager stanza not set or invalid in qm.ini. It should look similar to:
XAResourceManager:
Name=db2inst1 FMCDB
SwitchFile=/usr/lpp/fmc/db2swit/db2swit
XAOpenString=FMCDB, fmc, fmc
Verify the parameters are set properly for your system.
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Feb 05, 2003 9:02 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
There are a lot of threads in this forum for SQL Code =998. Do a search, and you will find out almost all the probable reasons. 
-Laze |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Feb 05, 2003 9:16 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I think the problem is because of this:
Prior to starting the queue manager, DB2INSTANCE must be set by running db2profile. This is best accomplished by adding the line . /home/db2inst1/sqllib/db2profile to the fmc's .profile.
I think a better idea is to search for Sqlstate + 58005 instead of -998. (I am not a DB2 person but I get lesser hits this way)
-------
Venny |
|
| Back to top |
|
|
| ramires |
| Posted: Wed Feb 05, 2003 4:27 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
you can also look to the MQ (amqerrxx.log) files, some errors are there
Joao |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
