Author |
Message
|
ghoshly |
Posted: Mon Feb 25, 2013 6:51 am Post subject: Data source name not found and no default driver specified |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
Hello,
I am facing the data source error as "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified" when trying to access Oracle database from compute node through odbc DSN. Please help me to find the step I am missing.
1. Created Broker in Windows 7
2. Create ODBC DSN using Administrative tools and tested connection
3. mqsisetdbparms - added the DSN with broker
4. Same DSN used in Compute node
5. tested with mqsicvp command.
Code: |
BIP8996I: Version: 7001
BIP8997I: Product: WebSphere Message Broker
BIP8998I: CMVC Level: S700-FP01
BIP8999I: Build Type: Production |
Code: |
C:\IBM\MQSI\7.0>mqsistop LOCALBRK
BIP8071I: Successful command completion.
C:\IBM\MQSI\7.0>
C:\IBM\MQSI\7.0>mqsisetdbparms LOCALBRK -n ESBDB -u sdxesb_dev_owner -p sdxesb_7
485_ -f
BIP8071I: Successful command completion.
C:\IBM\MQSI\7.0>
C:\IBM\MQSI\7.0>mqsistart LOCALBRK
BIP8096I: Successful command initiation, check the system log to ensure that the
component started without problem and that it continues to run without problem.
C:\IBM\MQSI\7.0>mqsicvp LOCALBRK -n ESBDB
BIP8270I: Connected to Datasource 'ESBDB' as user 'SDXESB_DEV_OWNER'. The dataso
urce platform is 'Oracle', version '11.01.0000 Oracle 11.1.0.0.0'.
===========================
databaseProviderVersion = 11.01.0000 Oracle 11.1.0.0.0
driverVersion = 06.00.0175 (B0126, U0056)
driverOdbcVersion = 03.52
driverManagerVersion = 03.80.7601.0000
driverManagerOdbcVersion = 03.80.0000
databaseProviderName = Oracle
datasourceServerName = sdxbf-maxnpdb1.na.sdxcorp.net
databaseName = N/A
odbcDatasourceName = ESBDB
driverName = UKORA24.DLL
supportsStoredProcedures = Yes
procedureTerm = PL/SQL
accessibleTables = Yes
accessibleProcedures = Yes
identifierQuote = "
specialCharacters = None
describeParameter = No
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 da
tasource 'ESBDB' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, INT
ERVAL, 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 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.
BIP8071I: Successful command completion.
C:\IBM\MQSI\7.0> |
Please help. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Feb 25, 2013 6:54 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
1. You need to update your toolkit and runtime. 7.0.0.1 is archaic.
2. You need to read more carefully the documentation or otherwise enhance your knowledge. Training is useful for this. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
adubya |
Posted: Mon Feb 25, 2013 6:56 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011 Posts: 377 Location: GU12, UK
|
lancelotlinc wrote: |
2. You need to read more carefully the documentation or otherwise enhance your knowledge. Training is useful for this. |
Harsh, seems to me the OP has followed the correct steps. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Feb 25, 2013 7:00 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
adubya wrote: |
lancelotlinc wrote: |
2. You need to read more carefully the documentation or otherwise enhance your knowledge. Training is useful for this. |
Harsh, seems to me the OP has followed the correct steps. |
Obviously not since we know that database connections work from recent fixpacks (7.0.0.5). If his does not work, his unwillingness to update his toolkit and runtime demonstrate a lack of knowledge about why fixpacks exist. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
adubya |
Posted: Mon Feb 25, 2013 7:03 am Post subject: |
|
|
Partisan
Joined: 25 Aug 2011 Posts: 377 Location: GU12, UK
|
Unwillingness ? The OP's hardly had a chance to speak!  |
|
Back to top |
|
 |
