| Author |
Message
|
| broker_new |
 Posted: Fri Jun 26, 2009 12:10 pm Post subject: Data Direct Drivers |
 |
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Hi Guys,
As we know broker(WMB 6.1) is shipped with in built data direct drivers, we are interested in using the Data Direct 6.0 drivers provided by Data Direct rather than the default drivers.
We have set the ODBCINI to point to the {new drivers installation path}/odbc.ini
we are encountering the following error.
[DataDirect][ODBC lib] Specified driver could not be loaded
Did anyone passed this error?
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
 |
| broker_new |
| Posted: Sat Jun 27, 2009 7:00 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
I was reading the following lines for setting up the informix database DSN settings.
# Informix Stanza
[INFORMIXDB]
Driver=libinfWrapper64.so
Description=IBM Informix ODBC Driver
ServerName=<Your Informix Server Name>
Database=<Your Database Name>
At line 3 it says the library name but not the path of the library how does the broker know to which library to look into...For especially Oracle the complete path is mentioned in odbc64.ini sample file....why not for the other database libraries???
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Jun 27, 2009 12:11 pm Post subject: Re: Data Direct Drivers |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| broker_new wrote: |
we are interested in using the Data Direct 6.0 drivers provided by Data Direct rather than the default drivers.
|
Why? What functionality do these drivers provide that the default ones do not?
What are the support implications of not using the supplied drivers? Assuming WMB works with the other drivers at all?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| broker_new |
| Posted: Mon Jun 29, 2009 4:46 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
For setting up the DSN for oracle database it is clearly mentioned that so and so Driver is located at some location.
# Oracle stanza
[ORACLEDB]
Driver=<Your Broker install directory>/ODBC64/V5.3/lib/UKora23.so
Description=DataDirect 5.3 64bit Oracle Wire Protocol
HostName=<Your Oracle Server Machine Name>
PortNumber=<Port on which Oracle is listening on HostName>
SID=<Your Oracle SID>
CatalogOptions=0
EnableStaticCursorsForLongData=0
ApplicationUsingThreads=1
EnableDescribeParam=1
OptimizePrepare=1
WorkArounds=536870912
ProcedureRetResults=1
ColumnSizeAsCharacter=1
But for the DSN for Informix database only the library name is mentioned but not the complete path, whats the logic behind this...will the broker automatically loads the libinfWrapper64.so?
# Informix Stanza
[INFORMIXDB]
Driver=libinfWrapper64.so
Description=IBM Informix ODBC Driver
ServerName=<Your Informix Server Name>
Database=<Your Database Name> 
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| broker_new |
| Posted: Mon Jun 29, 2009 4:55 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
and here is the Exception if we are using the default ODBC drivers.
Exception Message
( ['MQROOT' : 0x11268a870]
(0x01000000):RecoverableException = (
(0x03000000):File = '/build/S610_P/src/DataFlowEngine/ImbComputeNode.cpp' (CHARACTER)
(0x03000000):Line = 464 (INTEGER)
(0x03000000):Function = 'ImbComputeNode::evaluate' (CHARACTER)
(0x03000000):Type = 'ComIbmComputeNode' (CHARACTER)
(0x03000000):Name = 'TestInformixDSN_MsgFlow#FCMComposite_1_3' (CHARACTER)
(0x03000000):Label = 'TestInformixDSN_MsgFlow.CallInformix_StoredProcedure' (CHARACTER)
(0x03000000):Catalog = 'BIPv610' (CHARACTER)
(0x03000000):Severity = 3 (INTEGER)
(0x03000000):Number = 2230 (INTEGER)
(0x03000000):Text = 'Caught exception and rethrowing' (CHARACTER)
(0x01000000):DatabaseException = (
(0x03000000):File = '/build/S610_P/src/DataFlowEngine/ImbOdbc.cpp' (CHARACTER)
(0x03000000):Line = 327 (INTEGER)
(0x03000000):Function = 'ImbOdbcHandle::checkRcInner' (CHARACTER)
(0x03000000):Type = '' (CHARACTER)
(0x03000000):Name = '' (CHARACTER)
(0x03000000):Label = '' (CHARACTER)
(0x03000000):Catalog = 'BIPv610' (CHARACTER)
(0x03000000):Severity = 3 (INTEGER)
(0x03000000):Number = 2321 (INTEGER)
(0x03000000):Text = 'Root SQL exception' (CHARACTER)
(0x01000000):Insert = (
(0x03000000):Type = 2 (INTEGER)
(0x03000000):Text = '-1' (CHARACTER)
)
(0x01000000):DatabaseException = (
(0x03000000):File = '/build/S610_P/src/DataFlowEngine/ImbOdbc.cpp' (CHARACTER)
(0x03000000):Line = 456 (INTEGER)
(0x03000000):Function = 'ImbOdbcHandle::checkRcInner' (CHARACTER)
(0x03000000):Type = '' (CHARACTER)
(0x03000000):Name = '' (CHARACTER)
(0x03000000):Label = '' (CHARACTER)
(0x03000000):Catalog = 'BIPv610' (CHARACTER)
(0x03000000):Severity = 3 (INTEGER)
(0x03000000):Number = 2322 (INTEGER)
(0x03000000):Text = 'Child SQL exception' (CHARACTER)
(0x01000000):Insert = (
(0x03000000):Type = 5 (INTEGER)
(0x01000000):Insert = (
(0x03000000):Type = 5 (INTEGER)
(0x03000000):Text = '86' (CHARACTER)
)
(0x01000000):Insert = (
(0x03000000):Type = 2 (INTEGER)
(0x03000000):Text = '0' (CHARACTER)
)
(0x01000000):Insert = (
(0x03000000):Type = 5 (INTEGER)
(0x03000000):Text = '523 84' (CHARACTER)
)
)
)
)
)
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Mon Jun 29, 2009 5:00 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Does a user trace shed any more light on the issue? |
|
| Back to top |
|
|
| broker_new |
| Posted: Mon Jun 29, 2009 5:09 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
nothing promising
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version ; formatter version 6102
Threads encountered in this trace:
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Mon Jun 29, 2009 6:04 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| broker_new wrote: |
nothing promising
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version ; formatter version 6102
Threads encountered in this trace: |
I'd have expected more than that! are you sure the trace worked? |
|
| Back to top |
|
|
| broker_new |
| Posted: Mon Jun 29, 2009 6:13 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
the output is based on this commands... 
mqsichangetrace EAIDEV01 -u -e default -f TestInformixDSN_MsgFlow -l debug -r -c 50000
mqsireadlog EAIDEV01 -u -e default -f -o TestInformixDSN_MsgFlow.xml
mqsiformatlog -i TestInformixDSN_MsgFlow.xml -o TestInformixDSN_MsgFlow.txt
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 29, 2009 6:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can't expect it to succeed to use the wrong drivers.
You don't show where, between change trace and read log, you are attempting to do the thing you're trying to trace. If you're running those two commands immediately one after the other, that's your problem.
I do not believe you will be able to make unsupported versions of DataDirect ODBC drivers function properly. |
|
| Back to top |
|
|
| broker_new |
| Posted: Mon Jun 29, 2009 7:13 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
thats true..
here is the user trace
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version 6102; formatter version 6102
2009-06-29 11:07:44.287256 6940 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'TestInformixDSN_MsgFlow.TEST_IN'.
2009-06-29 11:07:44.287568 6940 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'TestInformixDSN_MsgFlow.TEST_IN' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-06-29 11:07:44.287596 6940 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'TEST_IN' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-06-29 11:07:44.287652 6940 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'TestInformixDSN_MsgFlow.TEST_IN' to handle portion of incoming message of length '56' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2009-06-29 11:07:46.614484 6940 UserTrace BIP2231E: Error detected whilst processing a message in node 'TestInformixDSN_MsgFlow.TEST_IN'.
The message broker detected an error whilst processing a message in node 'TestInformixDSN_MsgFlow.TEST_IN'. The message has been augmented with an exception list and has been propagated to the node's failure terminal for further processing.
See the following messages for details of the error.
2009-06-29 11:07:46.614540 6940 RecoverableException BIP2230E: Error detected whilst processing a message in node 'TestInformixDSN_MsgFlow.CallInformix_StoredProcedure'.
The message broker detected an error whilst processing a message in node 'TestInformixDSN_MsgFlow.CallInformix_StoredProcedure'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-06-29 11:07:46.614548 6940 DatabaseException BIP2321E: Database error: ODBC return code '-1'.
The message broker encountered an error whilst executing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database pertaining to this error.
Use the following messages to determine the cause of the error. This is likely to be such things as incorrect datasource or table names. Then correct either the database or message broker configuration.
2009-06-29 11:07:46.614552 6940 DatabaseException BIP2322E: Database error: SQL State ''86''; Native Error Code '0'; Error Text ''523 84''.
The error has the following diagnostic information: SQL State ''86'' SQL Native Error Code '0' SQL Error Text ''523 84''
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.
2009-06-29 11:07:46.614760 6940 UserTrace BIP2540I: Node 'TestInformixDSN_MsgFlow.Test_DSN': Finished evaluating expression ''CURRENT_TIMESTAMP'' at ('', '1.60'). The result was ''TIMESTAMP '2009-06-29 11:07:46.614666'''.
2009-06-29 11:07:46.614812 6940 UserTrace BIP2539I: Node 'TestInformixDSN_MsgFlow.Test_DSN': Evaluating expression ''Root'' at ('', '3.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2009-06-29 11:07:46.615660 6940 UserTrace BIP2539I: Node 'TestInformixDSN_MsgFlow.Test_DSN': Evaluating expression ''Environment'' at ('', '5.3'). This resolved to ''Environment''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2009-06-29 11:07:46.615684 6940 UserTrace BIP2539I: Node 'TestInformixDSN_MsgFlow.Test_DSN': Evaluating expression ''ExceptionList'' at ('', '7.3'). This resolved to ''ExceptionList''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2009-06-29 11:07:46.616308 6940 UserTrace BIP4067I: Message propagated to output terminal for trace node 'TestInformixDSN_MsgFlow.Test_DSN'.
The trace node 'TestInformixDSN_MsgFlow.Test_DSN' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2009-06-29 11:07:46.616580 6940 UserTrace BIP2638I: The MQ output node 'TestInformixDSN_MsgFlow.Test_DSN_ERROR' attempted to write a message to queue ''Test_DSN_ERROR'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2009-06-29 11:07:46.616592 6940 UserTrace BIP2622I: Message successfully output by output node 'TestInformixDSN_MsgFlow.Test_DSN_ERROR' to queue ''Test_DSN_ERROR'' on queue manager ''''.
Threads encountered in this trace:
6940
| Quote: |
| You can't expect it to succeed to use the wrong drivers. |
Its the same odbc64.ini which iam using and modified the sample DSN paramaters from it.
| Quote: |
| I do not believe you will be able to make unsupported versions of DataDirect ODBC drivers function properly. |
Can we assume that the drivers provided with WMBv6.1 supports only certain databases not the informix?
_________________
IBM ->Let's build a smarter planet |
|
| Back to top |
|
|
| broker_new |
| Posted: Sun Jul 19, 2009 1:15 pm Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
After some research and opening the PMR's with IBM, realized that broker provides 64 bit drivers for Oracle, SQL server and Sybase database and if you would like use 32 bit drivers you have to install all the clients to connect to their databases...
Why there is lot of gap between the 64 and 32 bit? why broker installation doesn't provide the drivers for 32 bit? |
|
| Back to top |
|
|
|
|
