Dangling References In DBA_NETWORK_ACL_PRIVILEGES When Using RCU To Drop The PORTAL Schema
Last updated on NOVEMBER 08, 2016
Applies to:Portal - Version 10.1.4.2 to 22.214.171.124.0 [Release 10gR2 to FMW11g]
Information in this document applies to any platform.
Checked for relevance on 21-Oct-2013
After dropping a PORTAL schema in the repository using RCU, some dangling privileges are still in place and breaks a new PORTAL install.
Step to reproduce:
- Run RCU against a database and install the Portal repository with schema CRASH_PORTAL
- Once installed, run RCU again and drop the CRASH_PORTAL
- Rerun the RCU and install Portal again as NEW_PORTAL.
This fails with the error below reported in portal.log:
checkinstall2=Add ACL for network packages if DB is 11.1 or higher...
old 4: schema varchar2(2000) := upper('&&1');
new 4: schema varchar2(2000) := upper('NEW_PORTAL');
Package DBMS_NETWORK_ACL_ADMIN exists, assign ACL if not already assigned
Removing dangling principals,if any from the ACL privilege list ...
ERROR: when assigning network ACL
ERROR at line 1:
ORA-24246: empty access control list (ACL) not allowed
ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 421
ORA-06512: at line 1
ORA-01403: no data found
ORA-06512: at line 83
This issue occurs when dropping the unique Portal schema in the database and trying to install it new.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms