| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Database Exception |
« View previous topic :: View next topic » |
| Author |
Message
|
| sraghukumar |
 Posted: Fri Mar 04, 2011 8:20 am Post subject: Database Exception |
 |
|
Apprentice
Joined: 15 Feb 2011
Posts: 49
|
Hi there!
i am stuck with this error message " Text:CHARACTER:[Microsoft][ODBC Driver Manager] Driver does not support this function"
i am trying to Insert value to Oracle Database using ESQL code, but i get this error, can any one help me.
I am using
Broker 7, Orical DB 11g, using ODBC, on Windows 7.
javascript:emoticon(' ') |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Mar 04, 2011 8:31 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Please show us the other error messages that are generated at the same time this error happens.
also the past part of the mqsicvp command used on the ODBC connection.
_________________
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 |
|
|
| sraghukumar |
| Posted: Fri Mar 04, 2011 10:15 am Post subject: Database Exception |
|
|
Apprentice
Joined: 15 Feb 2011
Posts: 49
|
Thank you for your response.
the error message which is "Text:CHARACTER:[Microsoft][ODBC Driver Manager] Driver does not support this function"
Here is the mqsicvp result on my broker and corresponding data source.
Let me know is there any inflammation i can share with you.
C:\Install\IBM\MQSI\7.0>mqsicvp MB7BROKER -n BRKXREF
BIP8270I: Connected to Datasource 'BRKXREF' as user 'HR'. The datasource platfor
m is 'Oracle', version '10.02.0000 Oracle 10.2.0.1.0'.
===========================
databaseProviderVersion = 10.02.0000 Oracle 10.2.0.1.0
driverVersion = 06.00.0165 (B0122, U0054)
driverOdbcVersion = 03.52
driverManagerVersion = 03.80.7601.0000
driverManagerOdbcVersion = 03.80.0000
databaseProviderName = Oracle
datasourceServerName = IMS04510.Ultramatics.local
databaseName = N/A
odbcDatasourceName = BRKXREF
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 'BRKXREF' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, I
NTERVAL, CLOB, BLOB' Unsupported functions: 'ACOS, ASIN, ATAN, ATAN2, COT, DEGRE
ES, 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. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Mar 04, 2011 10:20 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
And the other error messages?
Take a user trace of the errant flow.
Edit the output and just post the 3 or more errors that will be in the file.
There will be hints on what is going wrong.
Also the SQL of the operation that you are trying to perform.
_________________
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 |
|
|
| sraghukumar |
| Posted: Fri Mar 04, 2011 10:40 am Post subject: Database Exception |
|
|
Apprentice
Joined: 15 Feb 2011
Posts: 49
|
This is my Error, message,
----------------------------------------------------------------------------
( MB7BROKER.EG ) ('com.verizon.mb.commons.MF_ExceptionProcessor_ProcessException.Main', '11.3') Error detected whilst executing the SQL statement ''insertExceptionDetails();''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
( MB7BROKER.EG ) Error detected whilst executing the function or procedure ''insertExceptionDetails''.
The message broker detected an error whilst executing the function or procedure ''insertExceptionDetails''. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
( MB7BROKER.EG ) ('com.verizon.mb.commons.MF_ExceptionProcessor_ProcessException.insertExceptionDetails', '17.3') Error detected whilst executing the SQL statement ''INSERT INTO Database.EXCEPTION_DETAILS ( INTERFACE_NAME, EG_NAME, COMPONENT_NAME, SEVERITY, EXCEPTION_TYPE, CATALOG, CODE, APP_SPECIFIC_CODE, EXCEPTION_MESSAGE ) VALUES (COALESCE(rMsgBkrInfo.nsEx:InterfaceId, 'T'), COALESCE(rMsgBkrInfo.nsEx:ExecutionGroupName, 'T'), COALESCE(rMsgBkrInfo.nsEx:ComponentName, 'T'), COALESCE(rInMsgTree.nsEx:Severity, rExceptionDetail.Severity, 'T'), COALESCE(rInMsgTree.nsEx:Type, rExceptionDetail.Type, 'T'), COALESCE(rInMsgTree.nsEx:Catalog, rExceptionDetail.Catalog, 'T'), COALESCE(rInMsgTree.nsEx:Code, rExceptionDetail.Code, 'T'), COALESCE(rInMsgTree.nsEx:ApplicationSpecificCode, rExceptionDetail.ApplicationSpecificCode, 'T'), COALESCE(rInMsgTree.nsEx:Description, rExceptionDetail.Description, 'T') ) ''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
( MB7BROKER.EG ) Database error: ODBC return code '-1' using ODBC driver manager ''odbc32.dll''.
The message broker encountered an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database concerning this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect datasource or table names. Correct either the database or message broker configuration.
( MB7BROKER.EG ) Database error: SQL State ''IM001''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Driver does not support this function''.
The error has the following diagnostic information: SQL State ''IM001'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Driver does not support this function''
This message may be accompanied by other messages describing the effect on the message broker itself. Use the reason identified in this message with the accompanying messages to determine the cause of the error.
--------------------------------------------------------------------------
This is my Insert statement.
----------------------------------------------------------------------------------
INSERT INTO Database.EXCEPTION_DETAILS(INTERFACE_NAME,EG_NAME,COMPONENT_NAME,SEVERITY,EXCEPTION_TYPE,CATALOG,
CODE,APP_SPECIFIC_CODE,EXCEPTION_MESSAGE)
VALUES (COALESCE(rMsgBkrInfo.nsEx:InterfaceId,'T'),COALESCE(rMsgBkrInfo.nsEx:ExecutionGroupName,'T'),
COALESCE(rMsgBkrInfo.nsEx:ComponentName,'T'),
COALESCE(rInMsgTree.nsEx:Severity,rExceptionDetail.Severity,'T'),COALESCE(rInMsgTree.nsEx:Type,rExceptionDetail.Type,'T'),
COALESCE(rInMsgTree.nsEx:Catalog,rExceptionDetail.Catalog,'T'),COALESCE(rInMsgTree.nsEx:Code,rExceptionDetail.Code,'T'),
COALESCE(rInMsgTree.nsEx:ApplicationSpecificCode,rExceptionDetail.ApplicationSpecificCode,'T'),COALESCE(rInMsgTree.nsEx:Description,rExceptionDetail.Description,'T'));
END;
------------------------------------------------------------------- |
|
| Back to top |
|
|
| bsiggers |
| Posted: Fri Mar 04, 2011 11:10 am Post subject: |
|
|
Acolyte
Joined: 09 Dec 2010
Posts: 53
Location: Vancouver, BC
|
Well, looks like it doesn't support the COALESCE
| Quote: |
BIP8273I: The following datatypes and functions are not natively supported by da
tasource 'BRKXREF' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, I
NTERVAL, CLOB, BLOB' Unsupported functions: 'ACOS, ASIN, ATAN, ATAN2, COT, DEGRE
ES, 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. |
You may have to make your INSERT a bit more complicated and potentially use nested NVLs instead, which is a bit irritating, but should work. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Mar 04, 2011 11:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I read it as the datasource is not set up correctly.
The ESQL INSERT should be processing those COALESCE statements, not passing them to the databse.
But even if it were passing them to the database, there should be more specific information about the database itself in the error messages - like which ODBC driver is in use in the first place. |
|
| Back to top |
|
|
| bsiggers |
| Posted: Fri Mar 04, 2011 11:35 am Post subject: |
|
|
Acolyte
Joined: 09 Dec 2010
Posts: 53
Location: Vancouver, BC
|
You are correct - I should probably start reading my own quotes.
 |
