title: Chasing up "ORA-01084: invalid argument in OCI call"
body: <p>I've got here enterprise project with .net 4.0 c#, IBatisNet and CSLA framework. </p>
  
  <p>One of project jobs is failing with <code>ORA-01084: invalid argument in OCI call</code> when calling insert proc in a package. Error message returned is cryptic at best, the stored proc has 83 input parameters which aren't bound by name (thanks to IBatis). </p>
  
  <p>What is curious: I've got a set of records let's say <code>Order</code> and <code>OrderItems</code>. <code>Order</code> has 28 order items. The job has to renew the order by creating another <code>Order</code> and copying all <code>OrderItems</code> records. New order items are referencing the old order items by <code>ParentOrderItemId</code> field, which is also a selection criteria for <code>Orders</code> due to be renewed. </p>
  
  <p>When I run it first time the process blows on <code>OrderItemId: 12345</code> with <code>ORA-01084</code> error. But when I rerun it next time, it successfully process <code>OrderItemId: 12345</code>. And then blows up on <code>OrderItemId: 12444</code>. I then rerun and it processes <code>OrderItemId: 12444</code> correctly and so on and so forth. </p>
  
  <p>I've got logs of DbParameters passed in they are the same in both cases. </p>
  
  <p>I've got oci client trace, but it's not useful either. </p>
  
  <p>I've setup logging on a database layer, and so far it's giving me nothing. </p>
  
  <p>Any ideas how to trace those type of errors?</p>