| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [DataDirect][ODBC lib] System information file not found |
« View previous topic :: View next topic » |
| Author |
Message
|
| KIT_INC |
 Posted: Sat Feb 01, 2014 1:25 pm Post subject: [DataDirect][ODBC lib] System information file not found |
 |
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
This is a new WMB V7004 install under OpenSuse
The message flow failed with error
Feb 1 16:07:11 remotehost WebSphere Broker v7004[27261]: (WMBBRKU2.WMBCNEG02)[11]BIP2393E: Database error: ODBC return code '-1' from data source 'WMBDBU' using ODBC driver manager 'libbipodbc.so'. : WMBBRKU2.546dc0b0-4301-0000-0080-90215824b243: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 351: ImbOdbcHandle::checkRcInner: :
Feb 1 16:07:11 remotehost WebSphere Broker v7004[27261]: (WMBBRKU2.WMBCNEG02)[11]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.'. : WMBBRKU2.546dc0b0-4301-0000-0080-90215824b243: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 520: ImbOdbcHandle::checkRcInner: :
I ran MQSICVP with no problem ( I think , unless I miss something)
mqsicvp WMBBRKU2 -n WMBDBU
BIP8270I: Connected to Datasource 'WMBDBU' as user 'RXIMG'. The datasource platform is 'Oracle', version '11.02.0000 Oracle 11.2.0.3.0'.
===========================
databaseProviderVersion = 11.02.0000 Oracle 11.2.0.3.0
driverVersion = 06.00.0266 (B0190, U0090)
driverOdbcVersion = 03.52
driverManagerVersion = 3.52.0000
driverManagerOdbcVersion = 03.52.0000
databaseProviderName = Oracle
datasourceServerName = WMBdbuscan.hosts.KitInc.ca
databaseName = N/A
odbcDatasourceName = WMBDBU
driverName = UKora24.so
supportsStoredProcedures = Yes
procedureTerm = PL/SQL
accessibleTables = Yes
accessibleProcedures = Yes
identifierQuote = "
specialCharacters = None
describeParameter = Yes
schemaTerm = User Name
tableTerm = Table
sqlSubqueries = 31
activeEnvironments = 0
maxDriverConnections = 0
maxCatalogNameLength = 128
maxColumnNameLength = 30
maxSchemaNameLength = 30
maxStatementLength = 0
maxTableNameLength = 30
supportsDecimalType = Yes
supportsDateType = No
supportsTimeType = No
supportsTimeStampType = Yes
supportsIntervalType = No
supportsAbsFunction = Yes
supportsAcosFunction = No
supportsAsinFunction = No
supportsAtanFunction = No
supportsAtan2Function = No
supportsCeilingFunction = Yes
supportsCosFunction = Yes
supportsCotFunction = No
supportsDegreesFunction = No
supportsExpFunction = Yes
supportsFloorFunction = Yes
supportsLogFunction = Yes
supportsLog10Function = Yes
supportsModFunction = Yes
supportsPiFunction = No
supportsPowerFunction = Yes
supportsRadiansFunction = No
supportsRandFunction = No
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 = No
supportsCastFunction = No
supportsCoalesceFunction = No
supportsNullIfFunction = No
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 = No
supportsBlobType = No
charDatatypeName = CHAR
varCharDatatypeName = VARCHAR2
longVarCharDatatypeName = CLOB
clobDatatypeName = N/A
timeStampDatatypeName = TIMESTAMP
binaryDatatypeName = RAW
varBinaryDatatypeName = RAW
longVarBinaryDatatypeName = BLOB
blobDatatypeName = N/A
intDatatypeName = NUMBER
doubleDatatypeName = BINARY_DOUBLE
varCharMaxLength = 4000
longVarCharMaxLength = 2147483647
clobMaxLength = 0
varBinaryMaxLength = 2000
longVarBinaryMaxLength = 2147483647
blobMaxLength = 0
timeStampMaxLength = 29
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = 0
longVarBinaryDatatype = -4
blobDatatype = 0
BIP8273I: The following datatypes and functions are not natively supported by datasource 'WMBDBU' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, INTERVAL, CLOB, BLOB' Unsupported functions: 'ACOS, ASIN, ATAN, ATAN2, COT, DEGREES, PI, RADIANS, RAND, POSITION, EXTRACT, CASE, CAST, COALESCE, NULLIF'
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.
my ODBC environment variable is
ODBCINI=/var/mqsi/odbc/odbc.ini
and file attribute is
-rw-r--r-- 1 mqm mqbrkrs 2274 2013-12-24 12:39 /var/mqsi/odbc/odbc.ini
Any help would be greatly appreciated. |
|
| Back to top |
|
 |
