Thursday 1 September 2016

APEX Builder Installation error : ORA-00054: resource busy

While installing APEX builder in a duplicated database, I receive the following warnings and errors;

.  ____   ____           ____        ____
. /    \ |    \   /\    /     |     /
.|      ||    /  /  \  |      |    |
.|      ||---    ----  |      |    |-- 
.|      ||   \  /    \ |      |    |
. \____/ |    \/      \ \____ |____ \____
.
. Application Express Installation (DEV).
.........................................
.
... Checking prerequisites (ADD_DEV)
.
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
.
... Prerequisite checks passed.
.
no rows selected
PL/SQL procedure successfully completed.
..................
..................
Installing SYS view wrappers
Create apex_sys_all_synonyms view

View created.

Create apex_sys_all_objects view

View created.

Create apex_sys_all_constraints view

View created.

Create apex_sys_all_dependencies view

View created.

Installing Team Development objects
...create team development objects
create table wwv_flow_news
*
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired 

create unique index wwv_flow_news_idx1 on wwv_flow_news(security_group_id, id)
                                         *
ERROR at line 1:
ORA-00942: table or view does not exist 

create table  wwv_flow_links (
*
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified or timeout expired 

create index wwv_flow_links_idx1 on wwv_flow_links (security_group_id)
                                    *
ERROR at line 1:
ORA-00942: table or view does not exist 

The installation continues, however, the side effects of the above missing objects are numerous.
Once the pages are loaded and the installer puts me back in the console, I notice a number of invalid objects in the apex schema.

It seems that during the Team Development object installation, a resource busy issue compromises the installation. The solution was not an entire re-installation but rather
a re-running of the problematic subset of the installer - manually - and chasing it up with a recompile.

The script that runs the Team development install is <APEX_SOURCE>\apex\devins.sql

Within the devins.sql script, I extract the following lines of script and rerun them manually as sysdba:

alter session set current_schema = APEX_040200;

prompt Installing Team Development objects
@./core/team_tab.sql
@./core/wwv_flow_team.sql
@./core/wwv_flow_team_api.sql
@./core/wwv_flow_team_gen_api.sql

I then run a recompile:
@?/rdbms/admin/utlrp

The APEX objects are valid again and the builder is accessible.


No comments:

Post a Comment