Author |
Message
|
kiruthigeshwar |
Posted: Wed Oct 31, 2012 9:42 pm Post subject: Remote Oracle ODBC Acces Fails |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
Hi All,
I have Broker installed in my local system. While I have to access to access an oracle Db running in a remote machine. I created system DSN to that database and connection test was successful. But when I access the datasource from my flow (in my code I access it from java compute node using MbSQLStatement). It isn't working. I get the following error
-----------------
( QRBROKER.new ) Database error: SQL State ''IM006''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed''.
The error has the following diagnostic information: SQL State ''IM006'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed''
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.
------------------------
Thanks & Regards,
Eshwar |
|
Back to top |
|
 |
kiruthigeshwar |
Posted: Wed Oct 31, 2012 9:45 pm Post subject: Re: Remote Oracle ODBC Acces Fails |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
kiruthigeshwar wrote: |
Hi All,
I have Broker installed in my local system. While I have to access to access an oracle Db running in a remote machine. I created system DSN to that database and connection test was successful. But when I access the datasource from my flow (in my code I access it from java compute node using MbSQLStatement). It isn't working. I get the following error
-----------------
( QRBROKER.new ) Database error: SQL State ''IM006''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed''.
The error has the following diagnostic information: SQL State ''IM006'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed''
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.
------------------------
Thanks & Regards,
Eshwar |
This is the error I get in flow : Specified driver could not be loaded due to system error 126 (Oracle in OraDb10g_home1). |
|
Back to top |
|
 |
mqsiuser |
Posted: Wed Oct 31, 2012 11:21 pm Post subject: Re: Remote Oracle ODBC Acces Fails |
|
|
 Yatiri
Joined: 15 Apr 2008 Posts: 637 Location: Germany
|
ODBC --> ESQL (Execgroups / C / C++)
JDBC --> JCN - Java Compute Node (JVM / Java)
afaik there is no mixing allowed
You should carefully read and follow the instructions in the infocenter _________________ Just use REFERENCEs |
|
Back to top |
|
 |
kiruthigeshwar |
Posted: Wed Oct 31, 2012 11:30 pm Post subject: Re: Remote Oracle ODBC Acces Fails |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
mqsiuser wrote: |
ODBC --> ESQL (Execgroups / C / C++)
JDBC --> JCN - Java Compute Node (JVM / Java)
afaik there is no mixing allowed
You should carefully read and follow the instructions in the infocenter |
Hi , Thank you for the response.
I was getting the
Specified driver could not be loaded due to system error 126 (Oracle in OraDb10g_home1). error because Oracle I installed crashed. I re installed it and I tried the same with ESQL. The actual error am getting is
[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
When I tried to hit the local database, it works fine. This happens only with the remote database. Moreover connection test also ends successfully. |
|
Back to top |
|
 |
mqsiuser |
Posted: Thu Nov 01, 2012 12:09 am Post subject: Re: Remote Oracle ODBC Acces Fails |
|
|
 Yatiri
Joined: 15 Apr 2008 Posts: 637 Location: Germany
|
if you test it in the windows datasources (and it works), then it should also in your flow.
for a remote db you (additionally to a lokal db) need a (oracle) db client installed and I think an "ora.tns" file.
And... honestly... one of the checkboxes (in the windows "ORCL" datasource) must be changed/toggeled (from its default). |
|
Back to top |
|
 |
kiruthigeshwar |
Posted: Thu Nov 01, 2012 1:21 am Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
You mean tnsnames.ora. Yeah the DSN am using is oracle. The entryis
Quote: |
ORACLE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.100.13)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = oracle)
)
)
|
I forgot to do mqsisetdbparams. I used
mqsisetdbparms QRBROKER -n oracle -u <username> -p <password>.
After I did this the exception ma getting is : [Oracle][ODBC]Optional feature not implemented Below is the trace entry.
Quote: |
(
(0x01000000):RecoverableException = (
(0x03000000):File = 'F:\build\S000_P\src\DataFlowEngine\ImbDataFlowNode.cpp'
(0x03000000):Line = 739
(0x03000000):Function = 'ImbDataFlowNode::createExceptionList'
(0x03000000):Type = 'ComIbmComputeNode'
(0x03000000):Name = 'JavaComputeNodeMessageFlow#FCMComposite_1_7'
(0x03000000):Label = 'JavaComputeNodeMessageFlow.DB_STORE'
(0x03000000):Catalog = 'BIPv610'
(0x03000000):Severity = 3
(0x03000000):Number = 2230
(0x03000000):Text = 'Node throwing exception'
(0x01000000):DatabaseException = (
(0x03000000):File = 'F:\build\S000_P\src\DataFlowEngine\ImbOdbc.cpp'
(0x03000000):Line = 230
(0x03000000):Function = 'ImbOdbcHandle::checkRcInner'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv610'
(0x03000000):Severity = 3
(0x03000000):Number = 2321
(0x03000000):Text = 'Root SQL exception'
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '-1'
)
(0x01000000):DatabaseException = (
(0x03000000):File = 'F:\build\S000_P\src\DataFlowEngine\ImbOdbc.cpp'
(0x03000000):Line = 359
(0x03000000):Function = 'ImbOdbcHandle::checkRcInner'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv610'
(0x03000000):Severity = 3
(0x03000000):Number = 2322
(0x03000000):Text = 'Child SQL exception'
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = 'HYC00'
)
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '0'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = '[Oracle][ODBC]Optional feature not implemented.'
)
)
)
)
)
|
.  |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Nov 01, 2012 1:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You don't actually need a tnsnames.ora file with modern DataDirect Drivers that come with modern versions of Broker.
The 'optional feature not implemented' message almost certainly means that you have failed to follow the instructions in the infocenter for properly configuring the DSN and have decided on your own to use something other than the DataDirect drivers.
Go back to the info center. Read the documentation on configuring an Oracle DSN carefully. Follow the documentation on configuring an Oracle DSN twice as carefully. |
|
Back to top |
|
 |