| dogorsy |
| Posted: Mon Feb 03, 2014 1:59 am Post subject: Re: [DataDirect][ODBC lib] System information file not found |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| KIT_INC wrote: |
This is a new WMB V7004 install under OpenSuse
The message flow failed with error
Feb 1 16:07:11 remotehost WebSphere Broker v7004[27261]: (WMBBRKU2.WMBCNEG02)[11]BIP2393E: Database error: ODBC return code '-1' from data source 'WMBDBU' using ODBC driver manager 'libbipodbc.so'. : WMBBRKU2.546dc0b0-4301-0000-0080-90215824b243: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 351: ImbOdbcHandle::checkRcInner: :
Feb 1 16:07:11 remotehost WebSphere Broker v7004[27261]: (WMBBRKU2.WMBCNEG02)[11]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.'. : WMBBRKU2.546dc0b0-4301-0000-0080-90215824b243: /build/S700_P/src/DataFlowEngine/ImbOdbc.cpp: 520: ImbOdbcHandle::checkRcInner: :
I ran MQSICVP with no problem ( I think , unless I miss something)
mqsicvp WMBBRKU2 -n WMBDBU
BIP8270I: Connected to Datasource 'WMBDBU' as user 'RXIMG'. The datasource platform is 'Oracle', version '11.02.0000 Oracle 11.2.0.3.0'.
===========================
databaseProviderVersion = 11.02.0000 Oracle 11.2.0.3.0
driverVersion = 06.00.0266 (B0190, U0090)
driverOdbcVersion = 03.52
driverManagerVersion = 3.52.0000
driverManagerOdbcVersion = 03.52.0000
databaseProviderName = Oracle
datasourceServerName = WMBdbuscan.hosts.KitInc.ca
databaseName = N/A
odbcDatasourceName = WMBDBU
driverName = UKora24.so
supportsStoredProcedures = Yes
procedureTerm = PL/SQL
accessibleTables = Yes
accessibleProcedures = Yes
identifierQuote = "
specialCharacters = None
describeParameter = Yes
schemaTerm = User Name
tableTerm = Table
sqlSubqueries = 31
activeEnvironments = 0
maxDriverConnections = 0
maxCatalogNameLength = 128
maxColumnNameLength = 30
maxSchemaNameLength = 30
maxStatementLength = 0
maxTableNameLength = 30
supportsDecimalType = Yes
supportsDateType = No
supportsTimeType = No
supportsTimeStampType = Yes
supportsIntervalType = No
supportsAbsFunction = Yes
supportsAcosFunction = No
supportsAsinFunction = No
supportsAtanFunction = No
supportsAtan2Function = No
supportsCeilingFunction = Yes
supportsCosFunction = Yes
supportsCotFunction = No
supportsDegreesFunction = No
supportsExpFunction = Yes
supportsFloorFunction = Yes
supportsLogFunction = Yes
supportsLog10Function = Yes
supportsModFunction = Yes
supportsPiFunction = No
supportsPowerFunction = Yes
supportsRadiansFunction = No
supportsRandFunction = No
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 = No
supportsCastFunction = No
supportsCoalesceFunction = No
supportsNullIfFunction = No
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 = No
supportsBlobType = No
charDatatypeName = CHAR
varCharDatatypeName = VARCHAR2
longVarCharDatatypeName = CLOB
clobDatatypeName = N/A
timeStampDatatypeName = TIMESTAMP
binaryDatatypeName = RAW
varBinaryDatatypeName = RAW
longVarBinaryDatatypeName = BLOB
blobDatatypeName = N/A
intDatatypeName = NUMBER
doubleDatatypeName = BINARY_DOUBLE
varCharMaxLength = 4000
longVarCharMaxLength = 2147483647
clobMaxLength = 0
varBinaryMaxLength = 2000
longVarBinaryMaxLength = 2147483647
blobMaxLength = 0
timeStampMaxLength = 29
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = 0
longVarBinaryDatatype = -4
blobDatatype = 0
BIP8273I: The following datatypes and functions are not natively supported by datasource 'WMBDBU' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, INTERVAL, CLOB, BLOB' Unsupported functions: 'ACOS, ASIN, ATAN, ATAN2, COT, DEGREES, PI, RADIANS, RAND, POSITION, EXTRACT, CASE, CAST, COALESCE, NULLIF'
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.
my ODBC environment variable is
ODBCINI=/var/mqsi/odbc/odbc.ini
and file attribute is
-rw-r--r-- 1 mqm mqbrkrs 2274 2013-12-24 12:39 /var/mqsi/odbc/odbc.ini
Any help would be greatly appreciated. |
check that the user accessing the odbc.ini file have read permissions to the file. i.e., the userid that the broker uses to access the database. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Mon Feb 03, 2014 5:29 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
The broker was started with mqm user ID
The Dataflow engine WMBCNEG02 is running with mqm
I can edit the odbc.ini file with mqm login.
Please correct me if I am wrong. I thought that mqsicvp is using userid and password set using the setdbparm command. The execution group should be using the same ? I like to confirm if this is the correct understanding before I turn on tracing (need to invoke the linux team to do it). |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Feb 03, 2014 5:59 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What user are you running the broker under.
There are some very good reasons why you should not use the mqm user.
Many of these are discussed in a length post in this forum.
If you are using a different user why don't you 'su' to that user, make sure the mqsiprofile is executed and try the mqsicvp command again.
_________________
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 |
|
|
| KIT_INC |
| Posted: Mon Feb 03, 2014 6:19 am Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| Quote: |
| If you are using a different user why don't you 'su' to that user, make sure the mqsiprofile is executed and try the mqsicvp command again |
I did not so the original setup and was only asked to debug. The broker is a MI broker started by the MQ Qmgr. That is probably why it was running under mqm.
For running mqsicvp, the info center says
"On Linux and UNIX systems, run this command as the user ID under which you started, or will start, the broker by using the mqsistart command."
What other userId should I tried ? |
|
| Back to top |
|
|
| smuktineni |
| Posted: Tue Feb 04, 2014 8:33 pm Post subject: |
|
|
Apprentice
Joined: 28 Aug 2003
Posts: 33
Location: Omaha
|
Also the user who starts broker should have mqbrkrs as their primary group, just my 2 cents
_________________
-Satish |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 05, 2014 5:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The interactive shell that you log into as the mqm user is not guaranteed to be the same shell that a running queue manager uses to launch service processes.
You say you've been asked to debug this. Was this all working at some time in the past, including accessing the database? And now it's not working?
Or is this the first time they are trying to get the broker to access a database? |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Thu Feb 06, 2014 1:17 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| This is a new build. So it was not working before. The system team build the broker and use mqsicvp to do the basic test. Then pass the machine to us to test the application. |
|
| Back to top |
|
|
| KIT_INC |
| Posted: Thu Feb 06, 2014 1:26 pm Post subject: |
|
|
Knight
Joined: 25 Aug 2006
Posts: 589
|
| I have a basic question. Since this is a MI broker and is started as MQ service. Is there a way to control what user Id it should be running under ? I looked at the MQSC command for defining MQ service, I do not see any parameter to user ID. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Feb 06, 2014 6:19 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
you need to start the service using "sudo su - user command" or just "sudo command" depending on how your OS team set it up.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
