This is related to a Product Defect ID CR 33835
It is likely due to the inadequacies of the SQL server to process deep table structures with DeleteCascade. To circumvent this, some table relations in the DPR environment are monitored by the Customizer. The VI.DB does not know about these restrictions and tries to delete the objects in the wrong order. The relation tests have now been deactivated for the transport.