Vitor |
Posted: Mon Feb 25, 2013 7:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
lancelotlinc wrote: |
1. You need to update your toolkit and runtime. 7.0.0.1 is archaic. |
Possiblly, but not directly related to the problem I think.
lancelotlinc wrote: |
2. You need to read more carefully the documentation or otherwise enhance your knowledge. Training is useful for this. |
Which part of the documentation do you feel needs reviewing? The OP appears to have established a working datasource, or at least one which the mqsicvp command is happy with (and the OP has sufficient knowledge to use mqsicvp).
ghoshly wrote: |
I am facing the data source error as "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified" when trying to access Oracle database from compute node through odbc DSN. Please help me to find the step I am missing |
If you can get a pass from mqsicvp I doubt you're missing a step in the set up. It sounds more like there's a flow issue. Are you convinced that the Compute node is correctly configured and the ESQL likewise? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Feb 25, 2013 7:06 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Vitor wrote: |
If you can get a pass from mqsicvp I doubt you're missing a step in the set up. It sounds more like there's a flow issue. Are you convinced that the Compute node is correctly configured and the ESQL likewise? |
There is an error message associated with the Compute node failure, which has not been investigated or posted. What is that error message (ie. the one underneath the default driver error)? The documentation clearly calls out steps for troubleshooting. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
Vitor |
Posted: Mon Feb 25, 2013 7:07 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
lancelotlinc wrote: |
Obviously not since we know that database connections work from recent fixpacks (7.0.0.5). If his does not work, his unwillingness to update his toolkit and runtime demonstrate a lack of knowledge about why fixpacks exist. |
Bad drive to work this morning?
Dial it down a notch. Not all the posters here spend their lives sitting on the forum waiting for a response, or leap here directly they get an email saying there's a response.
Give the OP a chance. And offer something more constructive than "get training" or "update". The OP is clearly sufficiently trained to use mqsicvp and the 7.0.0.1 version in use has a demonstratably working ODBC.
I conceed that 7.0.0.1 is below the GA version and should be updated, but you can't just knee jerk updating or training as the answer to all queries.
Sorry, my bad, you can..... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Feb 25, 2013 7:11 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Hint: mqsicvp runs under the user id of the invoker. This may succeed while an equivalent call from the Compute node will fail because the user context of the mqsicvp command is not the same as the user context of the WMB runtime. The WMB runtime should not run in SYSTEM context, but in a service Id that has had the Prepare MQ Wizard run to enable it. The Prepare MQ wizard is needed, not because of the use of MQ, but because the WMB runtime needs to query Active Directory to obtain the user profile, and running the Prepare MQ Wizard enables this (you must be prepared to re-run this utility every time the Windows password expires for this account). Also, the DSN must be a SYSTEM dsn not user-context dsn.
These facts are discussed at length in the Installation Guide.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbh45500_.htm
Many users of WMB skip past the section that talks about preparing the system for use. They go right to unpacking and installing the files without following the step-by-step instructions.
My statement above is not unreasonable and I repeat it here:
2. You need to read more carefully the documentation or otherwise enhance your knowledge. Training is useful for this.
Knowing that a preparation to a system is needed is essential. Skipping the steps needed to prepare the system renders any attempt to fix the situation pointless.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbh26033_.htm
http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbh25910_.htm
Quote: |
Required: Make sure that you have access to the product documentation that you need for installation. |
Quote: |
Required: Prepare each computer on which you are installing one or more components. |
Quote: |
Required: Make sure that you have acquired the product packages that you need for installation. For instructions about downloading and applying service updates, see Applying service. |
If we want to have a discussion on how the documentation can be made more clear, concise and understandable by new users, that may be something we can talk about. The InfoCentre's style is to have many small short subjects with links to other small short subjects (non-linear). What people may be more used to with regard to initial product configuration is a PDF file that is more linear in it's presentation of step-by-step instructions. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mgk |
Posted: Mon Feb 25, 2013 1:30 pm Post subject: |
|
|
 Padawan
Joined: 31 Jul 2003 Posts: 1642
|
Quote: |
The WMB runtime should not run in SYSTEM context, but in a service Id that has had the Prepare MQ Wizard run to enable it. |
Actually the LocalSystem account has been fully supported from 7.0.0.0
Quote: |
The Prepare MQ wizard is needed, not because of the use of MQ, but because the WMB runtime needs to query Active Directory to obtain the user profile, and running the Prepare MQ Wizard enables this (you must be prepared to re-run this utility every time the Windows password expires for this account). |
Where is this documented as it sounds a little like urban myth to me?
Quote: |
Also, the DSN must be a SYSTEM dsn not user-context dsn. |
Indeed, this is the most likely cause in this case, given the info so far...
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 |
|
 |
ghoshly |
Posted: Tue Feb 26, 2013 12:03 am Post subject: sorry...sorry...sorry |
|
|
Partisan
Joined: 10 Jan 2008 Posts: 333
|
I am sorry for replying late.. working in odd indian hours..
Neither any wrong doing was there in compute node / esql.
and yes, by mistake instead of system DSN, a user DSN was created and hence was not working.
Corrected now and working as ever from earliest version I believe.
Thanks again for responses. |
|
Back to top |
|
 |
|