mqsiuser |
Posted: Thu Nov 01, 2012 1:29 am Post subject: |
|
|
 Yatiri
Joined: 15 Apr 2008 Posts: 637 Location: Germany
|
kiruthigeshwar wrote: |
(0x03000000):Text = '[Oracle][ODBC]Optional feature not implemented.' |
I know the error... go to the (windows) data source and check/uncheck a checkbox which enables / disables the "feature" !
Is there a checkbox like "allow passthru" or something like that ? _________________ Just use REFERENCEs |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Nov 01, 2012 1:40 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Read Jeff's post again (very carefully), then follow it.
And remember that the broker does not support the native Oracle drivers.  _________________ MQ & Broker admin |
|
Back to top |
|
 |
mqsiuser |
Posted: Thu Nov 01, 2012 1:57 am Post subject: |
|
|
 Yatiri
Joined: 15 Apr 2008 Posts: 637 Location: Germany
|
|
Back to top |
|
 |
kiruthigeshwar |
Posted: Thu Nov 01, 2012 2:32 am Post subject: |
|
|
Acolyte
Joined: 31 Oct 2012 Posts: 50
|
Thank you everyone for your response.
Initially I used Microsoft ODBC for Oracle while creating System DSN. Then I tried the Data Direct driver that comes with MQSeries : MQSeries Data Direct Technologies 5.2 32-BIT Oracle.
Then it worked.  |
|
Back to top |
|
 |
mqsiuser |
Posted: Fri Nov 02, 2012 4:04 am Post subject: Re: Remote Oracle ODBC Acces Fails |
|
|
 Yatiri
Joined: 15 Apr 2008 Posts: 637 Location: Germany
|
just to clarify something:
mqsiuser wrote: |
And... honestly... one of the checkboxes (in the windows "ORCL" datasource) must be changed/toggeled (from its default). |
mqsiuser wrote: |
I know the error... go to the (windows) data source and check/uncheck a checkbox which enables / disables the "feature" !
|
I confused this error message ("Optional feature not implemented.") with "Driver does not support this function".
sorry  _________________ Just use REFERENCEs |
|
Back to top |
|
 |
|