| Author |
Message
|
| fr3dl33 |
 Posted: Fri Nov 22, 2002 7:57 am Post subject: Problems with WF Configuration |
 |
|
Newbie
Joined: 14 Nov 2002
Posts: 6
|
I need big time help on this. I don't know why this is happening and this is driving me crazy. Not to mention that this is mission critical. I've done MQ installs before . . . so, I'm confused at this issue.
First, I've installed DB2 v.7.1, MQSeries 5.2, and MQWF 3.2.2.
Everything installs correctly. But, when I go to configure a WF Config, I error out when it tries to create the default ques in the qmgr. As far as I can tell, the RT and BT db's are built. When I go into the MQSeries Explorer, I can see the qmgr (the default one FMCQM), but there are no queues in it.
This is the error code I get FMC33903E.
The WF Config. GUI will let me "rollback" what I just did by deleting the RT and BT db's. But, when I go to try the config again, it won't even create the db's because the RT and DB db's already exist. But, I know they don't exist because it's not there using the DB2 command line utility, or the GUI.
Any ideas anyone? |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Nov 22, 2002 8:20 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| what I just did by deleting the RT and BT db's |
Have you deleted the DB's using the config utility or using DB2 tools?
Has workflow created user-ids and other stuff or did you do it manually. Because when config utility does all these things then it's pretty clean.
---
Venny |
|
| Back to top |
|
|
| fr3dl33 |
| Posted: Fri Nov 22, 2002 8:25 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2002
Posts: 6
|
When I get the error at the end of the WF Config Utility GUI tool, it give me the option of deleting the RT and BT db's. I hit 'ok'.
Workflow created the using id. |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Nov 22, 2002 8:39 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Why don't you try this then:
Start off again:
When it goes to the database page: Say you want to use an existing database. I guess if you click on DB2 it will list all the current databases. If you see the old databases then try using them.
You may also try this to delete the databases
on the windows command prompt:
fmcbdcdb -o=dd -d=<DBNAME>
Am still wondering about the queues not being defined.
Why 3.2.2.. why not 3.3.2
---
Venny |
|
| Back to top |
|
|
| Vladimir |
| Posted: Fri Nov 22, 2002 1:10 pm Post subject: |
|
|
Acolyte
Joined: 14 Nov 2002
Posts: 73
Location: USA, CA, Bay Area
|
I have one more proposal. 
Actually, when you create a database - first it got created on the server and then it got cataloged on your client. May be it was deleted from your DB2 catalog and left undeleted on the server.
In this case - you can go to the server (using Terminal Service Client, for instance), find and drop your RT and BT databases there.
Or you can catalog them on your client and then you have two choices - to drop them (I would prefer this option) or to use existent DB during WF configuration. |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Nov 22, 2002 1:47 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
I have one more proposal.
Actually, when you create a database - first it got created on the server and then it got cataloged on your client. May be it was deleted from your DB2 catalog and left undeleted on the server.
|
Vladimir, I guess you are 'assuming' he is using a 3 tier configuration of mqwf.
| Quote: |
| Actually, when you create a database - first it got created on the server and then it got cataloged on your client. May be it was deleted from your DB2 catalog and left undeleted on the server. |
Not being a DB2 expert I dont know how it works. Are you sure that is the way Db2 client works.
I believe I had a similar problem like this. In my case after failing to create the QM, wf also failed to delete the databases (I can see the messages when I use fmczutil). I am not sure why it failed, but it only happened once. It deleted databases succesfully for other configurations where it failed to create a QM.
-Laze |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Nov 22, 2002 1:53 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
i hope you are not doing it using terminal services client ( if your environment is WinNT/2000), it can cause a problem creating QM.
-Laze |
|
| Back to top |
|
|
| Vladimir |
| Posted: Fri Nov 22, 2002 6:26 pm Post subject: |
|
|
Acolyte
Joined: 14 Nov 2002
Posts: 73
Location: USA, CA, Bay Area
|
lazeknight:
Yes, you are right. I was assuming that it is 3 tier configuration of mqwf. Sorry, for not mentioning that.
About terminal services:
Yes, it is a known defect in MQSeries that you cannot connect to Queue Manager inside terminal services session using local binding.
It means that MQSeries Explorer and WF admin utility will not work properly there. We had a PMR with IBM on this issue (as usual  ) and they said they will fix this only when they bundle MQ and MQWF into WebSphere. |
|
| Back to top |
|
|
|
|
