| Author |
Message
|
| RG520 |
 Posted: Tue Apr 21, 2009 4:12 am Post subject: Couldnt run broker after installed MQ 6.0.2.6 Fixpack |
 |
|
Newbie
Joined: 16 Mar 2009
Posts: 7
|
Hi guys, I'm quite new in MQ stuff. I hunted for the solution so i found this forum.
Anyway, Let me tell you what happened to our system.
First, we run MQ version 6.0.2 with Message Broker v 6.0.0.3 on AIX machine. We also have the other AIX machine to run DB2 v8.1.1.120 FP 13 64 bit (Broker's database is in this machine).
Everthing was fine until our technician asked us to upgrade MQ FX to version 6.0.2.6 then the problem occured.
After the installation was completed, we tried to run mqsistart MYBROKER and we found that it couldnt run.
This is what we found in user.log
| Code: |
Apr 19 13:17:48 seaibrt1 user:info WebSphere Broker v6003[389338]: (EAI_CM64)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6003; process ID 413712. : EAI_CM64.service: /build/S600_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 338: ImbControlService::StartNewAA: :
Apr 19 13:18:03 seaibrt1 user:info WebSphere Broker v6003[479476]: (EAI_BK64)[1]BIP2001I: The WebSphere Message Brokers service has started at version 6003; process ID 463058. : EAI_BK64.service: /build/S600_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 338: ImbControlService::StartNewAA: :
Apr 19 13:18:04 seaibrt1 user:err|error WebSphere Broker v6003[463058]: (EAI_BK64)[1]BIP2048E: An Exception was caught while issuing database SQL command connect. : EAI_BK64.agent: /build/S600_P/src/AdminAgent/ImbAdminStore.cpp: 305: ImbAdminStore::Connect: :
Apr 19 13:18:04 seaibrt1 user:err|error WebSphere Broker v6003[463058]: (EAI_BK64)[1]BIP2321E: Database error: ODBC return code '-1'. : EAI_BK64.agent: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 227: ImbOdbcHandle::checkRcInner: :
Apr 19 13:18:04 seaibrt1 user:err|error WebSphere Broker v6003[463058]: (EAI_BK64)[1]BIP2322E: Database error: SQL State 'IM003'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] Specified driver could not be loaded'. : EAI_BK64.agent: /build/S600_P/src/DataFlowEngine/ImbOdbc.cpp: 355: ImbOdbcHandle::checkRcInner: :
Apr 19 13:18:04 seaibrt1 user:err|error WebSphere Broker v6003[463058]: (EAI_BK64)[1]BIP2053E: The broker made an unsuccessful attempt to access its database BRK_DB64 with userid db2inst1. : EAI_BK64.agent: /build/S600_P/src/AdminAgent/ImbAdminAgent.cpp: 569: ImbAdminAgent::instanceOfAdminAgent: :
Apr 19 13:18:04 seaibrt1 user:err|error WebSphere Broker v6003[479476]: (EAI_BK64)[1]BIP2013E: The broker was unable to access its database. : EAI_BK64.service: /build/S600_P/src/AdminAgent/ControlProcess/rios_aix_4/ImbControlService.cpp: 398: ImbControlService::GetAAexitCode: : |
We've tired this suggestion
http://www.mqseries.net/phpBB2/viewtopic.php?t=30025&highlight=10g
but it doesnt work.
It would be great if anybody can give a hint to fix it.  |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Apr 21, 2009 4:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Let's double-check some things.
You had a perfectly working Broker, accessing a perfectly working remote database.
You stopped everything in the correct way, and applied maintenance to MQ.
You then attempted to start everything in the correct way...and started having trouble accessing the Broker's *database*?
Do you have the Queue Manager configured to do global coordination against the external database?
You should talk to the database administrator as well, and ask them to see if there are errors on the remote side, or if for example the password for the database user has changed. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Apr 21, 2009 7:23 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| By the way, I believe DB2 8.2 and less are at End of Service now or at the end of this month... |
|
| Back to top |
|
|
| RG520 |
| Posted: Tue Apr 21, 2009 8:35 pm Post subject: |
|
|
Newbie
Joined: 16 Mar 2009
Posts: 7
|
| Quote: |
You had a perfectly working Broker, accessing a perfectly working remote database.
You stopped everything in the correct way, and applied maintenance to MQ.
You then attempted to start everything in the correct way...and started having trouble accessing the Broker's *database*?
|
Yes,that's right.
| Quote: |
| Do you have the Queue Manager configured to do global coordination against the external database? |
Yes, we have.
I asked our DBA to see if something error on DB server. They said everthing's just fine.
I also tried to connect to a remote DB using db2 connect command with the same username and password used by Broker and it worked.
Just when I tried to run mqsistart MYBROKER, it got errors.
Well, I also ran mqsilist MYBROKER. What I've got is
| Code: |
[wmbadmin@seaibrt1 /usr/IBM/mqsi/bin ]#mqsilist EAI_BK64
BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
BIP2322E: Database error: SQL State ''IM003''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''.
The error has the following diagnostic information: SQL State ''IM003'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Specified driver could not be loaded''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
BIP8040E: Unable to connect to the database.
The database cannot be accessed with the userid and password that were specified when the broker was created.
Check that the database is running, that an ODBC connection has been created and that the userid and password pair specified for ODBC connect on the mqsicreate command are capable of being used to connect to the database using an ODBC connection. Also ensure that the database has a adequate number of database connections available for use.
|
It seems like I got a problem with ODBC Driver? any suggestion would be appreciated.  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Apr 21, 2009 11:36 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Try starting the DB before you start MQ or the broker... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| RG520 |
| Posted: Wed Apr 22, 2009 1:22 am Post subject: |
|
|
Newbie
Joined: 16 Mar 2009
Posts: 7
|
Hi fjb_saper. I did start DB before MQ and Broker.
More information for you all.
| Code: |
[wmbadmin@seaibrt1 /home/wmbadmin ]#mqsiservice EAI_BK64
BIPv600 en US
ucnv Console CCSID 874 dft ucnv CCSID 874
ICUW ISO-8859-1 ICUA ISO-8859-1
Install Path = /usr/IBM/mqsi
Working Path = /var/mqsi
Component UUID = c91563d0-0e01-0000-0080-a7e1d56d4b13
process id = 626798
broker db name = BRK_DB64
broker db userId = db2inst1
broker db password =
queue manager = EAI_QM64
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
BIP8071I: Successful command completion.
[wmbadmin@seaibrt1 /home/wmbadmin ]#db2 connect to BRK_DB64 user db2inst1 using db2pwd1
Database Connection Information
Database server = DB2/AIX64 8.2.6
SQL authorization ID = DB2INST1
Local database alias = BRK_DB64
|
Still when I ran mqsistart EAI_BK64, I got following error in user.log
| Code: |
Apr 22 16:18:04 seaibrt1 user:err|error WebSphere Broker v6003[463058]: (EAI_BK64)[1]BIP2053E: The broker made an unsuccessful attempt to access its database BRK_DB64 with userid db2inst1. :
|
|
|
| Back to top |
|
|
| zpat |
| Posted: Wed Apr 22, 2009 1:26 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
DB2 8.2 remains supported when used with WMB 6.0. The WMB product team have an agreement with the DB2 team for this.
WMB 6.0 has no end of support date yet. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 22, 2009 3:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Try using mqsichangebroker to set the broker database password again. |
|
| Back to top |
|
|
| RG520 |
| Posted: Wed Apr 22, 2009 3:25 am Post subject: |
|
|
Newbie
Joined: 16 Mar 2009
Posts: 7
|
Hi mqjeff.
I did run mqsichangebroker EAI_BK64 -p db2pwd1 but still couldnt work. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 22, 2009 3:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| You should either open a PMR, or get your DBA to run traces on the connection that broker is attempting to make. |
|
| Back to top |
|
|
| RG520 |
| Posted: Wed Apr 22, 2009 6:19 pm Post subject: |
|
|
Newbie
Joined: 16 Mar 2009
Posts: 7
|
Well, maybe open PMR is a best solution.
Thanks you all, anyway.
I'll let you guy know if I can fix it. |
|
| Back to top |
|
|
| harish_td |
| Posted: Wed Apr 22, 2009 7:10 pm Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
| Can you re-check the contents of the ODBC64.INI file? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Apr 22, 2009 9:16 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| RG520 wrote: |
Well, maybe open PMR is a best solution.
Thanks you all, anyway.
I'll let you guy know if I can fix it. |
We just had a very similar problem. It had to do with the way the shared memory allocation table works in 32 bit apps in AIX. Db2 was the culprit this time and we were getting strange messages in the broker log.
Record everything and work the PMR with IBM.
If you need a really quick fix you can always try to reboot the box. This will get rid of the shared memory stuff. It fixes the symptom and not the cause. For that you will need to install some APARS.
I'm not at work or I would add a link to the relevant db2 doc...
Not saying that you have the same problem but it could be similar...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| RG520 |
| Posted: Sun Apr 26, 2009 11:37 pm Post subject: |
|
|
Newbie
Joined: 16 Mar 2009
Posts: 7
|
Well, after I reviewed variables in the user's environment, I just found out LIBPATH was set to
| Code: |
| LIBPATH=/usr/IBM/mqsi/jre/bin:/usr/IBM/mqsi/jre/bin/classic:/usr/mqm/java/lib:/usr/IBM/mqsi/lib:/usr/IBM/mqsi/bin:/usr/IBM/mqsi/merant/lib:/usr/IBM/mqsi/xml4c/lib:/usr/lib:/lib:/home/db2inst1/sqllib/lib |
So I changed it to
| Code: |
| LIBPATH=/home/db2inst1/sqllib/lib32:/usr/IBM/mqsi/jre/bin:/usr/IBM/mqsi/jre/bin/classic:/usr/mqm/java/lib:/usr/IBM/mqsi/lib:/usr/IBM/mqsi/bin:/usr/IBM/mqsi/merant/lib:/usr/IBM/mqsi/xml4c/lib:/usr/lib:/lib:/home/db2inst1/sqllib/lib |
then it worked.
But now, I got a new problem with DB2 under this user. So I'm gonna fix it later.
Just wonder why the system could work under the old enviroment without any problem??? Any idea??? |
|
| Back to top |
|
|
|
|
