| Author |
Message
|
| alma |
 Posted: Tue Feb 01, 2011 12:11 pm Post subject: mqsistart TESTBROKER error |
 |
|
Apprentice
Joined: 26 Jan 2011
Posts: 36
|
Dear Everyone,
I am not a Message Broker administrator still I have gotten this task.
There is a broker what is down and I don't know why.
It gives me the next messages:
| Quote: |
$ mqsistart TESTBROKER
BIP8875W: The component verification for 'TESTBROKER' has finished, but one or more checks failed.
One or more of the component verification checks failed.
Check the error log for preceding error messages.
$ mqsilist TESTBROKER
BIP2393E: Database error: ODBC return code '-1' from data source ''WSMBDB''.
The broker received an error when executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database about this error.
Use the following messages to determine the cause of the error. Typical causes are incorrect data source or table names. Correct either the database or the broker configuration.
BIP2322E: Database error: SQL State ''IM004''; Native Error Code '0'; Error Text ''[DataDirect][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed''.
The error has the following diagnostic information: SQL State ''IM004'' SQL Native Error Code '0' SQL Error Text ''[DataDirect][ODBC lib] Driver's SQLAllocHandle on SQL_HANDLE_ENV failed''
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 specified user Id and password pair.
- Check that the database is running.
- On Windows, check that an ODBC connection has been created.
- On systems that use $ODBCINI, check that the file pointed to by $ODBCINI has been correctly updated.
- Use mqsichangebroker brokername -a xxx to set the password to the correct value and try again.
Use mqsichangeconfigmgr configmgr -a xxx to set the password to the correct value and try again.
- Check that the database has an adequate number of database connections available for use.
|
Database is running, $ODBCINI is set. ...?
???
Thank you. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Feb 01, 2011 12:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What platform(s) is/are this on?
Can you use the ODBC indicated from other applications without error?
Can you use the ODBC indicated from other applications with the id & password broker is using?
How have you proved the database is running?
If you're not a Message Broker Administrator how did you get this task? Where's the admin & why are they not fixing this?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 01, 2011 12:26 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you're on broker v7, you can use mqsicvp to test the datasource independently of the Broker.
But if you were on Broker v7, the broker wouldn't be trying to connect to a database at startup like that...
Most likely cause is that the ODBC.ini file does not have the WSMBDB entry configured correctly. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Feb 01, 2011 12:47 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If this errant Broker was a V7 one then why would just starting the Broker need to access an ODBC database?
If this was V7 then only when the flows get going would any ODBC connections be opened up?
As mqjeff says the mqsicvp (V7 only I'm sorry to say) utility is very useful for sorting out ODBC issues.
_________________
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 |
|
|
| alma |
| Posted: Tue Feb 01, 2011 12:58 pm Post subject: |
|
|
Apprentice
Joined: 26 Jan 2011
Posts: 36
|
I won this task becasue the firm that did the administration suddenly went away , and I was the only one who attended a short course about MQ and MB even so I want to learn them.
The database:
| Quote: |
$ db2 connect to WSMBDB
Database Connection Information
Database server = DB2/AIX64 9.1.7
SQL authorization ID = DB2INST1
Local database alias = WSMBDB |
| Quote: |
$ db2 list active databases
Active Databases
Database name = WSMBDB
Applications connected currently = 2
Database path = /home/db2inst1/db2inst1/NODE0000/SQL00001/ |
Thank you the quick answer. |
|
| Back to top |
|
|
| alma |
| Posted: Tue Feb 01, 2011 1:00 pm Post subject: |
|
|
Apprentice
Joined: 26 Jan 2011
Posts: 36
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 01, 2011 1:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Neither of the 2 commands you've posted prove all that much. The connect is performed via the DB2 client not by the ODBC, and the fact that the database is active doesn't mean it's in any fit state to be used. As an extreme example, an application could time out because of a table deadlock or receive a deadlock error and the database would still be shown as active.
The error shown on broker startup is not a broker error; it's the error being returned from the ODBC driver repeated verbatum. It indicates that, for some reason, the driver was unable to obtain a connection handle from the database.
Hence it's in this area (as myself and others have indicated) you must investigate.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 01, 2011 1:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| alma wrote: |
| I was the only one who attended a short course about MQ and MB |
Presumably you've spoken to your management about a number of long courses? With the word "Administration" in their title?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 01, 2011 1:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| alma wrote: |
| I won this task becasue the firm that did the administration suddenly went away |
Ok, I'm going to ask - why? Most commercial organizations don't just up and leave.
(I've got my fingers crossed for massive corporate fraud or alien abduction, but that's just me).
More importantly, did they leave any documentation behind that describes your set up? Under most agreements that's the property of the client (i.e. your company) and could contain potentially useful clues for you.
There is of course the time honoured questions which I'll repeat here for the record:
- when was this broker last running?
- why was it stopped?
- what's changed in the environment since it stopped?
It may seem obvious, but on at least 1 occassion I was asked to diagnose a broker that wouldn't restart with ODBC issues and I wasted a good 10 minutes fiddling round before I thought to ask these obvious questions.
The answer - "the DBA wanted to apply maintenance & update the ODBC drivers" - would have been a serious clue to why the broker was acting as it was.
Not saying that's the problem here; just saying.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Tue Feb 01, 2011 1:12 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
As mqjeff said
| mqjeff wrote: |
| Most likely cause is that the ODBC.ini file does not have the WSMBDB entry configured correctly. |
So whats in your ODBC.ini file ?
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 01, 2011 1:12 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Edited because the padre beat me to it. Which would never happen were "it" a bottle of the old Janx spirit. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Tue Feb 01, 2011 1:14 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| mqjeff wrote: |
| mqjeff wrote: |
| Most likely cause is that the ODBC.ini file does not have the WSMBDB entry configured correctly. |
|
Beat me to it  . Thought you might have gone home by now.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| fatherjack |
| Posted: Tue Feb 01, 2011 1:20 pm Post subject: |
|
|
Knight
Joined: 14 Apr 2010
Posts: 522
Location: Craggy Island
|
| mqjeff wrote: |
| Edited because the padre beat me to it. Which would never happen were "it" a bottle of the old Janx spirit. |
Not an HHG aficionado myself....... But partial to a bottle of old Janx...... or a bottle of anything in fact. Toilet Duck included.
_________________
Never let the facts get in the way of a good theory. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 01, 2011 1:21 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fatherjack wrote: |
| Thought you might have gone home by now. |
Well, if I were working my normal schedule, I'd have stepped away for a few hours around about now.
But since I usually work from home, that's not the same as "gone home".
And I'm not on my normal schedule this week anyway.
Regardless, as Vitor says - if this was working previously, what changed? If this wasn't working previously, then the ODBC.ini file is likely wrong. |
|
| Back to top |
|
|
| alma |
| Posted: Tue Feb 01, 2011 1:26 pm Post subject: |
|
|
Apprentice
Joined: 26 Jan 2011
Posts: 36
|
This is a part of odbc64.ini:
| Quote: |
;# DB2 stanza
[WSMBDB]
DRIVER=libdb2Wrapper64.so
Description=DB2DB DB2 ODBC Database
Database=WSMBDB
;##########################################
;###### Mandatory information stanza ######
;##########################################
[ODBC]
;# To turn on ODBC trace set Trace=1
Trace=0
TraceFile=/tmp/odbctrace64.out
TraceDll=/opt/IBM/mqsi/6.1/ODBC64/V5.3/lib/odbctrac.so
InstallDir=/opt/IBM/mqsi/6.1/ODBC64/V5.3
UseCursorLib=0
IANAAppCodePage=4
UNICODE=UTF-8 |
Ok, I start to investigate the odbc setup. |
|
| Back to top |
|
|
|
|
