MQSeries.net :: View topic - DATE

Vijay_d · Posted: Tue Aug 05, 2008 1:02 pm Post subject:

Hi,

Please let me know wat caused me this error when iam trying to insert to oracle DB using compute node

INSERT INTO Database.FBD_FAC_BASIC_DTLS ( date1 ) values ( tag1.date )

the table is created in oracle with the column DATE1 decalred as DATE field.

The ODBC driver used is MQ series 32 bit oracle (10g). the error states its a driver error. Please let me know if there is any driver for 10g which is supported by broker 6.0.0.7

sample XML
___________
<TAG1>
<DATE>01-Jan-08</Date>
</TAG1>

Thanks in advance

Please find the trace file below
_____________________________
Error BIP2628E: Exception condition detected on input node 'LMSCrtFac.MQInput'.
The input node 'LMSCrtFac.MQInput' 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.
2008-08-05 17:48:16.318502 4208 RecoverableException BIP2230E: Error detected whilst processing a message in node 'LMSCrtFac.Compute1'.
The message broker detected an error whilst processing a message in node 'LMSCrtFac.Compute1'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2008-08-05 17:48:16.318513 4208 RecoverableException BIP2488E: ('.LMSCrtFac_Compute1.Main', '65.3') Error detected whilst executing the SQL statement ''INSERT INTO Database.FBD_FAC_BASIC_DTLS ( fbd_facility_id, fbd_facility_type, fbd_credit_appl_id, fbd_facility_strt_dt, fbd_facility_expry_dt, fbd_limit_crncy, fbd_gross_limit, fbd_net_limit, fbd_status, fbd_status_cd, fbd_le_id ) VALUES (NewFacId, LMSFaclity.FacilityType, LMSFaclity.FacilityCreditApplId, LMSFaclity.FacilityStartDate, LMSFaclity.FacilityExpDate, LMSFaclity.FacilityLimitCurr, LMSFaclity.FacilityGrossLt, LMSFaclity.FacilityNetLt, LMSFaclity.FacilityStatus, LMSFaclity.FacilityStatusCode, LMSParty.PartyId ) ''.
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.
2008-08-05 17:48:16.318523 4208 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.
2008-08-05 17:48:16.318534 4208 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.
2008-08-05 17:48:17.319768 4208 Error BIP2648E: Message backed out to a queue; node 'LMSCrtFac.MQInput'.
Node 'LMSCrtFac.MQInput' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2008-08-05 17:48:17.320220 4208 UserTrace BIP2638I: The MQ output node 'LMSCrtFac.MQInput' attempted to write a message to queue ''SYS_FAILURE'' connected to queue manager ''WBRK6_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2008-08-05 17:48:17.320241 4208 UserTrace BIP2615I: The WebSphere MQ input node 'LMSCrtFac.MQInput' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required.
2008-08-05 17:48:21.041173 3776 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2008-08-05 17:48:21.041227 3776 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2008-08-05 17:48:21.041250 3776 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2008-08-05 17:48:21.041301 3776 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '243' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.