| Author |
Message
|
| MQWFHelp |
 Posted: Tue Jul 30, 2002 4:25 pm Post subject: SQL CODE 998 while Starting WorkFlow on AIX |
 |
|
Newbie
Joined: 30 Jul 2002
Posts: 3
|
Hi All,
I am getting SQL Code -998 while issuing "fmcamain -y FMC &".
The fmcsys.log contains:
____________________
07/30/02 16:57:59 FMC31020E The server could not be started.
07/30/02 16:57:59 FmcSQLException, Sqlcode=-998, Sqlerrmc=9, Sqlerrp=SQL07010, S
qlerrd[0]=0, Sqlerrd[1]=9, Sqlerrd[2]=0, Sqlerrd[3]=0, Sqlerrd[4]=0, Sqlerrd[5]=
0, Sqlwarn= , Sqlstate=58005
07/30/02 16:57:59 FMC31000E A database error occurred. SQL code: -998.
07/30/02 16:57:59 FMC31000E A database error occurred. SQL code: -998.
The fmcerr.log contains
___________________
Error location = File=/projects/fmc/drvs/lbld/v330/objopt/db2cs/fmcdb
vs.cxx, Line=3619, Function=FmcDatabase::Server::selServerSetting(cons
nst FmcString&,const FmcString&,const FmcString&,FMC_SERVER&,FMC_SYSTE
TEM_GROUP&,FMC_DOMAIN&) const
Error data = FmcSQLException, Sqlcode=-998, Sqlerrmc=9, Sqlerrp=S
qlerrd[0]=0, Sqlerrd[1]=9, Sqlerrd[2]=0, Sqlerrd[3]=0, Sqlerrd[4]=0, S
0, Sqlwarn= , Sqlstate=58005
MQSeries Workflow 3.3 Error Report
Report creation = 07/30/02 16:22:50
Related message = FMC31000E A database error occurred. SQL code: -998.
Any help will highly appriciated.
Thanks and Regards,
Abishek |
|
| Back to top |
|
 |
| Ratan |
| Posted: Wed Jul 31, 2002 8:38 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Hi,
sql code 998 means a transaction processing error.
look into ur database configuration to see if TP_MON_NAME is set. Or else
update ur db configuration using db2 command line processor. connect to your database and then update ur configuration.
db2=>update dbm cfg using TP_MON_NAME = mqmax.
-Laze |
|
| Back to top |
|
|
| MQWFHelp |
| Posted: Wed Jul 31, 2002 9:22 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2002
Posts: 3
|
Thnx for reply.
I checked the the value . It is set to mqmax.
Could u pls guide us further.I would like to know is there any other parameter 2 check.
Just to mention that we are using the same DB2Instance for WebSphere and MQWorkFlow. I hope this is not the reason for trouble ???
Looking for much awaited reply
Abhishek |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Jul 31, 2002 9:46 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
It is some thing to do with Db2 configuration. check to see if u have followed all the procedures exactly as described in the installation guide.
Also check if you have included the db2profile to the user .profile file of the USERID you are logging in with to start workflow.
-Laze |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Jul 31, 2002 10:04 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
sqlerrmc =9 means a problem with registring with the the transaction manager. So probably you need to concentrate there and try to figure out what went wrong.
-Laze
Last edited by Ratan on Tue Dec 17, 2002 4:47 pm; edited 1 time in total |
|
| Back to top |
|
|
| MQWFHelp |
| Posted: Wed Jul 31, 2002 10:15 am Post subject: |
|
|
Newbie
Joined: 30 Jul 2002
Posts: 3
|
In DB2 configuration the entry for TP_MON_NAME=mqmax is found but
in the AIX System we didnt find the any Dll /file named mqmax But in the our Test NT Setup we found the mqmax.dll under MQSeries Directory.
From where can I get this file installed in the AIX SYSTEM.
Looking for reply.
Abhishek |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed Jul 31, 2002 4:48 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Hey, I got this error when I was attempting to start workflow with an UserID that did not have the correct authority. Might want to check to see if your using an userid that has the proper security.
Good Luck
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Aug 07, 2002 4:26 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Ran into the exact same problem today. Checked and found out that DB2 instance did not start up. started DB2 instance and everything was fine.
-Laze |
|
| Back to top |
|
|
| clindsey |
| Posted: Wed Aug 07, 2002 6:17 pm Post subject: SQL CODE 998 while Starting WorkFlow on AIX |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
Here is a list of things I have compiled that can cause the -998:
(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 that
was enabled as transaction coordinator when mqwf was configured.
Enter "ps -flu fmc | grep amq" and verify the amq* processes are displayed.
If not, the queue manager was not started with the fmc 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.
NOTE: Almost all of these changes require a stop/start of the
queue manager. Once the AMQ7604 is logged, the queue
manager will go ahead and start but fmcamain is doomed
when it starts becuase the qmgr started without XA support. |
|
| Back to top |
|
|
|
|
