| Author |
Message
|
| abhyyy |
 Posted: Thu Dec 15, 2011 11:59 pm Post subject: Component verification for broker failing |
 |
|
Voyager
Joined: 29 Sep 2011
Posts: 83
|
Hi Friends,
Problem is : Not able to start Broker after I did settings for connecting to remote DB2
Below are the steps that I followed and the Problem I am facing.
Step 1: Installed message broker and mq successfully on Redhat 6 (on lets say 'server1'
)
Step 2: Created broker(STARHUB_BROKER) and Queue manager (QM_STARHUB_BROKER), created Queues, deployed a simple flow and every thing worked fine.
Step 3: Now I wanted to connect to DB2 (installed on Linux,on server2) from message broker on server 1 so I ran below commands.
I place odbc.ini file inside /home/mqm/.odbc.ini with below mention entries inside it.
====================================
# DB2 stanza
[PEMKTODS]
Driver=/home/db2cli97/sqllib/lib/libdb2.so
Description=IBM DB2 ODBC Database
Database=PEMKTODS
Then set the environment variable as ODBCINI=/home/mqm/.odbc.ini
Then run the below command
mqsisetdbparms STARHUB_BROKER -n pemktods -u wmbdbadm -p xxxxxx
Now The (probable)Problem 1 is when I run below component verification command , I get a message in the end as shown
mqsicvp -n PEMKTODS -u wmbdbadm -p xxxxxx
BIP8270I: Connected to Datasource 'PEMKTODS' as user 'wmbdbadm'. The datasource platform is 'DB2/LINUXX8664', version '09.07.0005'.
===========================
databaseProviderVersion = 09.07.0005
driverVersion = 09.07.0005
driverOdbcVersion = 03.51
driverManagerVersion = 3.52.0000
driverManagerOdbcVersion = 03.52.0000
databaseProviderName = DB2/LINUXX8664
datasourceServerName = db2cli97
databaseName = PEMKTODS
odbcDatasourceName = PEMKTODS
driverName = libdb2.a
supportsStoredProcedures = Yes
procedureTerm = stored procedure
accessibleTables = No
accessibleProcedures = No
identifierQuote = "
specialCharacters = None
describeParameter = Yes
schemaTerm = schema
tableTerm = table
sqlSubqueries = 31
activeEnvironments = 1
maxDriverConnections = 0
maxCatalogNameLength = 0
maxColumnNameLength = 128
maxSchemaNameLength = 128
maxStatementLength = 2097152
maxTableNameLength = 128
supportsDecimalType = Yes
supportsDateType = Yes
supportsTimeType = Yes
supportsTimeStampType = Yes
supportsIntervalType = No
supportsAbsFunction = Yes
supportsAcosFunction = Yes
supportsAsinFunction = Yes
supportsAtanFunction = Yes
supportsAtan2Function = Yes
supportsCeilingFunction = Yes
supportsCosFunction = Yes
supportsCotFunction = Yes
supportsDegreesFunction = Yes
supportsExpFunction = Yes
supportsFloorFunction = Yes
supportsLogFunction = Yes
supportsLog10Function = Yes
supportsModFunction = Yes
supportsPiFunction = Yes
supportsPowerFunction = Yes
supportsRadiansFunction = Yes
supportsRandFunction = Yes
supportsRoundFunction = Yes
supportsSignFunction = Yes
supportsSinFunction = Yes
supportsSqrtFunction = Yes
supportsTanFunction = Yes
supportsTruncateFunction = Yes
supportsConcatFunction = Yes
supportsInsertFunction = Yes
supportsLcaseFunction = Yes
supportsLeftFunction = Yes
supportsLengthFunction = Yes
supportsLTrimFunction = Yes
supportsPositionFunction = No
supportsRepeatFunction = Yes
supportsReplaceFunction = Yes
supportsRightFunction = Yes
supportsRTrimFunction = Yes
supportsSpaceFunction = Yes
supportsSubstringFunction = Yes
supportsUcaseFunction = Yes
supportsExtractFunction = No
supportsCaseExpression = Yes
supportsCastFunction = Yes
supportsCoalesceFunction = Yes
supportsNullIfFunction = Yes
supportsConvertFunction = Yes
supportsSumFunction = Yes
supportsMaxFunction = Yes
supportsMinFunction = Yes
supportsCountFunction = Yes
supportsBetweenPredicate = Yes
supportsExistsPredicate = Yes
supportsInPredicate = Yes
supportsLikePredicate = Yes
supportsNullPredicate = Yes
supportsNotNullPredicate = Yes
supportsLikeEscapeClause = Yes
supportsClobType = Yes
supportsBlobType = Yes
charDatatypeName = CHAR
varCharDatatypeName = VARCHAR
longVarCharDatatypeName = LONG VARCHAR
clobDatatypeName = CLOB
timeStampDatatypeName = TIMESTAMP
binaryDatatypeName = CHAR (1) FOR BIT DATA
varBinaryDatatypeName = VARCHAR (1) FOR BIT DATA
longVarBinaryDatatypeName = LONG VARCHAR FOR BIT DATA
blobDatatypeName = BLOB
intDatatypeName = INTEGER
doubleDatatypeName = DOUBLE
varCharMaxLength = 32672
longVarCharMaxLength = 32700
clobMaxLength = 2147483647
varBinaryMaxLength = 32672
longVarBinaryMaxLength = 32700
blobMaxLength = 2147483647
timeStampMaxLength = 32
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = -99
longVarBinaryDatatype = -4
blobDatatype = -98
BIP8273I: The following datatypes and functions are not natively supported by da tasource 'PEMKTODS' using this ODBC driver: Unsupported datatypes: 'INTERVAL' Un supported functions: 'POSITION, EXTRACT'
Examine the specific datatypes and functions not supported natively by this data source using this ODBC driver.
When using these datatypes and functions within ESQL, the associated data proces sing is done within WebSphere Message Broker rather than being processed by the database provider.
Note that "functions" within this message can refer to functions or predicates.
PROBLEM 2 ::
Even If I ignore the above information, and try to start the Broker (which I was easily doing before) , I can't and I get the below message.
[root@wmb2 bin]# mqsistart STARHUB_BROKER
WebSphere MQ queue manager 'QM_STARHUB_BROKER' ending.
BIP8048E: It was not possible to start WebSphere MQ queue manager 'QM_STARHUB_BROKER'.
BIP8875W: The component verification for 'STARHUB_BROKER' 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.
BTW I have already added wmbdbadm in mqbrkrs and mqm group.
Please help if I have missed or messed up any thing here.[/b]
_________________
----------------------
NeVeR StOp LeaRnInG. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Dec 16, 2011 1:35 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I think you went wrong when you copoed the odbc.ini file from /var/mqsi/odbc to your directory.
This will only work IF
- Broker is created to use your account at runtime
OR
- You have given the account that broker runs under proper access to the ODBC.INI file in your account.
The 'odbc.ini' file is in /var/mqsi/odbc for a very good reason.
Ok, you might say that I want to run different brokers on the same box.
Easy. Here's how I do it.
Create different versions of the ODBC.ini file /var/mqsi/odbc/
for example
/var/mqsi/odbc/odbc_dev.ini
/var/mqsi/odbc/odbc_uat.ini
Then create different accounts for the broker to run under.
Then edit the .bashrc for these accounts to sourrce the mqsiprofile
Then add a definition to the .bashrc that points the ODBCINI environment variable to the correct odbc.ini file.
Always make trhe changes to these files by sudo'ing to the correct broker account and then editing $ODBCINI
By definig the ODBCINI variable in the .bashrc, a broker started up under that account will automatically use the right set of definitions.
We have a Linux POC server that has 4 different brokers defined on it. There are 4 different versions of the odbc.ini file in /var/mqsi/odbc.
_________________
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 |
|
|
| abhyyy |
| Posted: Fri Dec 16, 2011 2:01 am Post subject: |
|
|
Voyager
Joined: 29 Sep 2011
Posts: 83
|
| smdavies99 wrote: |
I think you went wrong when you copoed the odbc.ini file from /var/mqsi/odbc to your directory.
. |
I did not copy the odbc.ini file from /var/mqsi/odbc , I'm a first timer so I thought it had to be copied from /opt/ibm/mqsi/7.0/ODBC/unixodbc..
Is it where I went wrong??
And odbc.ini file in the /var/mqsi/odbc is having a lot of stanzas, should I delete all the stanzas apart from DB2 stanza and modify DB2 stanza in it
FROM
;# DB2 stanza
[DB2DB]
DRIVER=libdb2Wrapper.so
Description=DB2DB DB2 ODBC Database
Database=DB2DB
TO
[PEMKTODS]
Driver=/home/db2cli97/sqllib/lib/libdb2.so
Description=IBM DB2 ODBC Database
Database=PEMKTODS
_________________
----------------------
NeVeR StOp LeaRnInG. |
|
| Back to top |
|
|
| abhyyy |
| Posted: Fri Dec 16, 2011 2:28 am Post subject: |
|
|
Voyager
Joined: 29 Sep 2011
Posts: 83
|
I took your advice and changed the path of ODBCINI env variable to /var/mqsi/odbc/.odbc.ini and modified the odbc.ini file and just changed 2 entries inside it
changed to [PEMKTODS] from [DB2DB]
changed to Database=PEMKTODS from Database=DB2DB
for DB2 Stanza..
Still I am facing the same error(as below) while starting the Broker
[mqm@wmb2 bin]$ mqsistart STARHUB_BROKER
WebSphere MQ queue manager 'QM_STARHUB_BROKER' starting.
10 log records accessed on queue manager 'QM_STARHUB_BROKER' during the log replay phase.
Log replay for queue manager 'QM_STARHUB_BROKER' complete.
Transaction manager state recovered for queue manager 'QM_STARHUB_BROKER'.
AMQ6109: An internal WebSphere MQ error has occurred.
BIP8048E: It was not possible to start WebSphere MQ queue manager 'QM_STARHUB_BROKER'.
BIP8875W: The component verification for 'STARHUB_BROKER' 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.
_________________
----------------------
NeVeR StOp LeaRnInG. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Dec 16, 2011 2:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The failure to start the queue manager has nothing to do with the configuration of the ODBC connections.
You need to troubleshoot the failure to start the queue manager. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Dec 16, 2011 3:25 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
I'm not sure this is a DB problem.
The mqsicvp command (and broker startup) checks a number of parts of the environment including MQ, DB and Java.
The message you're seeing when you run that command is an informational one related to the DB driver inspection; it's just saying that your ODBC driver doesn't support all the capabilities available in ESQL, so the Broker will fall back to using its own implementations. That's fine.
I would be more concerned about this:
AMQ6109: An internal WebSphere MQ error has occurred.
BIP8048E: It was not possible to start WebSphere MQ queue manager 'QM_STARHUB_BROKER'.
Edit: Jeff got there before me; lucky we agree.  |
|
| Back to top |
|
|
| abhyyy |
| Posted: Fri Dec 16, 2011 7:59 pm Post subject: |
|
|
Voyager
Joined: 29 Sep 2011
Posts: 83
|
| mqmatt wrote: |
I would be more concerned about this:
AMQ6109: An internal WebSphere MQ error has occurred.
BIP8048E: It was not possible to start WebSphere MQ queue manager 'QM_STARHUB_BROKER'.
|
Point well agreed, I was trying to a find solution for this for for 2 days and am well stuck at this point and cant move an inch forward.
Is there a way I can troubleshoot this, as this error seems like giving generic details and I am not able to find what is the specific reason for QM_STARHUB_BROKER not starting up.
_________________
----------------------
NeVeR StOp LeaRnInG. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 16, 2011 9:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| abhyyy wrote: |
| mqmatt wrote: |
I would be more concerned about this:
AMQ6109: An internal WebSphere MQ error has occurred.
BIP8048E: It was not possible to start WebSphere MQ queue manager 'QM_STARHUB_BROKER'.
|
Point well agreed, I was trying to a find solution for this for for 2 days and am well stuck at this point and cant move an inch forward.
Is there a way I can troubleshoot this, as this error seems like giving generic details and I am not able to find what is the specific reason for QM_STARHUB_BROKER not starting up. |
There should be an FDC file related to that and some more information there...
Fix this first. Start the qmgr with mqm and leave it running. Then start the broker...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Dec 17, 2011 5:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| abhyyy wrote: |
| Is there a way I can troubleshoot this, as this error seems like giving generic details and I am not able to find what is the specific reason for QM_STARHUB_BROKER not starting up. |
Yes. The queue manager logs and FDC files as my most worthy associates point out.
At some point you bounced the broker to make the ini file effective. Did the queue manager close down as well? Did it go down clean? Have you got shared memory or semaphores hanging round?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Dec 19, 2011 5:20 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
I agree with Vitor and fjb_saper. There is advice already out there; for example, a quick look through the online docs showed the following response for AMQ6109:
| http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp wrote: |
| Use the standard facilities supplied with your system to record the problem identifier and to save any generated output files. Use either the WebSphere MQ Support site, or the IBM support assistant at http://www.ibm.com/software/support/isa/, to see whether a solution is already available. If you are unable to find a match, contact your IBM support center. Do not discard these files until the problem has been resolved. |
So, look at your FFSTs, try some web searches, raise a PMR. In that order. |
|
| Back to top |
|
|
|
|
