| Author |
Message
|
| xiaojiahuochen |
 Posted: Tue Jul 11, 2006 10:29 pm Post subject: fmcamain sometime had down |
 |
|
Newbie
Joined: 11 Jul 2006
Posts: 6
|
HI
can somebody help me
my env is:
aix 5.2 ml03
db2 v8.1
mqwf 3.4 csd6
mq 5.3 csd5
it is a problem that last week we restart the db2 server hardware,
after the machine is restart,MQ WF process fmcamain sometime down but have no reason!
it is log after fmcamain down i collected!
i am read the log,db2diag.log,fmcsys,fmcerr
but have no error,so i think it may be have some problem in runtime db
,perhaps not system prblem,but data is not correct
who can help me |
|
| Back to top |
|
 |
| koko |
| Posted: Wed Jul 12, 2006 5:10 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
Did you check the workflow qmanagers log files? Also another very interesting thing I observed recently is "Cache Problem" on the database side. If the memory on the system where db2 is hosted is filled up, nothing works on workflow side ( and absoulutely no errors get written on workflow side).
Pls check the system resources on your env.
_________________
Thanks
Koko |
|
| Back to top |
|
|
| xiaojiahuochen |
| Posted: Wed Jul 12, 2006 6:45 am Post subject: |
|
|
Newbie
Joined: 11 Jul 2006
Posts: 6
|
thanks reply!
can you tell me more information about runtime db2 system
| Quote: |
| "Cache Problem" on the database side. If the memory on the system where db2 is hosted is filled up, nothing works on workflow side |
how to check it and if it is wrong,how to resolve it
i ask the ibm support,and they reply to me
the version 3.4 maybe has the problem that you said,and advice me
upgrade to 3.5 sp1,maybe resolve it
 |
|
| Back to top |
|
|
| xiaojiahuochen |
| Posted: Wed Jul 12, 2006 6:32 pm Post subject: |
|
|
Newbie
Joined: 11 Jul 2006
Posts: 6
|
today i reboot the db2 machine again,but nothing help me to solve it
mq error log below
06年07月13日 06时31分15秒
AMQ9209: Connection to host 'mqwfsvr2 (10.70.86.26)' closed.
EXPLANATION:
An error occurred receiving data from 'mqwfsvr2 (10.70.86.26)' over TCP/IP.
The connection to the remote host has unexpectedly terminated.
ACTION:
Tell the systems administrator.
----- amqccita.c : 2781 -------------------------------------------------------
06年07月13日 06时31分15秒
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.FMCQM2.TCP' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.FMCQM2.TCP' in the
error files to determine the cause of the failure.
----- amqrccca.c : 784 --------------------------------------------------------
06年07月13日 06时31分24秒
AMQ9002: Channel 'TO.FMCQM2.TCP' is starting.
EXPLANATION:
Channel 'TO.FMCQM2.TCP' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
06年07月13日 06时32分39秒
AMQ9202: Remote host 'mqwfsvr2 (10.70.86.26) (5010)' not available, retry
later.
EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'mqwfsvr2
(10.70.86.26) (5010)' was not successful. However the error may be a
transitory one and it may be possible to successfully allocate a TCP/IP
conversation later.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
78 (X'4E'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'mqwfsvr2 (10.70.86.26) (5010)' was not running. If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.
----- amqccita.c : 973 --------------------------------------------------------
06年07月13日 06时32分39秒
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'TO.FMCQM2.TCP' ended abnormally.
ACTION:
Look at previous error messages for channel program 'TO.FMCQM2.TCP' in the
error files to determine the cause of the failure.
----- amqrccca.c : 784 --------------------------------------------------------
06年07月13日 06时51分24秒
AMQ9002: Channel 'TO.FMCQM2.TCP' is starting.
EXPLANATION:
Channel 'TO.FMCQM2.TCP' is starting.
ACTION:
None. |
|
| Back to top |
|
|
| koko |
| Posted: Thu Jul 13, 2006 3:54 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
You ask the SA or DBA who own the DB server to let you know if everything is fine on their side.
Coming to the issue, are you sure you are following all the procedures to check if workflow is really up
1 If fmcamain is running
2. fmcemains are running
3. you have started trigger monitor before you start workflow
4 are you able to connect to WF thru fmcautil
5. when u try to login do you see any msgs giong to the proper qs on WF qmanager
also can you let us know ur set up a lil bit what is on the box 'mqwfsvr2 (10.70.86.26). I guess your workflow server is on a different box. Is it true?
_________________
Thanks
Koko |
|
| Back to top |
|
|
| xiaojiahuochen |
| Posted: Tue Jul 18, 2006 10:25 pm Post subject: |
|
|
Newbie
Joined: 11 Jul 2006
Posts: 6
|
it is my start mqwf script:
#!/usr/bin/ksh
export LANG=en_US
nohup strmqm FMCQM1
nohup strmqcsv
nohup runmqtrm -m FMCQM1 -q FMCTRIGGER &
nohup fmcamain -y FMC &
it start ok
fmcamain,fmcemain is running
i use fmcautil to login in mqwf,it is ok
dba report the db system is ok
this week it's running ok,but i have do nothing
i don't know what happen!
thanks you help |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Jul 19, 2006 6:21 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| You don't have to nohup the first to entries though. |
|
| Back to top |
|
|
| xiaojiahuochen |
| Posted: Tue Aug 01, 2006 9:01 pm Post subject: |
|
|
Newbie
Joined: 11 Jul 2006
Posts: 6
|
i think i has no effect .
ibm ask me to use nohup in start script
the system has run good,no problem 15 days
i think it has a little problem in system
maybe caused in performs problem
 |
|
| Back to top |
|
|
|
|
