| Author |
Message
|
| jfry |
 Posted: Wed Apr 02, 2008 5:42 am Post subject: Reinstalling Message Brokers Toolkit Default Configuration |
 |
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
I cannot use my default configuration in the toolkit so I am trying to reinstall it. I get the following messages when I try to run the wizard:
Verifying that the default queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] does not already exist.
The task succeeded
Verifying that the default broker [WBRK6_DEFAULT_BROKER] does not already exist.
The task succeeded
Verifying that the default broker database [DEFBKDB6] does not already exist.
TASK FAILED
++++++++++
A task has failed, so all the tasks that have already been performed will now be backed out.
++++++++++
++++++++++
All tasks were successfully rolled back.
++++++++++
It appears to me that it thinks the default broker database [DEFBKDB6] exists but it doesn't. When I run the "mqsideletedb DEFBKDB6" command, I get the following message:
BIP9804W: No database of name 'DEFBKDB6' found, no action taken.
The database name specified could not be found. The requested command action was aborted. Please check the database name supplied.
Any help would be appreciated.
Thank You. |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Wed Apr 02, 2008 7:46 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
You don't say if you're using DB2 or Derby (through DB2 Runtime Client Lite). Have you tried using the "-d DeleteAllDatabases" option on mqsideletedb?
Also look in your ODBC settings (in the Windows control panel) and make sure that there is no data source defined of that name.
Cheers
-Matt |
|
| Back to top |
|
|
| jfry |
| Posted: Wed Apr 02, 2008 7:55 am Post subject: |
|
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
Matt,
Thanks for the reply. I have gotten past this error by manually creating the database and then manually removing it. The wizard then thought the DB wasn't there and continued.
I do keep running into other errors along the way. Most of them having to do with my user id/password. The wizard would create the default queue manager but couldn't start it. I have a domain account and there were some services that had my old password. I changed those and now the wizard is failing on the creation of a listener:
Creating a listener for queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] on port 2414.
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the listener.
Collected output from task >
Stdout: [5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Listener creation no longer supported
Active Connections
Proto Local Address Foreign Address State
TCP 37516D:ftp 37516D.aamhc.local:0 LISTENING
TCP 37516D:http 37516D.aamhc.local:0 LISTENING
TCP 37516D:epmap 37516D.aamhc.local:0 LISTENING
TCP 37516D:https 37516D.aamhc.local:0 LISTENING
TCP 37516D:microsoft-ds 37516D.aamhc.local:0 LISTENING
TCP 37516D:1049 37516D.aamhc.local:0 LISTENING
TCP 37516D:1167 37516D.aamhc.local:0 LISTENING
TCP 37516D:1168 37516D.aamhc.local:0 LISTENING
TCP 37516D:1761 37516D.aamhc.local:0 LISTENING
TCP 37516D:2030 37516D.aamhc.local:0 LISTENING
TCP 37516D:2810 37516D.aamhc.local:0 LISTENING
TCP 37516D:2967 37516D.aamhc.local:0 LISTENING
TCP 37516D:3389 37516D.aamhc.local:0 LISTENING
TCP 37516D:8881 37516D.aamhc.local:0 LISTENING
TCP 37516D:9044 37516D.aamhc.local:0 LISTENING
TCP 37516D:9061 37516D.aamhc.local:0 LISTENING
TCP 37516D:9081 37516D.aamhc.local:0 LISTENING
TCP 37516D:9101 37516D.aamhc.local:0 LISTENING
TCP 37516D:9444 37516D.aamhc.local:0 LISTENING
TCP 37516D:59449 37516D.aamhc.local:0 LISTENING
TCP 37516D:60001 37516D.aamhc.local:0 LISTENING
TCP 37516D:61709 37516D.aamhc.local:0 LISTENING
TCP 37516D:1097 localhost:1098 ESTABLISHED
TCP 37516D:1098 localhost:1097 ESTABLISHED
TCP 37516D:1146 37516D.aamhc.local:0 LISTENING
TCP 37516D:1158 localhost:1159 ESTABLISHED
TCP 37516D:1159 localhost:1158 ESTABLISHED
TCP 37516D:1167 localhost:1169 ESTABLISHED
TCP 37516D:1169 localhost:1167 ESTABLISHED
TCP 37516D:1519 localhost:1527 TIME_WAIT
TCP 37516D:1521 localhost:1527 TIME_WAIT
TCP 37516D:1527 37516D.aamhc.local:0 LISTENING
TCP 37516D:1527 localhost:1520 TIME_WAIT
TCP 37516D:1527 localhost:1522 TIME_WAIT
TCP 37516D:1527 localhost:1544 FIN_WAIT_2
TCP 37516D:1527 localhost:1557 FIN_WAIT_2
TCP 37516D:1544 localhost:1527 CLOSE_WAIT
TCP 37516D:1555 localhost:1527 TIME_WAIT
TCP 37516D:1557 localhost:1527 CLOSE_WAIT
]
Stderr: [WebSphere MQ queue manager running.] null
Any ideas? |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Apr 02, 2008 8:52 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| A similar problem was fixed in a recent(ish) fixpack in the toolkit. So first up, use the product updater to ensure that you're on the very latest fixpack. |
|
| Back to top |
|
|
| jfry |
| Posted: Wed Apr 02, 2008 12:28 pm Post subject: |
|
|
Apprentice
Joined: 31 Mar 2008
Posts: 32
|
I found instructions on how to manually create all of the pieces and parts without doing the default configuration wizard.
Thanks. |
|
| Back to top |
|
|
|
|
