| Author |
Message
|
| arijitchakraborty1986 |
 Posted: Mon Jul 13, 2015 3:06 am Post subject: Not able to create ODBC connectivity from IIB9 |
 |
|
Newbie
Joined: 13 Jul 2015
Posts: 5
|
Hi, I am not able to connect to IIB9. I am getting below error.
<text>Exception. BIP2230E: Error detected whilst processing a message in node 'JSON_WEBSERVICE.Compute'. : F:\build\slot1\S900_P\src\DataFlowEngine\SQLNodeLibrary\ImbComputeNode.cpp: 497: ImbComputeNode::evaluate: ComIbmComputeNode: JSON_WEBSERVICE#FCMComposite_1_5
BIP2393E: Database error: ODBC return code '-1' from data source ''TEST'' using ODBC driver manager ''odbc32.dll''. : F:\build\slot1\S900_P\src\DataFlowEngine\MessageServices\ImbOdbc.cpp: 2260: ImbOdbcConnection::checkRcInner: :
BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''. : F:\build\slot1\S900_P\src\DataFlowEngine\MessageServices\ImbOdbc.cpp: 2438: ImbOdbcConnection::checkRcInner: : </text>
--------------------
When i am running mqsicvp command i am getting below output
mqsicvp IB9NODE -n Test -i db2admin
BIP8270I: Connected to Datasource 'Test' as user 'db2admin'. The datasource pla
form is 'DB2/NT64', version '09.07.0000'.
===========================
databaseProviderVersion = 09.07.0000
driverVersion = 09.07.0000
driverOdbcVersion = 03.51
driverManagerVersion = 03.80.7601.0000
driverManagerOdbcVersion = 03.80.0000
databaseProviderName = DB2/NT64
datasourceServerName = DB2
databaseName = ARIJITDB
odbcDatasourceName = ARIJITDB
driverName = DB2CLI.DLL
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 = 0
longVarCharMaxLength = 0
clobMaxLength = 0
varBinaryMaxLength = 0
longVarBinaryMaxLength = 0
blobMaxLength = 0
timeStampMaxLength = 0
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = -99
longVarBinaryDatatype = -4
blobDatatype = -98
BIP8273I: The following datatypes and functions are not natively supported by d
tasource 'Test' using this ODBC driver: Unsupported datatypes: 'INTERVAL' Unsup
orted functions: 'POSITION, EXTRACT'
Examine the specific datatypes and functions not supported natively by this dat
source using this ODBC driver.
When using these datatypes and functions within ESQL, the associated data proce
sing is done within IBM Integration Bus rather than being processed by the data
ase provider.
Note that "functions" within this message can refer to functions or predicates.
BIP8071I: Successful command completion.
--------------------------
In my message flow in compute node i define data source name as Test.
code:-
SET OutputRoot.JSON.Data[] = SELECT * FROM Database.db2admin.Test AS P WHERE P.TPNB = productid;
i also created obdc data source in my system as Test.
Please help me to solve this issue. |
|
| Back to top |
|
 |
| maurito |
| Posted: Mon Jul 13, 2015 4:11 am Post subject: Re: Not able to create ODBC connectivity from IIB9 |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| arijitchakraborty1986 wrote: |
In my message flow in compute node i define data source name as Test.
code:-
SET OutputRoot.JSON.Data[] = SELECT * FROM Database.db2admin.Test AS P WHERE P.TPNB = productid;
i also created obdc data source in my system as Test.
|
You don't define the datasource in the code. In the select statement you specify a table name. The datasource is specified elsewhere ( and it is well documented ). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 13, 2015 4:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you sure you are using the correct datasource setup?
mqsicvp -n Test -i db2admin shows
| Code: |
BIP8270I: Connected to Datasource 'Test' as user 'db2admin'. The datasource pla
form is 'DB2/NT64', version '09.07.0000'. |
Where your error message shows:
| Quote: |
BIP2393E: Database error: ODBC return code '-1' from data source ''TEST'&apos
Error Text ''[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified''. |
Remember Test is not the same as TEST. CASE MATTERS!!! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| arijitchakraborty1986 |
| Posted: Mon Jul 13, 2015 4:29 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 5
|
| Compute Node->Properties->Basic->Data Source here i declared it as Test[/img] |
|
| Back to top |
|
|
| maurito |
| Posted: Mon Jul 13, 2015 4:38 am Post subject: Re: Not able to create ODBC connectivity from IIB9 |
|
|
Partisan
Joined: 17 Apr 2014
Posts: 358
|
| arijitchakraborty1986 wrote: |
using ODBC driver manager ''odbc32.dll'&apos
databaseProviderName = DB2/NT64
|
are you using the correct driver ? |
|
| Back to top |
|
|
| arijitchakraborty1986 |
| Posted: Mon Jul 13, 2015 4:40 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 5
|
| How to check this driver? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jul 13, 2015 4:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| arijitchakraborty1986 wrote: |
| How to check this driver? |
Check to see if it's the one you need for the database you're trying to connect to. There seems to be a discrepancy in the bitness from what you've posted.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wbisantosh |
| Posted: Mon Jul 13, 2015 12:48 pm Post subject: |
|
|
Apprentice
Joined: 12 Nov 2012
Posts: 47
|
arijitchakraborty1986,
You might want to check the DB Connectivity from Compute Node first. Select the Check Box "Connect before flow starts" from the Compute node properties to do that.
This is a Sample Syntax for a DB Select statement from a Compute Node -
| Code: |
SET PartsTable.Part[] = SELECT
P.PartNumber,
P.Description,
P.Price
FROM Database.Datasource.SchemaName.Table AS P; |
If not you could also give "PASSTHRU" statement a try
Santosh |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Jul 13, 2015 12:53 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
I suspect that you may have defined the DSN as a User DSN rather than a System DSN in the ODBC control panel applet. This would explain why it works on the command line but the DSN is not found in the compute node as the Node (Broker) is running with a different user id to the one on your command line. User DSNs do work, but only when the Broker is running as the same user id that the DSN is defined for...
Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| arijitchakraborty1986 |
| Posted: Mon Jul 13, 2015 10:51 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2015
Posts: 5
|
Thank you very much.Issue got resolved:P. I delete User DSN from my system and create one System DSN which helped to resolve problem.
Thanks to all of you. |
|
| Back to top |
|
|
|
|
