Thanks for the heads up here. I’ll be looking out for the support ticket here.
We would not have expected a major increase in temp space utilization here, especially without enabling the new patch reporting capabilities. Another thought would be if certain steps of the ETL were manually disabled in the past due to issues and the upgrade has them running again.
We are aware of some significant temp usage on DB2 BES DB backends, and have prioritized working on addressing that, but is some substantial rewriting of things so will take us a little while.
