| Author |
Message
|
| slaupster |
 Posted: Mon Mar 20, 2006 10:09 am Post subject: Creating broker on RHEL 3 hangs |
 |
|
Apprentice
Joined: 17 Nov 2004
Posts: 41
|
When I create a broker (v5) on RHEL 3, the comand hangs:
| Quote: |
[mqm@gbahel116 errors]$ mqsicreatebroker MY_BRK -i *** -a *** -q MY_QM -n WBRKBKDB -u *** -p ***
AMQ8110: WebSphere MQ queue manager already exists.
WebSphere MQ queue manager running.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
|
The ODBC trace shows the SQLConnect happening but nothing after that:
| Quote: |
ppid=24198:pid= 5e87:4000 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 0x0813d810
UWORD 2535
UDWORD 0
ppid=24198:pid= 5e87:4000 ENTER SQLConnect
HDBC 0x0813d810
UCHAR * 0xbfffb6f8 [ -3] "WBRKBKDB"
SWORD -3
UCHAR * 0xbfffb6d8 [ -3] "**"
SWORD -3
UCHAR * 0xbfffb590 [ -3] "******"
SWORD -3
|
I've tried various but no joy. I can connect to the DB and administer with various db2 commands and utilities. I have LD_ASSUME_KERNEL=2.4.19 exported. I can find no reference to any connection attempt in db2 logs, but may not know where to look. Nothing interesting in syslog.
Any suggestions much appreciated! |
|
| Back to top |
|
 |
| thomaszheng |
| Posted: Mon Mar 20, 2006 10:59 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
| it happend to me the same, it is hang on the same place, it is on solaris machine. it hang, the broker is created and can be started, but can not be delete, the delete process also hang. |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Mon Mar 20, 2006 11:01 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
| the same to me, nothing is the syslog |
|
| Back to top |
|
|
| slaupster |
| Posted: Mon Mar 20, 2006 12:46 pm Post subject: |
|
|
Apprentice
Joined: 17 Nov 2004
Posts: 41
|
I finally worked it out - buried deep in a manual is the instruction that you need to source the db2 profile AS WELL AS the broker profile - slightly annoying!! as never seen that any where else, and nothing very helpful error message wise, I was even stracing it!
hope that solves your guys problems as well.
cheers |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Mon Mar 20, 2006 12:57 pm Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
| would you tell me the name of the manual |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Mar 20, 2006 1:03 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Its in the "Installing" manual:
| Quote: |
To work with a broker, you need to set up the required environment for its databases and you are recommended to do this by running the vendor-provided profile for the database manager.
Note that the environment setup depends on the database manager being used. You run the appropriate script, as follows:
* DB2, run db2profile for the relevant DB2 instance.
* Oracle, run oraenv (Note that you must export ORACLE_HOME and ORACLE_SID prior to running oraenv)
* Sybase, run SYBASE.sh
|
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Mar 20, 2006 1:09 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| thomaszheng |
| Posted: Tue Mar 21, 2006 9:52 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
Hi,
I create db2 user with the user id of borker. now the creating of broker is working well.
but have created two broker with a broker user id and a be user id. the process was hang. the tow broker are there, with mqsilist can be them, how to clean those brokers. |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Tue Mar 21, 2006 10:55 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
| Hi, I have successfully deleted those brokers,that is simple, just delete them from registry and components |
|
| Back to top |
|
|
|
|
