| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere Transformation Extender problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| balaji83it |
 Posted: Wed Apr 15, 2009 1:40 am Post subject: Websphere Transformation Extender problem |
 |
|
Acolyte
Joined: 20 Jul 2007
Posts: 72
|
Hello all,
I have a transformation extender mapping which maps from an XML message to the fields of a database table. My requirement is such that the xml contains some fields which have multiple occurrences. And for each occurrence, I need to make a new entry in the table, i.e. to say for one xml message we should create multiple rows in the table.
The structure of xml message is explained here below.
<xml>
<abc/>
<def/>
<Transactions>
<T1>
<Name/>
<Type/>
</T1>
<T2>
<Name/>
<Type/>
</T2>
<T3>
<Name/>
<Type/>
</T3>
</Transactions>
</xml>
The table entries should differ only in the transaction part. Remaining else should be the same.
Please let me know if any one has ideas or solutions. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Apr 15, 2009 2:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Why, specifically, do you need to use WTX for this? It seems like the regular WMB Mapping node will do just fine. |
|
| Back to top |
|
|
| balaji83it |
| Posted: Wed Apr 15, 2009 3:24 am Post subject: |
|
|
Acolyte
Joined: 20 Jul 2007
Posts: 72
|
Hello GrandMaster,
Iam using the mapping node, it is giving me the following exception
[Microsoft][ODBC Driver Manager] Information type out of range
The complete Exception List is here with attached.
ExceptionList
RecoverableException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbDataFlowNode.cpp
Line:INTEGER:957
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmMQInputNode
Name:CHARACTER:Classifier_Flow#FCMComposite_1_1
Label:CHARACTER:Classifier_Flow.MQInput
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
RecoverableException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbComputeNode.cpp
Line:INTEGER:464
Function:CHARACTER:ImbComputeNode::evaluate
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:Classifier_Flow#FCMComposite_1_9.ComIbmMapping#FCMComposite_1_1
Label:CHARACTER:Classifier_Flow.Mapping.ComIbmCompute
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
RecoverableException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbRdl\ImbRdlStatementGroup.cpp
Line:INTEGER:602
Function:CHARACTER:SqlStatementGroup::execute
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:Classifier_Flow#FCMComposite_1_9.ComIbmMapping#FCMComposite_1_1
Label:CHARACTER:Classifier_Flow.Mapping.ComIbmCompute
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2488
Text:CHARACTER:Error detected, rethrowing
Insert
Type:INTEGER:5
Text:CHARACTER:.IBM_WBIMB_Classifier_Flow_Mapping.MAIN
Insert
Type:INTEGER:5
Text:CHARACTER:3.1
Insert
Type:INTEGER:5
Text:CHARACTER:Classifier_Flow_Mapping(InputRoot, InputLocalEnvironment);
RecoverableException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbRdl\ImbRdlRoutine.cpp
Line:INTEGER:548
Function:CHARACTER:SqlRoutine::invoke
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:Classifier_Flow#FCMComposite_1_9.ComIbmMapping#FCMComposite_1_1
Label:CHARACTER:Classifier_Flow.Mapping.ComIbmCompute
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2934
Text:CHARACTER:Error occured in procedure
Insert
Type:INTEGER:5
Text:CHARACTER:Classifier_Flow_Mapping
RecoverableException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbRdl\ImbRdlStatementGroup.cpp
Line:INTEGER:586
Function:CHARACTER:SqlStatementGroup::execute
Type:CHARACTER:ComIbmComputeNode
Name:CHARACTER:Classifier_Flow#FCMComposite_1_9.ComIbmMapping#FCMComposite_1_1
Label:CHARACTER:Classifier_Flow.Mapping.ComIbmCompute
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2488
Text:CHARACTER:Error detected, rethrowing
Insert
Type:INTEGER:5
Text:CHARACTER:.Classifier_Flow_Mapping
Insert
Type:INTEGER:5
Text:CHARACTER:72.2
Insert
Type:INTEGER:5
Text:CHARACTER:INSERT INTO Database.ISCSA.ISCSA_USER.FTX_STATE_DEST ( FTX_STATE_DEST_ID, PROC_STATUS, TRANS_TYPE, TRANS_REC_TYPE, PYMT_TRANS_REF, BANK_ID, BANK_NAME, BANK_ACCT, BANK_ACCT_TYPE, ACCT_PYMT_REF, SWIFT_CDE, INTL_BANK_ACCT_NUM, ROUTE_NUM, DEST_CTRY_ID, DEST_AMT, DEST_AMT_DECIMAL, DEST_ISO_CRNCY_CDE, EFF_DT_TM, CREATEDDT ) VALUES ('100', '1', #sr2.(XMLNSC.Field)TransactionType, #sr2.(XMLNSC.Field)TransactionRecordType, #sr2.(XMLNSC.Field)PaymentTransactionReference, #sr2.DestinationAccount.Account.(XMLNSC.Field)BankID, #sr2.DestinationAccount.Account.(XMLNSC.Field)BankName, #sr2.DestinationAccount.Account.(XMLNSC.Field)BankAccount, #sr2.DestinationAccount.Account.(XMLNSC.Field)BankAccountType, #sr2.DestinationAccount.Account.(XMLNSC.Field)AccountPaymentReference, #sr2.DestinationAccount.Account.(XMLNSC.Field)SWIFTBIC, #sr2.DestinationAccount.Account.(XMLNSC.Field)IBAN, #sr2.DestinationAccount.Account.(XMLNSC.Field)RoutingNumber, #sr2.DestinationAccount.Account.(XMLNSC.Field)CountryCode, #sr2.(XMLNSC.Field)Amount, #sr2.(XMLNSC.Field)AmountDecimal, #sr2.(XMLNSC.Field)CurrencyCode, #sr2.(XMLNSC.Field)EffectiveDateTime, CURRENT_TIMESTAMP )
DatabaseException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbOdbc.cpp
Line:INTEGER:323
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2321
Text:CHARACTER:Root SQL exception
Insert
Type:INTEGER:2
Text:CHARACTER:-1
DatabaseException
File:CHARACTER:F:\build\S610_P\src\DataFlowEngine\ImbOdbc.cpp
Line:INTEGER:438
Function:CHARACTER:ImbOdbcHandle::checkRcInner
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:2322
Text:CHARACTER:Child SQL exception
Insert
Type:INTEGER:5
Text:CHARACTER:HY096
Insert
Type:INTEGER:2
Text:CHARACTER:0
Insert
Type:INTEGER:5
Text:CHARACTER:[Microsoft][ODBC Driver Manager] Information type out of range
My DB is oracle 10g
Iam using a driver type of MQSeries Data direct for Oracle.
Please let me know any ideas of solving this. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 3:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Did you configure and test the ODBC Oracle Data source? Did you talk to your Oracle DBA for assistance?
Are you sure you're using the right ODBC Driver for Oracle 10g on Windows with Message Broker? It has to be the DataDirect driver that comes with Broker, not any Oracle ODBC driver. |
|
| Back to top |
|
|
| balaji83it |
| Posted: Wed Apr 15, 2009 4:07 am Post subject: |
|
|
Acolyte
Joined: 20 Jul 2007
Posts: 72
|
Hello Master,
The following are my answers in bold to your questions:
Did you configure and test the ODBC Oracle Data source? Did you talk to your Oracle DBA for assistance?
I configured and tested the ODBCData source. I have run a number of flows with DB statements using the same dsn and is working fine.
Are you sure you're using the right ODBC Driver for Oracle 10g on Windows with Message Broker? It has to be the DataDirect driver that comes with Broker, not any Oracle ODBC drive
Iam using the driver type of MQ-Series data direct technologies5.3 32-bit Oracle.
I think there is no problem with dsn because I have run lot of DB statements from ESQL using the same dsn successfully.
Please let me know your ideas. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 15, 2009 4:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Okay,I agree. The data source is not the cause of the problem.
So the cause of the problem is either a bug in the mapping or more likely it's a data level error with the data you're trying to insert.
"Information type out of range" sounds like some field is not correctly matching validation rules. |
|
| Back to top |
|
|
| balaji83it |
| Posted: Wed Apr 15, 2009 6:10 am Post subject: |
|
|
Acolyte
Joined: 20 Jul 2007
Posts: 72
|
Hello Master,
Iam getting the following statement in the exception which I sent to you previously.
INSERT INTO Database.ISCSA.ISCSA_USER.FTX_STATE_DEST ( TRANS_TYPE ) VALUES (CAST(#sr1.(XMLNSC.Field)TransactionType AS CHARACTER) )
This exception is caused in Mapping node. Here in the above statement ISCSA_USER is my schema name and ISCSA is my physical data model name. Here ISCSA should not come in the statement.
It should be "Database.ISCSA_USER.FTX_STATE_DEST"
So what should I do to remove this.
Thanks
Balaji |
|
| 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
|
|
|
|
