I posed a question last year with the same topic (), I was hoping the upgrade to 18 would have fixed it. Unfortunately, it did not. I went back to update my old issue and it was archived. I accidentally marked it "assumed fixed," but it is actually not fixed. There is no way for me to update that old article, so I will post a new one I guess.
We have a page with an Interactive Grid containing an (admittedly complex) sql query. The query spans multiple databases and can return a huge dataset. We expect it to be a little slow (few seconds). Everything works fine until we export the application (using the builder export tool) and import into another environment (Test/Production). After Import, the exact same page now takes around a minute to load. If we go into builder within that environment (Test/Prod) and add a space to the query to register a change (exact same query) the page works fine. I can reproduce this every time. It even does this if I export the app from dev and import it back into dev. Until I make any change to the page and save it, the page runs REALLY slow.
Unfortunately, this app is tied into our eBusiness applications so I cannot reproduce it on apex.com. I am just curious to know what would be different about running a page that has been directly edited with builder vs imported?
We have been experiencing this for over a year now with multiple versions of APEX (starting with 5.0 and now we are on 18.2.0.00.12). I have opened a second ticket with Oracle and am now waiting for a response, however they have not been helpful in the past so I am not confident they will be helpful now. For now, our only work around is to have the person performing the migration, actually go into builder and edit each impacted page and save it. This is not ideal. Especially in production to have developers updating the app in our live environment.
Thank you,
Jen