| Author |
Message
|
| protocol |
 Posted: Wed Sep 01, 2010 5:20 am Post subject: WMQI 5 - Error connecting to SQLServer |
 |
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hello,
We are using WMQI v5, CSD 09.
I am trying to connect to the SQLServer DB from my Compute Node.
This is what I have in the "Data Source" property of this node - MLDB.
This is what I have in the .odbc.ini:
MLDB=DataDirect 5.0 SQL Server Wire Protocol
[MLDB]
Driver=/usr/opt/mqsi/merant50/lib/UKmsss20.so
Description=DataDirect 5.0 SQL Server Wire Protocol
Address=GA500VD,1433
Database=D_Extract
AnsiNPW=Yes
QuotedId=No
This is the exception that I am getting:
<DatabaseException>
<File>/build/S500_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>377</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Text>Child SQL exception</Text>
<Catalog>BIPv500</Catalog>
<Severity>3</Severity>
<Number>2322</Number>
<Insert>
<Type>5</Type>
<Text>IM003</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>80</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text>Specified driver could not be loaded</Text>
</Insert>
</DatabaseException>
</DatabaseException>
In the degug perspective, I see that this is happening before it enters the Compute node.
We have issued the mqsisetdbparms and followed the recommended steps. Not sure what is causing this exception. I have done a search before posting this, but did not see anything that applies to my issue.
Any help would be greatly appreciated.
Thanks in advance! |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Sep 01, 2010 5:37 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
is this version supported by Broker ? 
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| protocol |
| Posted: Wed Sep 01, 2010 7:08 am Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
There was something wrong in the ODBC.INI file, we corrected it.
We are now getting this error:
<DatabaseException>
<File>/build/S500_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>377</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Text>Child SQL exception</Text>
<Catalog>BIPv500</Catalog>
<Severity>3</Severity>
<Number>2322</Number>
<Insert>
<Type>5</Type>
<Text>S1000</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>11</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text></Text>
</Insert>
</DatabaseException>
<DatabaseException>
<File>/build/S500_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>377</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Text>Child SQL exception</Text>
<Catalog>BIPv500</Catalog>
<Severity>3</Severity>
<Number>2322</Number>
<Insert>
<Type>5</Type>
<Text>IM006</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>0</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text>[DataDirect][ODBC lib] Driver's SQLSetConnectAttr failed</Text>
</Insert>
</DatabaseException>
<DatabaseException>
<File>/build/S500_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>377</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Text>Child SQL exception</Text>
<Catalog>BIPv500</Catalog>
<Severity>3</Severity>
<Number>2322</Number>
<Insert>
<Type>5</Type>
<Text>01000</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>364</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text>The driver returned invalid (or failed to return) SQL_DRIVER_ODBC_VER: </Text>
</Insert>
</DatabaseException>
<DatabaseException>
<File>/build/S500_P/src/DataFlowEngine/ImbOdbc.cpp</File>
<Line>377</Line>
<Function>ImbOdbcHandle::checkRcInner</Function>
<Type></Type>
<Name></Name>
<Label></Label>
<Text>Child SQL exception</Text>
<Catalog>BIPv500</Catalog>
<Severity>3</Severity>
<Number>2322</Number>
<Insert>
<Type>5</Type>
<Text>p</Text>
</Insert>
<Insert>
<Type>2</Type>
<Text>11</Text>
</Insert>
<Insert>
<Type>5</Type>
<Text></Text>
</Insert>
</DatabaseException>
</DatabaseException>
</RecoverableException>
Per the infocenter, Broker supports SQLServer 2000 and that's what we are using. |
|
| Back to top |
|
|
| rbicheno |
| Posted: Wed Sep 01, 2010 7:12 am Post subject: |
|
|
Apprentice
Joined: 07 Jul 2009
Posts: 43
|
|
| Back to top |
|
|
| protocol |
| Posted: Fri Sep 03, 2010 9:34 am Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
I was able to fix this.
It looks like Message Broker by default looks only at /opt/mqsi/merant and the Data Direct 5 drivers are in /opt/mqsi/merant50.
We had to mv /merant to /merant41 and create a link from merant to merant50.
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/topic/com.ibm.etools.mft.fp8.doc/ah14446_.htm
I have one question here:
We have other projects that are using /merant (Data Direct 4.1). Is there anyway that we can use both versions /merant and /merant50?
I can change existing applications to use /merant50 drivers, but we would need to do a regression test of all those applications, want to see if we can avoid that in anyway.
I know this version of Broker is out of support, and we having a migration project which is the planning phase, but we had to change the current application in WMB 5 to meet some regulations.
Thanks! |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Sep 03, 2010 9:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In order to meet the regulations, you should have migrated the current application to a co-existing broker on the same system.
Then you would not be concerned about using two different versions of the DataDirect drivers from the same Broker, as you would have two different brokers.
I would still recommend that you take this course - install broker 7.0 on your broker v5 server, and configure it to talk to your SQLServer, and then deploy your application that requires it there.
Then you also don't have to regression test your other applications. You just have to perform migration testing on things as you move them forward. |
|
| Back to top |
|
|
| rsk33 |
| Posted: Mon Sep 20, 2010 6:30 am Post subject: |
|
|
Centurion
Joined: 21 Aug 2006
Posts: 141
|
dear protocol
I happend to see your message. presently we are also trying to upgrade the oracle from 9i to 10G. Ours is AIX ver 5.2 ML10. The version CD Broker 5 do not create the merant50 directory for data direct 5.0 drivers. I am also not getting location or pointer the broker 5 version which creates the merant50. I have opened PMR with IBM but they never respond positively as we are asked for the service extension contract.
It is highly appreciated if you can provide me the pointer or the same merant50 folder zipped file provided if you are using the AIX. If you let me know the size of the file then you can transfer me by mail or by uploading to some website.
waiting for your response. Your help is highly appreciated.
Regards |
|
| Back to top |
|
|
| protocol |
| Posted: Wed Sep 22, 2010 2:58 pm Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
|
| Back to top |
|
|
|
|
