| Author |
Message
|
| dxbmq |
 Posted: Wed Dec 14, 2005 6:50 am Post subject: throws exeception during insert statement |
 |
|
Newbie
Joined: 08 Dec 2005
Posts: 5
|
Hi,
I am trying to execute an insert statement in the compute node but it throws an exeception :ODBC Driver does not support this function. calling oracle stored procedure works perfect.
insert statement:
INSERT INTO Database.schema_name.table_name(FIRSTNAME,PASSPORT) VALUES('dxbmq',E1234');
external database:oracle 9i (9.2.0.1.0)
WBIMB v6
I appreciate if anyone could help me !!!!!!
Thanks... |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Dec 14, 2005 7:04 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
INSERT INTO Database.schema_name.table_name(FIRSTNAME,PASSPORT) VALUES('dxbmq',E1234');
|
Did you mean:
| Code: |
INSERT INTO Database.schema_name.table_name(FIRSTNAME,PASSPORT) VALUES('dxbmq','E1234');
|
??
_________________
-wayne |
|
| Back to top |
|
|
| dxbmq |
| Posted: Wed Dec 14, 2005 7:35 am Post subject: |
|
|
Newbie
Joined: 08 Dec 2005
Posts: 5
|
yes wschutz.
is anything missing ? |
|
| Back to top |
|
|
| dxbmq |
| Posted: Wed Dec 14, 2005 7:47 am Post subject: |
|
|
Newbie
Joined: 08 Dec 2005
Posts: 5
|
this is the actual code :
INSERT INTO Database.DOIUSR.TAB1(FIRSTNAME,PASSPORT) VALUES('dxbmq','E1234');
schema_name:DOIUSR
table_name: TAB1
and find few warnings :
Unresolvable table reference "Database.DOIUSR.TAB1
Unresolvable table reference "FIRSTNAME"
Unresolvable table reference "PASSPORT" |
|
| Back to top |
|
|
| JT |
| Posted: Wed Dec 14, 2005 11:29 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
What database driver are you using?
Post the contents of the .odbc.ini file. |
|
| Back to top |
|
|
| dxbmq |
| Posted: Thu Dec 15, 2005 12:29 am Post subject: |
|
|
Newbie
Joined: 08 Dec 2005
Posts: 5
|
Hi ,
am using
"MQSeries DataDirect Technologies 5.0 32-BIT Oracle (32 bit)" driver
also please find the ODBC.INI file contents below :
[ODBC 32 bit Data Sources]
MQIS=SQL Server (32 bit)
RESERVDB=IBM DB2 ODBC DRIVER (32 bit)
DEFBKDB6=IBM DB2 ODBC DRIVER (32 bit)
DNRDBKDB=IBM DB2 ODBC DRIVER (32 bit)
TESTDB=IBM DB2 ODBC DRIVER (32 bit)
DBAORA=MQSeries DataDirect Technologies 5.0 32-BIT Oracle (32 bit)
[MQIS]
Driver32=C:\WINNT\System32\SQLSRV32.dll
[RESERVDB]
Driver32=C:\IBM\SQLLIB\BIN\DB2CLI.DLL
[DEFBKDB6]
Driver32=C:\IBM\SQLLIB\BIN\DB2CLI.DLL
[DBAORA]
Driver32=C:\IBM\WMB6\bin\UKOR820.DLL
-------------------------------------------------------------------------------------
DBAORA is the oracle data source name.
thanks.. |
|
| Back to top |
|
|
| dxbmq |
| Posted: Thu Dec 15, 2005 4:27 am Post subject: |
|
|
Newbie
Joined: 08 Dec 2005
Posts: 5
|
Thanks everyone ......
My problem is solved.
Its not a ODBC driver problem though it throws an exception saying "ODBC driver doesnot support this function" please find the solution given by Robert.
also note: mentioning wrong data source name in the node properties will also result to the same exeception.
Robert wrote
| Quote: |
I found a quicker way to remove the database warnings.
1- From the Data perspective create the Database and Schema.
2- From the Broker Application Development perspective, create a Message Flow Mapping file (even if you don't intend to use any) that refers to your Database/schema.
3- In the Target Mapping section, <right> <click> and select "Add RDB Table Mapping Output"...
And presto! Your Database warnings are gone from your sample message flows without having to define each table/columns...
|
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 15, 2005 4:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Please understand that there is a significant difference between a "warning in the toolkit" and an "exception".
If you had been clear that you were dealing with warnings from the toolkit, you would have gotten the right answer quickly.
You talked about an "exception".
Exceptions are runtime errors. Warnings in the toolkit are compile time errors - and this one could have been ignored!
Of course, nobody asked for more information about the exception, which might have helped us understand that you were talking about a compiletime error rather than a runtime error.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
