| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mqsicvp command |
« View previous topic :: View next topic » |
| Author |
Message
|
| vishBroker |
 Posted: Fri May 18, 2012 9:20 am Post subject: mqsicvp command |
 |
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
Hi,
When I run mqsicvp command to get details about 'DataSource', I get response like something below(nothing different here)-
-------------------------------------------------
[]$ mqsicvp DV01_BRK -n GMSDEV
BIP8270I: Connected to Datasource 'xxxx' as user 'BROKER2'. The datasource platform is 'Oracle', version '11.02.0000 Oracle 11.2.0.1.0'.
===========================
databaseProviderVersion = 11.02.0000 Oracle 11.2.0.1.0
driverVersion = 06.00.0254 (B0179, U0089)
driverOdbcVersion = 03.52
driverManagerVersion = 03.52.0002.0002
driverManagerOdbcVersion = 03.52
databaseProviderName = Oracle
datasourceServerName = x.x.x.x
databaseName = N/A
odbcDatasourceName = xxxx
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 = No
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 = N/A
binaryDatatypeName = RAW
varBinaryDatatypeName = RAW
longVarBinaryDatatypeName = BLOB
blobDatatypeName = N/A
intDatatypeName = NUMBER
doubleDatatypeName = BINARY_DOUBLE
varCharMaxLength = 0
longVarCharMaxLength = 0
clobMaxLength = 0
varBinaryMaxLength = 0
longVarBinaryMaxLength = 0
blobMaxLength = 0
timeStampMaxLength = 0
identifierCase = Upper
escapeCharacter = \
longVarCharDatatype = -1
clobDatatype = 0
longVarBinaryDatatype = -4
blobDatatype = 0
BIP8273I: The following datatypes and functions are not natively supported by datasource 'GMSDEV' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, TIMESTAMP, 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.
===========
From the output it is clear that
---
BIP8273I: The following datatypes and functions are not natively supported by datasource 'xxxx' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, TIMESTAMP, 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.
---
above dataTypes are not supported by NATIVELY this version of ODBC driver.
Well, when I call a stored procedure which have parameters with 'Date', 'timestamp' dataTypes, it runs SUCCESSFULLY.
Can anyone kindly explain how it works.
I do see that BIP code has 'I' at the end - which means information. (Misleading information-would be better choice of words).
Thanks. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri May 18, 2012 9:28 am Post subject: Re: mqsicvp command |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vishBroker wrote: |
Well, when I call a stored procedure which have parameters with 'Date', 'timestamp' dataTypes, it runs SUCCESSFULLY.
Can anyone kindly explain how it works.
|
Yes, because for those data types in the context you've used them it's possible for the code (in conjuction with the database software) to bridge the gap. This is slower than native support and doesn't work in all cases. If (for instance) you have a high volume transaction or a tight SLA knowing that may influence your design. Likewise if you call one of the unsupported functions and it fails, this gives you a clue where to start looking.
Date types in particular are notoriously held in different native formats by different software.
| vishBroker wrote: |
| I do see that BIP code has 'I' at the end - which means information. (Misleading information-would be better choice of words). |
What's misleading about it? The message says there's no native support not that it doesn't work. What would you prefer? No message at all, and when you raise a PMR about a related issue IBM responds "Psych!"?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| vishBroker |
| Posted: Fri May 18, 2012 4:17 pm Post subject: |
|
|
Centurion
Joined: 08 Dec 2010
Posts: 135
|
| Quote: |
| Yes, because for those data types in the context you've used them it's possible for the code (in conjuction with the database software) to bridge the gap. This is slower than native support and doesn't work in all cases. If (for instance) you have a high volume transaction or a tight SLA knowing that may influence your design. Likewise if you call one of the unsupported functions and it fails, this gives you a clue where to start looking. |
Thanks for info. This helps understanding, why it works.
I was wondering about what makes the trick, even if those dataTypes were not supported.
well,What I am reading/understanding is - unsupported dataTypes are converted into 'char'(string) when stored procedure calls are made and then converted to corresponding dataTypes at DB side(if supported). - kindly correct me if wrong! |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat May 19, 2012 8:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vishBroker wrote: |
| well,What I am reading/understanding is - unsupported dataTypes are converted into 'char'(string) when stored procedure calls are made and then converted to corresponding dataTypes at DB side(if supported). - kindly correct me if wrong! |
Where are you reading that? Post a link.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sat May 19, 2012 12:38 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| vishBroker wrote: |
| I was wondering about what makes the trick, even if those dataTypes were not supported. |
The trick is to read the rest of the BIP message:
| vishBroker wrote: |
BIP8273I: The following datatypes and functions are not natively supported by datasource 'GMSDEV' using this ODBC driver: Unsupported datatypes: 'DATE, TIME, TIMESTAMP, 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. ... |
|
|
| 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
|
|
|
|