|
| Back to top |
|
|
| sraghukumar |
| Posted: Fri Mar 04, 2011 1:31 pm Post subject: Database Exception |
|
|
Apprentice
Joined: 15 Feb 2011
Posts: 49
|
Thank you for your response guys,
So what do you guys suggest me to do, Do i need to change the insert quires ? |
|
| Back to top |
|
|
| mgk |
| Posted: Fri Mar 04, 2011 1:47 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Have you checked the "Enable SQLDescribeParam" checkbox for the ODBC Datasource?
_________________
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 |
|
|
| sraghukumar |
| Posted: Fri Mar 04, 2011 2:14 pm Post subject: Database Exception |
|
|
Apprentice
Joined: 15 Feb 2011
Posts: 49
|
Hi guys,
thank you for your response. after enabling "Enable SQLDescribeParam" it insertion went through, but i got one more error, that is because of my SQL statement,
You guys are awesome. Thank you again.
Rag |
|
| Back to top |
|
|
| Gama |
| Posted: Thu May 31, 2012 8:13 am Post subject: |
|
|
Centurion
Joined: 11 Jan 2005
Posts: 103
Location: Portugal
|
| mgk wrote: |
| Have you checked the "Enable SQLDescribeParam" checkbox for the ODBC Datasource? |
Thanks mgk, I had the same problem with WMB8 using ORACLE Data Direct x64 driver.
Many thanks, |
|
| Back to top |
|
|
| kiruthigeshwar |
| Posted: Fri Nov 02, 2012 2:44 am Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012
Posts: 50
|
| mgk wrote: |
| Have you checked the "Enable SQLDescribeParam" checkbox for the ODBC Datasource? |
Thanks guys. I had the same issue. It worked now after enabling SQLDescribeParam |
|
| Back to top |
|
|
| shahid78 |
| Posted: Mon Dec 10, 2012 11:25 pm Post subject: Thanks, It worked |
|
|
Newbie
Joined: 10 Dec 2012
Posts: 1
|
| Thanks guys. I had the same issue. It worked now after enabling SQLDescribeParam in DSN settings. |
|
| Back to top |
|
|
| sarasu |
| Posted: Thu Feb 07, 2013 1:35 pm Post subject: |
|
|
Master
Joined: 02 Feb 2006
Posts: 229
|
Hi All,
Is there a similar setting for SQL Server as well ?
If yes, where should I find this option for SQL Server configuration ?
Please advise.
I am getting the same error when I configure the SQL Server DB as below.
BIP8273I: The following datatypes and functions are not natively supported by datasource 'DEVDBDS' using this O
DBC driver: Unsupported datatypes: 'DATE, TIME, INTERVAL, CLOB, BLOB' Unsupported functions: 'POSITION, BETWEEN, IN, LIK
E'
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 Br
oker rather than being processed by the database provider.
Note that "functions" within this message can refer to functions or predicates.
BIP8071I: Successful command completion.
Last edited by sarasu on Mon Feb 11, 2013 6:48 am; edited 1 time in total |
|
| Back to top |
|
|
|
|
|
  |
Goto page 1, 2 Next |
Page 1 of 2 |
|
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
|
|
|
|
