| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error in Database Node - not sure whats causing the problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| GAKD |
 Posted: Fri Jun 26, 2015 9:41 am Post subject: Error in Database Node - not sure whats causing the problem |
 |
|
Novice
Joined: 25 Jun 2015
Posts: 14
|
Below is the esql code in the DATABASE node and I have configured the DSN in the windows odbc.
------------------------------------------------------------------------------------
| Code: |
CREATE DATABASE MODULE ETS_Routing_Flow_Database
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
DECLARE NS1 namespace 'http://EFT_Test/CustomerInput';
DECLARE bons0 namespace 'http://DMAS_IRI_Mediation';
DECLARE fileId INT 0;
DECLARE currentTime CHARACTER;
SET fileId = CAST(FIELDVALUE(Root.SOAP.Body.NS1:getCustomer.input1.fileId) AS INTEGER);
--26-JUN-15 10.07.54.710000000 AM
SET currentTime = CAST(CURRENT_TIMESTAMP AS CHARACTER FORMAT 'dd-MMM-yy hh.mm.ss.SSSSSS');
IF(fileId > 0) THEN
INSERT INTO Database.TRANSACTION_STATUS_ETS(TRANSID, STATUS, ERROR_MESSAGE, STATUS_TIMESTAMP, STATUS_CD)
VALUES(fileId, "FileReceived", null, currentTime, 2);
ELSE
THROW USER EXCEPTION CATALOG 'BIPmsgs' MESSAGE 3001 VALUES('The fileId of the webService request seems to be incorrect');
END IF;
RETURN TRUE;
END;
END MODULE; |
--------------------------------------------------------------------------------
=> Please find USER trace as well below . Not sure whats causing the problem. Do you see anything wrong in the syntax?
-------------------------------------------------------------------------------
| Code: |
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version 9002; formatter version 9002 (build S900-FP02 on amd64_nt_4)
2015-06-26 11:28:10.508806 11876 UserTrace BIP4040I: The Execution Group ''WebService'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2015-06-26 11:28:10.509326 11876 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''QM''. The MQCC was '0' and the MQRC was '0'.
2015-06-26 11:28:10.509375 11876 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''QM''.
2015-06-26 11:28:10.509603 11876 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2015-06-26 11:29:05.108789 15740 UserTrace BIP3630I: The broker has received an HTTP message on port '8089' with URL path '/DBHDS_ModuleWeb/sca/WSExport1'.
The broker is listening on port '8089' and has received a message sent by a client using URL path '/DBHDS_ModuleWeb/sca/WSExport1'. This message will be sent on to either a SOAP Input Node or a SOAP Asynchronous Response Node.
No action required.
2015-06-26 11:29:05.110294 11356 UserTrace BIP11501I: Received data from input node ''SOAP Input''.
The input node ''SOAP Input'' has received data and has propagated it to the message flow ''ETS_Routing_Flow''.
2015-06-26 11:29:05.110474 11356 UserTrace BIP6060I: Node 'ETS_Routing_Flow.SOAP Input' used parser type ''Properties'' to process a portion of the incoming message of length '0' bytes beginning at offset '0'.
2015-06-26 11:29:05.110559 11356 UserTrace BIP6061I: Node 'ETS_Routing_Flow.SOAP Input' used parser type ''SOAP'' to process a portion of the incoming message of length '8' bytes beginning at offset '0'. The parser type was selected based on value ''SOAP'' from the previous parser.
2015-06-26 11:29:05.110615 11356 UserTrace BIP3907I: Message received and propagated to 'out' terminal of input node 'ETS_Routing_Flow.SOAP Input'.
2015-06-26 11:29:05.110721 11356 UserTrace BIP2539I: Node 'ETS_Routing_Flow.Trace1': Evaluating expression ''Root'' at ('', '1.3'). This resolved to ''Root''. The result was ''ROW... Root Element Type=16777216 NameSpace='' Name='Root' Value=NULL''.
2015-06-26 11:29:05.111301 11356 UserTrace BIP4067I: Message propagated to output terminal for trace node 'ETS_Routing_Flow.Trace1'.
The trace node 'ETS_Routing_Flow.Trace1' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2015-06-26 11:29:05.111363 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''DECLARE ns NAMESPACE 'http://DMAS_IRI_Mediation';'' at ('.ns', '1.1').
2015-06-26 11:29:05.130312 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''BEGIN ... END;'' at ('.ETS_Routing_Flow_Database.Main', '2.2').
2015-06-26 11:29:05.130394 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''DECLARE NS1 NAMESPACE 'http://EFT_Test/CustomerInput';'' at ('.ETS_Routing_Flow_Database.Main', '3.3').
2015-06-26 11:29:05.130436 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''DECLARE bons0 NAMESPACE 'http://DMAS_IRI_Mediation';'' at ('.ETS_Routing_Flow_Database.Main', '4.3').
2015-06-26 11:29:05.130474 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''DECLARE fileId INTEGER 0;'' at ('.ETS_Routing_Flow_Database.Main', '5.3').
2015-06-26 11:29:05.130511 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''DECLARE currentTime CHARACTER;'' at ('.ETS_Routing_Flow_Database.Main', '6.3').
2015-06-26 11:29:05.130553 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''SET fileId = CAST(FIELDVALUE(Root.SOAP.Body.NS1:getCustomer.input1.fileId) AS INTEGER);'' at ('.ETS_Routing_Flow_Database.Main', '7.3').
2015-06-26 11:29:05.172647 11356 UserTrace BIP2540I: Node 'ImbESQLManager': Finished evaluating expression ''FIELDVALUE(Root.SOAP.Body.NS1:getCustomer.input1.fileId)'' at ('.ETS_Routing_Flow_Database.Main', '7.21'). The result was '''1141'''.
2015-06-26 11:29:05.172798 11356 UserTrace BIP2539I: Node 'ImbESQLManager': Evaluating expression ''CAST(FIELDVALUE(Root.SOAP.Body.NS1:getCustomer.input1.fileId) AS INTEGER)'' at ('.ETS_Routing_Flow_Database.Main', '7.16'). This resolved to ''CAST('1141' AS INTEGER)''. The result was ''1141''.
2015-06-26 11:29:05.172886 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''SET currentTime = CAST(CURRENT_TIMESTAMP AS CHARACTER FORMAT 'dd-MMM-yy hh.mm.ss.SSSSSS');'' at ('.ETS_Routing_Flow_Database.Main', '9.3').
2015-06-26 11:29:05.173060 11356 UserTrace BIP2540I: Node 'ImbESQLManager': Finished evaluating expression ''CURRENT_TIMESTAMP'' at ('.ETS_Routing_Flow_Database.Main', '9.26'). The result was ''TIMESTAMP '2015-06-26 11:29:05.111344'''.
2015-06-26 11:29:05.173170 11356 UserTrace BIP2539I: Node 'ImbESQLManager': Evaluating expression ''CAST(CURRENT_TIMESTAMP AS CHARACTER FORMAT 'dd-MMM-yy hh.mm.ss.SSSSSS')'' at ('.ETS_Routing_Flow_Database.Main', '9.21'). This resolved to ''CAST(TIMESTAMP '2015-06-26 11:29:05.111344' AS CHARACTER FORMAT 'dd-MMM-yy hh.mm.ss.SSSSSS' )''. The result was '''26-Jun-15 11.29.05.111344'''.
2015-06-26 11:29:05.173246 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''IF fileId > 0 THEN... ELSE... END IF;'' at ('.ETS_Routing_Flow_Database.Main', '10.3').
2015-06-26 11:29:05.173314 11356 UserTrace BIP2539I: Node 'ImbESQLManager': Evaluating expression ''fileId'' at ('.ETS_Routing_Flow_Database.Main', '10.6'). This resolved to ''fileId''. The result was ''1141''.
2015-06-26 11:29:05.173378 11356 UserTrace BIP2539I: Node 'ImbESQLManager': Evaluating expression ''fileId > 0'' at ('.ETS_Routing_Flow_Database.Main', '10.13'). This resolved to ''1141 > 0''. The result was ''TRUE''.
2015-06-26 11:29:05.173453 11356 UserTrace BIP2537I: Node 'ETS_Routing_Flow.WebService Ack': Executing statement ''INSERT INTO Database.TRANSACTION_STATUS_ETS ( TRANSID, STATUS, ERROR_MESSAGE, STATUS_TIMESTAMP, STATUS_CD ) VALUES (fileId, 'FileReceived', NULL, currentTime, 2 ) '' at ('.ETS_Routing_Flow_Database.Main', '11.5').
2015-06-26 11:29:05.173551 11356 UserTrace BIP2539I: Node 'ImbESQLManager': Evaluating expression ''fileId'' at ('.ETS_Routing_Flow_Database.Main', '12.12'). This resolved to ''fileId''. The result was ''1141''.
2015-06-26 11:29:05.173614 11356 UserTrace BIP2539I: Node 'ImbESQLManager': Evaluating expression ''currentTime'' at ('.ETS_Routing_Flow_Database.Main', '12.42'). This resolved to ''currentTime''. The result was '''26-Jun-15 11.29.05.111344'''.
2015-06-26 11:29:05.173676 11356 UserTrace BIP2544I: Node 'ETS_Routing_Flow.WebService Ack': Executing database SQL statement ''INSERT INTO TRANSACTION_STATUS_ETS(TRANSID, STATUS, ERROR_MESSAGE, STATUS_TIMESTAMP, STATUS_CD) VALUES (?, ?, ?, ?, ?)'' derived from ('.ETS_Routing_Flow_Database.Main', '11.5'); expressions ''fileId, 'FileReceived', NULL, currentTime, 2''; resulting parameter values ''1141, 'FileReceived', NULL, '26-Jun-15 11.29.05.111344', 2''.
2015-06-26 11:29:05.174870 11356 Error BIP2628E: Exception condition detected on input node 'ETS_Routing_Flow.SOAP Input'.
The input node 'ETS_Routing_Flow.SOAP Input' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2015-06-26 11:29:05.174970 11356 RecoverableException BIP2230E: Error detected whilst processing a message in node 'ETS_Routing_Flow.WebService Ack'.
The message broker detected an error whilst processing a message in node 'ETS_Routing_Flow.WebService Ack'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2015-06-26 11:29:05.175012 11356 RecoverableException BIP2488E: ('', '1.1') Error detected whilst executing the SQL statement ''''.
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.
2015-06-26 11:29:05.175051 11356 DatabaseException BIP2321E: Database error: ODBC return code '-1' using ODBC driver manager ''odbc32.dll''.
The message broker encountered an error when processing a database operation. The ODBC return code was '-1'. See the following messages for information obtained from the database concerning this error.
Use the following messages to determine the cause of the error. Typical problems are an incorrect datasource or table names. Correct either the database or message broker configuration.
2015-06-26 11:29:05.175085 11356 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. Use the mqsicvp command to test connectivity to this database.
2015-06-26 11:29:05.175204 11356 UserTrace BIP11507W: Rolled back a local transaction.
A local transaction has been rolled back for work done on the message flow thread.
2015-06-26 11:29:10.176091 11356 UserTrace BIP11504I: Waiting for data from input node ''SOAP Input''.
A thread is waiting for data from input node ''SOAP Input'' in flow ''ETS_Routing_Flow''.
2015-06-26 11:30:09.604211 11876 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2015-06-26 11:30:09.604335 11876 UserTrace BIP6060I: Node '.InputNode' used parser type ''Properties'' to process a portion of the incoming message of length '0' bytes beginning at offset '0'.
2015-06-26 11:30:09.604383 11876 UserTrace BIP6061I: Node '.InputNode' used parser type ''MQMD'' to process a portion of the incoming message of length '364' bytes beginning at offset '0'. The parser type was selected based on value ''MQHMD'' from the previous parser.
2015-06-26 11:30:09.604468 11876 UserTrace BIP6061I: Node '.InputNode' used parser type ''XMLS'' to process a portion of the incoming message of length '209' bytes beginning at offset '364'. The parser type was selected based on value ''XMLS'' from the previous parser.
2015-06-26 11:30:09.604746 11876 Information BIP2152I: Configuration message received from broker.
An execution group received a command from the Broker.
No user action required.
2015-06-26 11:30:09.604894 11876 Information BIP2153I: About to ''Change'' an execution group.
An execution group is about to perform an action.
No user action required.
Threads encountered in this trace:
11356 11876 15740 |
|
|
| Back to top |
|
 |
| nelson |
| Posted: Fri Jun 26, 2015 10:25 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| Are you running a supported database version? |
|
| Back to top |
|
|
| GAKD |
| Posted: Fri Jun 26, 2015 10:29 am Post subject: Yes it ORACLE database which is hosted in my local system |
|
|
Novice
Joined: 25 Jun 2015
Posts: 14
|
| Yes it ORACLE database which is hosted in my local system |
|
| Back to top |
|
|
| GAKD |
| Posted: Fri Jun 26, 2015 10:38 am Post subject: Got it. Enabled SQLDescribeParam in setting WIndows ODBC |
|
|
Novice
Joined: 25 Jun 2015
Posts: 14
|
| 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). |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jun 26, 2015 10:52 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
you have a problem with your ODBC setup:
| Quote: |
| [Microsoft][ODBC Driver Manager] Driver does not support this function |
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
