| Author |
Message
|
| mohamed |
 Posted: Sun Feb 12, 2006 9:37 am Post subject: Solved (Problem on AIX 5.3) |
 |
|
Newbie
Joined: 12 Feb 2006
Posts: 6
|
Dear ALL
the following information about the AIX configuration machines
system 1:
AIX version : 5300-03
DB2 Sever version "DB2 v8.1.1.64", "s040812", "U498350", and FixPak "7". 64 bit instance
system 2:
AIX version : 5300-01
DB2 Client version : "DB2 v8.1.1.64", "s040812", "U498350", and FixPak "7" 32 bit instance
WebSphere MQ Version: 6.0.0.0 (Server)
WebSphere MQ Workflow Version 3.6.0 (Server)
the configuration was created successfully ,it created the queue manager and the queue started OK but the MQWF server couldn't start by the "fmcamain" command
and return the following error
FMC31020E The server could not be started.
FMC31000E A database error occurred. SQL code: -998
I tried the fmczchk command and return :
FMC34010I: Configuration checker version 3.6.0.118 started.
FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.6.0 checks.
FMC34207W: Usage: which CommandName... is not an WebSphere MQ Workflow program file. The core file is ignored.
FMC34013I: ===> Admin Server found, checks started.
FMC34500I: ==> Database Manager configuration for db2inst1.
FMC34509E: Query heap size is 0, must be at least 1500.
FMC34501I: ==> Database configuration for FMCDB.
FMC34503E: sqlfxdb: SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING").
FMC34013I: ===> Server message device found, checks started.
FMC34nnnW: No MQSeries TCP port found at default number 5010
FMC34013I: ===> Execution Server found, checks started.
FMC34013I: ===> Client message layer (server API) found, checks started.
FMC34013I: ===> Client message layer (client API) found, checks started.
FMC34013I: ===> WebSphere MQ Workflow C/C++ API found, checks started.
FMC34100I: Messages have been written to /fmczchk.log.
FMC34998I: See fmczchk.htm for more information on the messages.
FMC34999I: Configuration checker ended: 2 error(s), 2 warning(s), rc = 0.
I cataloged the database instance on the client machine and i can connect to the database form the command line or the control center
Last edited by mohamed on Sun Mar 12, 2006 12:51 am; edited 1 time in total |
|
| Back to top |
|
 |
