| Author |
Message
|
| Deeko |
 Posted: Fri Oct 28, 2005 2:59 am Post subject: WMB6 - mqsicreatebroker hangs |
 |
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
Hi,
I've been installing WMB6 on Linux (SUSE) and I'm running into a problem creating the broker. The create command runs and hangs after the setmqaut messages. I left it for ages but nothing happened. I started another shell and did an mqsilist and it showed the broker so I thought I'd have a go at starting it.
It seemed to start OK but it had a bit of a problem....there was no open queue handle on SYSTEM.BROKER.ADMIN.QUEUE so it was completely useless! My config manager messages just ended up on the queue unread. Strangely enough nothing is being written to syslog.user other than successful start messages.
After that I tried to delete the broker and that command hung too! After much fiddling I moved the broker directory under /var/mqsi/registry and then tried to create a new broker - guess what - that's currently hanging too!!
Anyone had anything similar - I'm just about to delete everything manually (including my broker DB) and try again but I fear this may just happen again!!
Regards,
Derek. |
|
| Back to top |
|
 |
| wschutz |
| Posted: Fri Oct 28, 2005 3:11 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Does it look like the broker's database tables got created?
_________________
-wayne |
|
| Back to top |
|
|
| Deeko |
| Posted: Fri Oct 28, 2005 3:15 am Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
Hi Wayne,
No - nothing's in the broker db at all - I've tried to run an odbc trace but not got it writing anything out as of yet. It seems to be creating the queues and the registry directory and then stopping.
I suspect this may be an ODBC issue of some sort - funny how it's not giving me any errors though - it usually flags up the ODBC errors in the shell.
Regards,
Derek. |
|
| Back to top |
|
|
| Deeko |
| Posted: Fri Oct 28, 2005 5:45 am Post subject: |
|
|
Acolyte
Joined: 16 May 2001
Posts: 72
Location: Edinburgh, UK
|
Sorted it! I was picking up an old profile file! 
Incidentally the trace didn't say anything at all - it just froze on the SQLConnect.
Cheers,
Derek. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sat Oct 29, 2005 12:49 am Post subject: I experienced this as well |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I had this happen to me on Linux (Fedora Core 3).
I was (like yourself) unable to ascertain exactly why this happened but I did get round it eventually.
Originally, I was running WBIMB V5 on this system so I decided to scrub the whole lot and install V6. I deleted DB2 and WBIMB and WMQ and rebooted.
I installed WMQ V6 ok and like your experience it worked fine.
Then I installed DB2 V8.2 from the V6 kit and it seemed to go through ok.
I created the database for the broker usingthe same script that worked for V5. Again all seemed to be ok.
I then installed Broker V6(not toolkit) and it completed ok.
So, I tried to create the broker using a script that worked for V5 and like you it hung after doing the setmqaut commands.
I looked at the broker database after killing the create broker and all the tables seemed to be there but the broker would not start.
So, I deleted the database Broker 6 and DB2. This time I deleted the accounts (db2inst1 etc). I also made sure that everything in /opt/mqsi... & /var/mqsi.. (the directory trees for V5 & V6) were also deleted.
I installed DB2 V8.1 which I knew worked with V5.
Then I installed Broker 6 again. I created the DB2 Database again.
Lo & Behold, the crrate broker worked faultlessly.
I now have a working Broker on Fedora Core 3.
I decided on another test.
I installed RHEL4 on another system and patched it.
This time, I installed everyting from the Broker 6 CD's apart from the RAC which won't install(CPU goes to 100% and stays there when it is starting the JVM).
The broker was created ok and works fine.
I think it must have been something lying around from the old installation.
Remember that DB2 is the only database supported for the Broker stuff on Linux. There is a table somewhere in the docs that lays out what Databases are available for the broker on all the platforms it run on.
For , it would have been nice to be able to use Oracle. I can't seem to remove the aliases on DB2 after dropping the database but that is a small nitpick.
I hope this explanation helps.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| damianharvey |
| Posted: Mon Oct 31, 2005 6:06 pm Post subject: Re: I experienced this as well |
|
|
Acolyte
Joined: 05 Aug 2003
Posts: 59
Location: Sydney, Australia
|
| smdavies99 wrote: |
Remember that DB2 is the only database supported for the Broker stuff on Linux. |
Oracle is supported. We are running WMB v5.0 CSD6 here on RedHat ES 3.0 Update 2 with Oracle 9.2.0.6. You need to get the LCR016 patch from IBM.
[edit] oops. Just noticed that you are on WMB6. I retract everything I just said....unless you are interested in WMB5.... |
|
| Back to top |
|
|
|
|
