Major Problem with importing application from QA environment to PROD

Question

We did our first ever full move of our application from our QA server to our PROD server tonight. First, I exported the current PROD application version as a backup. Then I did an export of the application on QA and then imported it into PROD using the same application ID as it had previously (which is the same as it was in QA). When the installation portion of the import was running I received an error. The error was: ORA-20001: GET_BLOCK Error. ORA-20001: Execution of the statement was unsuccessful. ORA-00001: unique constraint (APEX_030200.WWV_FLOW_WORKSHEET_COND_PK) violated <pre>begin wwv_flow_api.create_worksheet_condition( p_id => 2700222847807840wwv_flow_api.g_id_offset, p_flow_id=> wwv_flow.g_flow_id, p_page_id=> 42, p_worksheet_id => 7285923079312021+wwv_flow_api.g_id_offset, p_report_id => 2694211409728899+wwv_flow_api.g_id_offset, p_condition_type+*
h1. We have been unable to get the app installed using the same application ID, so we installed it using a new application ID. However, we have now lost all of the user's saved interactive reports.
h3. So, first, we need to know how to get the user's saved interactive reports put into the new application id. Second, we need to know what the proper procedures should have been for exporting our QA application and importing it into PROD without loosing the saved interactive reports. Hope someone can help us out very quickly - the natives will be very restless tomorrow morning when they find out that they don't have their saved reports.
Thanks in advance for any help you can provide!
Dale

Answer 1

Thanks for your reply Scott.
The problem is that the saved reports are not in the application we are exporting, they are in the one we are trying to update. I'll try to provide a more detailed description of what we are doing. We have two separate server environments, one for our production Oracle databases and our production APEX workspaces and applications. The other is for our development and QA Oracle databases and APEX workspaces and applications. Both environments run the same version of Oracle. So, on the production environment, we have a workspace called "payorprofile" and, within that workspace we have an application with application ID 126. That is where our users have been happily creating their saved interactive reports for the past 4 months. On the development environment, we have a workspace called "payorprofile" and, within that workspace we have an application with application ID 126. Now we have a new version of application 126 on the development environment that we need to promote to production. This newly QA'd version does NOT have the user's saved reports but it has all of the new and changed pages, LOVs, lists, breadcrumbs, etc. We needed to merge the new pages, etc. from dev with the data and user's saved reports on prod. What we did was to export the Dev version without saved reports and then we imported it into the prod system using the same application ID. It asked if we wanted to overlay the current application 126 with the new one and we said yes. During the install step we got the error noted in this post. The only thing we knew to do was to import the dev application as a new application ID (we chose 326). The application works fine, but, of course, we don't have the saved reports. Now we need to get the saved reports into the new application 326 - and I think with the help of some articles and posts on the web we can do that. However, we need to know what to do differently the next time we are ready to promote a version of the application to production.
Thanks,
Dale