| Author |
Message
|
| wmqiadmin |
 Posted: Tue Apr 11, 2006 10:27 am Post subject: ODBC errors |
 |
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
Hi Friends,
I am working with V6 message broker, config manager and toolkit with oracle database.
We have brokers database on the oracle server and created another one for logging flow on the same server. I am trying to insert data in new database table for this logging flow and getting this error.
| Quote: |
Text = [Microsoft][ODBC Driver Manager] Driver does not support this function
|
ODBC connections are all set and tested they are working fine, i have issued mqsisetdbparms cmd also but still i am unable to insert the data to the database.
| Quote: |
mqsisetdbparms--brokername-- -n --DataSourceName------------->
>-- -u --DataSourceUserId-- -p --DataSourcePassword------------><
|
Thanks in advance for your help. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Apr 11, 2006 11:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What driver are you using for the ODBC data source? It should be *the same* as the one you are using for the broker database.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Apr 11, 2006 11:49 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
| jefflowrey wrote: |
| What driver are you using for the ODBC data source? It should be *the same* as the one you are using for the broker database. |
yup they are same
"MQSeries data direct technologies 5.0 32 bit oracle" |
|
| Back to top |
|
|
| JT |
| Posted: Tue Apr 11, 2006 12:13 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
yup they are same
"MQSeries data direct technologies 5.0 32 bit "oracle" |
| Quote: |
Quote:
Text = [Microsoft][ODBC Driver Manager] Driver does not support this function |
Unless things have changed in v6, these seem to conflict. |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Tue Apr 11, 2006 12:32 pm Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
We have check the ODBC connection, i am able to login to the database using the SQL plus.
I have given insert, update, delete access to both the DataSourceUserId and ServiceUserID on this data source, but still i am unable to connect to the database. Getting the same error. |
|
| Back to top |
|
|
| fschofer |
| Posted: Tue Apr 11, 2006 1:14 pm Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
can you please post the ESQL statements your are using for the insert.
Additional run a trace with debug level of the ESQL execution and post this also.
Greetings
Frank |
|
| Back to top |
|
|
| dipankar |
| Posted: Tue Apr 11, 2006 7:51 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi wmqiadmin,
Have you checked Enable SQLDescribeParam box? This parameter is on the Advanced tab of the driver settings.
_________________
Regards |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Wed Apr 12, 2006 5:20 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
| fschofer wrote: |
Hi,
can you please post the ESQL statements your are using for the insert.
Additional run a trace with debug level of the ESQL execution and post this also.
Greetings
Frank |
INSERT INTO Database.table1 (BUSINESS_ID) VALUES ('1234567890');
I tried with
INSERT INTO Database.Schema.table1 (BUSINESS_ID) VALUES ('1234567890');
Gives the same exception
Dipankar:
I will check that with the database guys will post the result,
frank
I'll try the trace node.
Thanks guys |
|
| Back to top |
|
|
| fschofer |
| Posted: Wed Apr 12, 2006 5:39 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
i am not talking about the trace node, i talk about a trace with debug level.
I always wonder why nearly no one uses this features which is excellent for finding errors, especially ESQL ones.
To turn on 'debug' trace for your message flow
=> mqsichangetrace <BR name> -u -e <EG name> -f <Flow name> -l debug -r -c 5000
Put a message to your input queue
Read the trace
=> mqsireadlog <BR name> -u -e <EG name> -f -o log.xml
=> mqsiformatlog -i log.xml -o log.txt
Greetings
Frank |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Wed Apr 12, 2006 8:10 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
| fschofer wrote: |
Hi,
i am not talking about the trace node, i talk about a trace with debug level.
I always wonder why nearly no one uses this features which is excellent for finding errors, especially ESQL ones.
To turn on 'debug' trace for your message flow
=> mqsichangetrace <BR name> -u -e <EG name> -f <Flow name> -l debug -r -c 5000
Put a message to your input queue
Read the trace
=> mqsireadlog <BR name> -u -e <EG name> -f -o log.xml
=> mqsiformatlog -i log.xml -o log.txt
Greetings
Frank |
Hi Frank,
This is what the log file says:
| Quote: |
The try-catch node 'DATABASE_MF.TryCatch' has caught an exception which occurred in a node connected to its try terminal. The message has been augmented with an exception list and is propagating it to any nodes connected to its catch terminal for further processing. See the following messages for details of the exception list.
No user action required.
2006-04-12 12:04:03.513000 4468 RecoverableException BIP2230E: Error detected whilst processing a message in node 'DATABASE_MF.database'.
The message broker detected an error whilst processing a message in node 'DATABASE_MF.database'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2006-04-12 12:04:03.513000 4468 RecoverableException BIP2488E: ('.Database.Main', '4.3') Error detected whilst executing the SQL statement ''CopyEntireMessage();''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2006-04-12 12:04:03.513000 4468 RecoverableException BIP2934E: Error detected whilst executing the function or procedure ''CopyEntireMessage''.
The message broker detected an error whilst executing the function or procedure ''CopyEntireMessage''. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2006-04-12 12:04:03.513000 4468 RecoverableException BIP2488E: ('.Database.CopyEntireMessage', '23.3') Error detected whilst executing the SQL statement ''INSERT INTO Database.Schema1.Table ( BUSINESS_ID ) VALUES ('1234567890' ) ''.
The message broker detected an error whilst executing the given statement. An exception has been thrown to cut short the SQL program.
See the following messages for details of the error.
2006-04-12 12:04:03.513000 4468 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.
2006-04-12 12:04:03.513000 4468 DatabaseException BIP2322E: Database error: SQL State ''IM001''; Native Error Code '0'; Error Text ''[Microsoft][ODBC Driver Manager] Driver does not support this function''.
The error has the following diagnostic information: SQL State ''IM001'' SQL Native Error Code '0' SQL Error Text ''[Microsoft][ODBC Driver Manager] Driver does not support this function''
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.
2006-04-12 12:04:03.513000 4468 UserTrace BIP2638I: The MQ output node 'DATABASE_MF.MQOutput1' attempted to write a message to queue ''KOUT'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2006-04-12 12:04:03.513000 4468 UserTrace BIP2622I: Message successfully output by output node 'DATABASE_MF.MQOutput1' to queue ''KOUT'' on queue manager ''''.
Threads encountered in this trace:
4468 |
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 12, 2006 8:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| JT wrote: |
| Quote: |
yup they are same
"MQSeries data direct technologies 5.0 32 bit "oracle" |
| Quote: |
Quote:
Text = [Microsoft][ODBC Driver Manager] Driver does not support this function |
Unless things have changed in v6, these seem to conflict. |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wmqiadmin |
| Posted: Wed Apr 12, 2006 9:10 am Post subject: |
|
|
Disciple
Joined: 19 Jun 2005
Posts: 163
Location: epping UK
|
| dipankar wrote: |
Hi wmqiadmin,
Have you checked Enable SQLDescribeParam box? This parameter is on the Advanced tab of the driver settings. |
Thanks dipankar,
the actual error was this only. Now broker is able to connect to the DB, Now i am wondering what exactly this cmd do? Any ways thanks alot for your help.
Thanks to all of you guys. |
|
| Back to top |
|
|
| dipankar |
| Posted: Wed Apr 12, 2006 8:03 pm Post subject: |
|
|
Disciple
Joined: 03 Feb 2005
Posts: 171
|
Hi wmqiadmin,
| Quote: |
| Now i am wondering what exactly this cmd do? |
Enable SQLDescribeParam: Select this check box to enable the SQLDescribeParam function, which results in all parameters being described with a data type of SQL_VARCHAR for Select statements. For Insert/Update/Delete statements and for stored procedures, the parameters are described as the actual Oracle data types on the Oracle server. This option must be selected to access data when using Microsoft Remote Data Objects (RDO).
_________________
Regards |
|
| Back to top |
|
|
|
|