| vennela |
| Posted: Sun Feb 12, 2006 12:52 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Have you checked if DB2 client 32 bit is supported for 64 bit DB2 servers for workflow configuration |
|
| Back to top |
|
|
| supreeth |
| Posted: Sun Feb 12, 2006 9:18 pm Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
The log dump says it all.
| Quote: |
A database error occurred. SQL code: -998
Attempt to establish connection failed with security reason
|
The DB login name or password u hav specified to be used while connecting to the DB is wrong at the time of configuring WF.
try logging in as the user with the password specified there. If the login fails and if u hav root permission, reset the password of the DB user. (Note: Ensure that it doesnt affect other applications using the same user and with a password specified)
1> Check who you have authorized to start the queue manager. Login as the same user. Assuming user fmc is the one u have given authorization, login as user fmc.
stop the WF Server queue manager (FMCQM).
start the qmgr using the command strmqm <qmgr name>
start the command server strmqcsv <qmgr name>
2> Check if the port u hav specified while configuring workflow is running.
3> Start the db2 instance using the command db2start <instance name>
4> start WF server using fmcamain
It shud start without much ado.
Thanks and Regards,
Supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| mohamed |
| Posted: Mon Feb 13, 2006 3:16 am Post subject: |
|
|
Newbie
Joined: 12 Feb 2006
Posts: 6
|
-yes I checked the DB2 client 32 bit is supported for 64 bit DB2 servers for workflow configuration
-I tried the second solution but it failed and return the same erorr
I can connect from the db2 client to the db2 server by the fmc user that used in the configuration
I can connect by the command line and control center |
|
| Back to top |
|
|
| latelatif |
| Posted: Mon Feb 13, 2006 1:47 pm Post subject: |
|
|
Novice
Joined: 08 Feb 2006
Posts: 21
|
Logon as "fmc"
1) fmczutil
2) "s" to select the configuration
3) r ... Runtime Database Commands Menu
4) b ... Bind packages
Post the error you get ( if any )
If no errors, do what supreeth suggested.
1) Start FMCQM, Command Server and Trigger Monitor with userid "fmc"
2) Make sure that the database server is running
3)start workflow server
If you are still getting errors, post the output of
and /var/mqm/qmgrs/FMCQM/qm.ini |
|
| Back to top |
|
|
| mohamed |
| Posted: Wed Feb 15, 2006 11:50 pm Post subject: |
|
|
Newbie
Joined: 12 Feb 2006
Posts: 6
|
hi latelatif
I tried your solution but still give the same error
I can attatch to the instance from the db2 client machine to the db2 server machine which host the database of MQWF
when I run the fmcamain command it return :
FMC31020E The server could not be started.
FMC31000E A database error occurred. SQL code: -998
the output from ps command:
bash-2.04# ps -ef | grep -i FMCQM
root 241844 360648 0 08:05:20 - 0:01 amqzmur0 -m FMCQM
root 250098 360648 0 08:05:21 - 0:11 amqzlaa0 -mFMCQM -fip0
root 262200 401644 0 08:05:21 - 0:01 /usr/mqm/bin/runmqchi -m FMCQM -r
root 286970 1 0 08:05:47 - 0:03 runmqtrm -q FMCTRIGGER -m FMCQM
root 323708 401644 0 08:05:22 - 0:05 /usr/mqm/bin/amqpcsea FMCQM
root 327782 360648 0 08:05:20 - 0:03 /usr/mqm/bin/amqzdmaa -m FMCQM
root 335972 278594 0 01:56:10 pts/2 0:00 grep -i FMCQM
root 360648 1 0 08:05:19 - 0:06 amqzxma0 -m FMCQM
root 364730 360648 0 08:05:20 - 0:01 /usr/mqm/bin/amqzfuma -m FMCQM
root 368692 360648 0 08:05:20 - 0:03 /usr/mqm/bin/amqrrmfa -t2332800 -s2592000 -p2592000 -g5184000 -c3600 -m FMCQM
root 376958 360648 0 08:05:20 - 0:00 amqzmuc0 -m FMCQM
root 401644 360648 0 08:05:20 - 0:00 /usr/mqm/bin/amqzmgr0 -m FMCQM
the content of /var/mqm/qmgrs/FMCQM/qm.ini 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=13
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/usr/mqm/lib64/amqzfu
ComponentDataSize=0
XAResourceManager:
Name=local FMCDB
SwitchFile=db2swit
XAOpenString=DB=FMCDB, toc=t, UID=work, PWD=abc
ThreadOfControl=THREAD |
|
| Back to top |
|
|
| supreeth |
| Posted: Thu Feb 16, 2006 12:45 am Post subject: |
|
|
Voyager
Joined: 17 May 2005
Posts: 90
Location: London
|
Hi,
I dont think you have even bothered to look at the error you are getting in detail. It is clearly telling that
| Quote: |
| FMC34503E: sqlfxdb: SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING"). |
did you try investigating/rectifying the same ???
Thanks and Regards,
Supreeth
_________________
Supreeth Gururaj
IBM Certified WMQ Solution Expert |
|
| Back to top |
|
|
| Q_change |
| Posted: Thu Feb 16, 2006 8:21 am Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 8
|
Assuming you are on a Teir 3 environment, the error message is "normal" (per IBM):
FMC34503E: sqlfxdb: SQL30082N Attempt to establish connection failed with security reason "3" ("PASSWORD MISSING").
I get this error when I run on one of my working WF 3.6 deployments.
I do have a different WF 3.6 deployment that I am encountering the same error as you are.
Funny thing is I can run fmczutil & rebind the databases fine, but get a Database error when I try to start up WF.
Will keep you posted if we figure anything out. |
|
| Back to top |
|
|
| Q_change |
| Posted: Thu Feb 16, 2006 2:15 pm Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 8
|
| We fixed it by changing out the mq profile for the db2 profile on the unix box which we were running. This fixed our issue. |
|
| Back to top |
|
|
| Q_change |
| Posted: Thu Feb 16, 2006 2:19 pm Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 8
|
| Sorry bad text, we pointed the mq id profile to point to the db2 profile for the server we are running on. |
|
| Back to top |
|
|
| hos |
| Posted: Thu Feb 16, 2006 11:51 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
| Quote: |
| XAOpenString=DB=FMCDB, toc=t, UID=work, PWD=abc |
If this is really the XAOpenString of your MQ profile, I would say the problem is obvious, isn't it?
Run fmczutil and set the proper UID and PWD for MQ and DB2. |
|
| Back to top |
|
|
| Q_change |
| Posted: Fri Feb 17, 2006 7:42 am Post subject: |
|
|
Newbie
Joined: 10 Feb 2006
Posts: 8
|
The PASSWORD error is NOT the problem in MY case. Remember a teir 3 archirtecture spit out these "ghost" problems (per IBM). Open a PMR and ask them. They will tell you this is know bug in fmczchk.
Our issue was that we need to reference the db2profile upon starting up our user ids (mq & wf). So we needed to add a script to their profile that sets up the default database environment for these ids. |
|
| Back to top |
|
|
| latelatif |
| Posted: Fri Feb 17, 2006 8:23 am Post subject: |
|
|
Novice
Joined: 08 Feb 2006
Posts: 21
|
| mohamed wrote: |
bash-2.04# ps -ef | grep -i FMCQM
root 241844 360648 0 08:05:20 - 0:01 amqzmur0 -m FMCQM
root 250098 360648 0 08:05:21 - 0:11 amqzlaa0 -mFMCQM -fip0
|
OK it was pointed out that the Queue Manager FMCQM must be started as the Wokflow Admin. You started the queue manager as "root". So logon as the Workflow Admin ID and restart FMCQM.
| Quote: |
the content of /var/mqm/qmgrs/FMCQM/qm.ini is:
XAResourceManager:
Name=local FMCDB
SwitchFile=db2swit
XAOpenString=DB=FMCDB, toc=t, UID=work, PWD=abc
ThreadOfControl=THREAD |
So is your Workflow Admin "work" or "fmc". The UID needs to match that. And the Queue Manager must be started by that same ID. Unless you defined it explicitly during configuration, which i doubt you did seeing as you are getting -998.
What is the output of
| Code: |
cat /etc/group|grep -i fmc
|
That is if you are going with the standard group name for all Workflow Admins. You should get the idea here. |
|
| Back to top |
|
|
| mohamed |
| Posted: Mon Feb 20, 2006 3:48 am Post subject: |
|
|
Newbie
Joined: 12 Feb 2006
Posts: 6
|
I changed the configuration,Now everything installed on the same server(db2 8.2.1 64 bit instance-MQ series 6.0.1.0-MQWF 6.0.1.0)
when I uesd the fmczutil command it failed to create the database and return the following error:
exec(): 0509-036 Cannot load program /usr/lpp/fmc/bin/fmczrdb because of the following errors:
0509-022 Cannot load module /usr/opt/db2_08_01/lib/libdb2.a(shr.o).
0509-150 Dependent module /home/db2inst1/sqllib/lib/libdb2osse.a(shr.o) could not be loaded.
0509-152 Member shr.o is not found in archive
0509-022 Cannot load module fmczrdb.
0509-150 Dependent module /usr/opt/db2_08_01/lib/libdb2.a(shr.o) could not be loaded.
0509-022 Cannot load module . |
|
| Back to top |
|
|
| karthik |
| Posted: Mon Feb 20, 2006 10:49 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi mohamed,
| Quote: |
| Have you checked if DB2 client 32 bit is supported for 64 bit DB2 servers for workflow configuration |
May be 64 Bit DB2 is not yet supported..
can you check with IBM regarding that.
Thanks
karthik |
|
| Back to top |
|
|
|
|
