sky123 wrote:What do you mean by APEX_040100 schema was copied into APEX_040200 ??
The upgrade stopped at exactly the following (2 times already), which tried to run the "sample_app.sql" under the following path:
There were some obsolete entries of the sample application with exactly the same ID = 8950 in the following tables:
Therefore, after the APEX_040100 schema was copied into APEX_040200 and when it tried to insert those LOV again, it violated the constraint. The sample applications - as well as some others unused applications - were already dropped from the APEX workspace in APEX_040100. I don't know why these obsolete entries still exist in these tables. Should I simply delete them before the upgrade? Why weren't they automatically removed by APEX when the applications were dropped?
and wwv_flow_lov_data_fk on wwv_flow_list_of_values_data
flow_id number not null constraint wwv_flow_lov_fk references wwv_flows on delete cascade,
in your APEX_040100 schema. Are those constraints enabled and validated? I'm wondering how you could have a LOV for a non existing application if there is a "delete cascade" FK which automatically removes the LOV if an application is deleted. Those FK exist at least for 6 years.
lov_id number constraint wwv_flow_lov_data_fk references wwv_flow_lists_of_values$ on delete cascade,