most probabily the private saved interacive report where never exported with the APPS in the first place.
have a look here if required to see how to it:
Thanks for the response Franck,
Actually the export did not include the saved interactive reports on purpose. That way when you update the app in different environments the existing private reports in each environment should not be overwritten. My problem is that they are being overwritten (i.e. deleted) in my production environment, but not in dev or test.
We are using SQLcl to do the export:
apex export -skipExportDate -expOriginalIds -split -splitNoCheckSum -applicationid $apexappid
The 2010 blog posting by joelkallman-Oracle is helpful. It suggests that we need to set the offset during application install to the same offset as the app we are replacing instead of generating a new offset every time (which is what we are currently doing). We can/will try using a consistent offset. It is surprising however that our current approach seems to work fine in dev and test.
We found the cause and solved this problem.
The problem was that in production our deploy script was being fired twice simultaneously. It appears even though the install is [apparently] completed in one transaction firing the script twice at exactly the same time changed how offset was applied to existing saved reports, resulting in them being deleted.