| Author |
Message
|
| jbanoop |
 Posted: Fri Oct 12, 2012 6:25 am Post subject: mqsicvp successful but message flow errors out - MB 7.0.0.3 |
 |
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
All,
environment is MB MB 7.0.0.3 on Linux.
The problem is that after a broker restart, we are facing database connectivity issues with a DSN. However the mqsicvp command is successful.
We have tried restarting the broker again and also tried restarting the EG/Flows.
Any help would be really appreciated.
The error message is as below:
| Code: |
BIP2393E: Database error: ODBC return code '-1' from data source 'ABCD' using ODBC driver manager 'libbipodbc.so'. : SGTW05.78efeb00-3401-0000-0080-e477ce22b968: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 349: ImbOdbcHandle::checkRcInner: :
Oct 12 08:43:56 lsoh0019mqapp01 WebSphere Broker v7003[18668]: (SGTW05.ADPT1)[5]BIP2322E: Database error: SQL State 'IM002'; Native Error Code '0'; Error Text '[DataDirect][ODBC lib] System information file not found. Please check the ODBCINI environment variable.'. : SGTW05.78efeb00-3401-0000-0080-e477ce22b968: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 518: ImbOdbcHandle::checkRcInner: :
|
The output of the mqsicvp is:
| Code: |
BIP8270I: Connected to Datasource 'ABCD' as user 'mbuser'. The datasource platform is 'DB2/LINUXX8664', version '09.05.0008'.
===========================
databaseProviderVersion = 09.05.0008
driverVersion = 09.07.0004
driverOdbcVersion = 03.51
driverManagerVersion = 3.52.0000
driverManagerOdbcVersion = 03.52.0000
databaseProviderName = DB2/LINUXX8664
datasourceServerName = db2clt9
databaseName = S141
odbcDatasourceName = ABCD
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 = 26
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = -99
longVarBinaryDatatype = -4
blobDatatype = -98
BIP8273I: The following datatypes and functions are not natively supported by datasource 'ABCD' using this ODBC driver: Unsupported datatypes: 'INTERVAL' Unsupported functions: 'POSITION, EXTRACT'
Examine the specific datatypes and functions not supported natively by this datasource using this ODBC driver.
When using these datatypes and functions within ESQL, the associated data processing 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.
BIP8071I: Successful command completion.
|
|
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Oct 12, 2012 6:28 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| jbanoop |
| Posted: Fri Oct 12, 2012 6:42 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
lancelotlinc,
Both the mqsicvp as well as the broker flows use the same id and it is a specific broker id which is NOT mqm.
the puzzling thing here is that mqsicvp (which is supposed to verify if DSNs are configured correctly for the broker) works while the flow that uses the DSN cant seem to get the right environment. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Oct 12, 2012 6:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Login with the service Id only and display the environment, and I think you will find that the ODBC envirionment variables are incorrect or not present.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| jbanoop |
| Posted: Fri Oct 12, 2012 8:30 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
We had to restart MQ and MB components and the error was addressed. We do not however understand the root cause of the issue yet.
We have MQ starting up with mqm and which in turn starts MB but with its own id (not as mqm). |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 12, 2012 8:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| jbanoop wrote: |
We had to restart MQ and MB components and the error was addressed. We do not however understand the root cause of the issue yet.
We have MQ starting up with mqm and which in turn starts MB but with its own id (not as mqm). |
You don't have the ODBCINI variable set in the shell that starts Broker, or you didn't have it set in the shell that last issued mqsistart. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Oct 12, 2012 11:08 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Especially on Linux, or AIX, I am much more fond of starting WMB from a startup script rather than from MQ service. You can have the same script start both WMQ and WMB, with a 90 second sleep between the two.
Not to say that the way you are doing it is wrong or won't work. It will. I just prefer the other way better.
Excellent foresight using a different service Id than mqm. Good job!
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 12, 2012 11:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
mqsistart will start the queue manager if it's not running already.
 |
|
| Back to top |
|
|
|
|
