Author |
Message
|
venky |
Posted: Mon Aug 11, 2008 5:45 pm Post subject: WMB V 6.0.2 & WBIA JDBC adapter 2.6.9 , Framework 2.6.11 |
|
|
 Master
Joined: 08 Jul 2003 Posts: 205
|
Hi Folks,
Here is my scenario:
Source App --> WMB Flow --> JDBC Adapter -->Target SQL database.
The JDBC adapter Business object is as follows: 1 parent table with 2 child tables--> child table 1 and child table 2.
When I send a 'Create' everything goes fine..parent table gets created along with 2 entries in child table..
Update: In an update, I am sending parent with only one type of child table (lets say child table 1)..so after updating the simple attributes of the parent table the adapter is suppose to delete the child table 2 entry from the database and update or delete and create new child table 1.
Eventually, at the end of the transaction, I should have 1 row in parent table with 1 row in child table1. But, I am getting the following error:
[Time: 2008/08/11 18:31:08.115] [System: ConnectorAgent] [SS: SQLJDBCConnector] [Thread: ESRI.IDB2.JDBC.REQUESTQUEUEJmsThreadPool.thread1 (#1161621212)] [Type: Trace] [Mesg: :
com.crossworlds.cwconnectorapi.exceptions.ConnectionFailureException: [Type: Error] [MsgID: 37004] [Mesg: Execution of Prepared Update Statement Failed : com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'null'.]
at com.crossworlds.connectors.JDBC.JDBCBOhandler.doVerbFor(JDBCBOhandler.java:1802)
at com.crossworlds.cwconnectorapi.CWConnectorBOHandler.doVerbFor(CWConnectorBOHandler.java:127)
at CxCommon.BusinessObject.doVerbFor(BusinessObject.java:2179)
at AppSide_Connector.BusObjJavaInterface.DoVerbFor(BusObjJavaInterface.java:255)
at AppSide_Connector.AppCalls.DoVerbFor(AppCalls.java:266)
at AppSide_Connector.AgentBusinessObjectManager.DoVerbFor(AgentBusinessObjectManager.java:1777)
at CxCommon.Messaging.ClientPacketSyncDrvFormatter.receiverCallback(ClientPacketSyncDrvFormatter.java:1551)
at CxCommon.Messaging.jms.Receiver.processBO(Receiver.java:962)
at CxCommon.Messaging.jms.Receiver.processMsg(Receiver.java:552)
Any suggestion..help ?
Thanks all, V |
|
Back to top |
|
 |
Gaya3 |
Posted: Tue Aug 12, 2008 1:42 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
are doing any condition checks for NULL value in the Adapter side.
if so please let us know _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
venky |
Posted: Tue Aug 12, 2008 7:44 am Post subject: |
|
|
 Master
Joined: 08 Jul 2003 Posts: 205
|
No, I am not.
Also, from the trace, I see the following lines..
[Time: 2008/08/12 08:35:15.045] [System: ConnectorAgent] [SS: SQLJDBCConnector] [Thread: ABCD.IDB2.JDBC.REQUESTQUEUEJmsThreadPool.thread1 (#1153173825)] [Type: Trace] [Mesg: :update Dispatch_Equipment set null='null' where DispatchId=3723583 and EquipmentCode=73013 |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Aug 12, 2008 9:29 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Column name should never be "null".
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
venky |
Posted: Tue Aug 12, 2008 9:37 am Post subject: |
|
|
 Master
Joined: 08 Jul 2003 Posts: 205
|
None of the columns in the BO are named null.
The 'Create' goes through fine...Its only the 'Update' I am having trouble with. |
|
Back to top |
|
 |
fjb_saper |
Posted: Tue Aug 12, 2008 9:40 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
venky wrote: |
[Mesg: :update Dispatch_Equipment set null='null' where DispatchId=3723583 and EquipmentCode=73013 |
And here we have a column named null ? _________________ MQ & Broker admin |
|
Back to top |
|
 |
venky |
Posted: Tue Aug 12, 2008 10:01 am Post subject: |
|
|
 Master
Joined: 08 Jul 2003 Posts: 205
|
yes, I see what you are asking. But, I am sure that in my BO or ib my code I have no column name set to "null"
Well, if I have a column name set to null...there is no way that the 'Create' will go through right?
May be a its a problem with the adapter or the jdbc driver I am using.. |
|
Back to top |
|
 |
venky |
Posted: Tue Aug 19, 2008 9:47 am Post subject: Solved |
|
|
 Master
Joined: 08 Jul 2003 Posts: 205
|
This problem was solved by setting the "ChildUpdatePhyDelete" property in the connector configurator to true.
As they mention in the JDBC adapter manual, we will see unpredictable results if the properties are not set correct.
V |
|
Back to top |
|
 |
|