Cascade deletes in DB2

I am using cascade deletes in DB2 and an error is generated by the DB2 driver. I copied the SQL generated by LightSpeed and tried it against the database from DB2 Maestro. I get the same error.

[IBM][CLI Driver][DB2/NT64] SQL0206N "LINEITEMS.PARENTDOCUMENTID" is not valid in the context where it is used. SQLSTATE=42703

The SQL is:

DELETE FROM
  dbo.LineItems
WHERE
  EXISTS (
    SELECT
      Documents.*
    FROM
      dbo.Documents Documents
    WHERE
      Documents.Id = LineItems.ParentDocumentId AND
      Documents.ParentTripId = 1897
  );

It works if the SQL is changed to:

DELETE FROM
  dbo.LineItems
WHERE
  EXISTS (
    SELECT
      Documents.*
    FROM
      dbo.Documents Documents
    WHERE
      Documents.Id = dbo.LineItems.ParentDocumentId AND
      Documents.ParentTripId = 1897
  );

Notice the "dbo." in front of LineItems,ParentDocumentId in the second WHERE.

Can this be fixed in configuration?

This looks like a bug - Im assuming you have specified dbo as the schema on your context or as part of the table definition but it isnt being applied correctly as part of that criteria - is it possible to send through a small repro project which triggers this for us to investigate further with?

Thanks!
Jeremy

I did not follow through on this as we moved cascade delete to the database. The issue has re-appeared in another context, where the user is not the owner of the schema "dbo".

The generated SQL for a delete is: DELETE FROM dbo.Orders WHERE Orders.OrderId = '55505'

This results in a DB2 error SQL0206N "ORDERS.ORDERID" is not valid in the context where it is used.

The query works if it is: DELETE FROM dbo.Orders WHERE dbo.Orders.OrderId = '55505'

Unfortunately this was discovered on production testing where the database security setup is a lot more restrictive. Basically the table names need to always be fully qualified with the schema name. Is there a setting that will activate this?