APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

APEX 20.2, builder errors when change default authentication schema for an application

AndyHSep 9 2021 — edited Sep 9 2021

We have a workspace where if we try to change the default authentication schema for the applications an error is raised by the builder. The debug includes:

POST https://looradev01.ad.dom/ords203/apex
REMOTE_ADDR=0:0:0:0:0:0:0:1
REMOTE_USER=APEX_PUBLIC_USER
APEX_LISTENER_VERSION=20.3.0.r3011819
REFERER=https://looradev01.ad.dom/ords203/apex/f?p=4000:4495:12650220633376:::RP,4495:P4495_ID:157031766726401453

APEX Version=20.2.0.00.20
SID=141
USER=APEX_PUBLIC_USER
INSTANCE=1

and

Error in error handler: ORA-06550: line 5, column 38:
PLS-00201: identifier 'WWV_FLOW_ERROR_DEV.INTERNAL_ERROR_HANDLER' must be declared
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 124
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2282
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 555
ORA-06550: line 5, column 1:
PL/SQL: Statement ignored
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1458
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 544
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 1698
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2206
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 96
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 301
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC", line 340
ORA-06550: line 2, column 8:
PLS-00201: identifier 'WWV_FLOW_PLUGIN_DEV.HAS_STANDARD_ATTRIBUTE' must be declared
ORA-06512: at "APEX_200200.WWV_FLOW_PROCESS_NATIVE", line 56
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 124
ORA-06512: a~

and

Backtrace: ORA-06512: at "SYS.DBMS_SYS_SQL", line 1458
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 544
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1458
ORA-06512: at "APEX_200200.WWV_FLOW_PROCESS_NATIVE", line 56
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 124
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2282
ORA-06512: at "SYS.DBMS_SYS_SQL", line 2120
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 635
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2243
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 96
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 330
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC", line 394
ORA-06512: at "APEX_200200.WWV_FLOW_EXEC_LOCAL", line 2787
ORA-06512: at "APEX_200200.WWV_FLOW_EXEC", line 4172
ORA-06512: at "APEX_200200.WWV_FLOW_EXEC", line 4208
ORA-06512: at "APEX_200200.WWV_FLOW_PROCESS_NATIVE", line 35
ORA-06512: at "APEX_200200.WWV_FLOW_PROCESS_NATIVE", line 1116
ORA-06512: at "APEX_200200.WWV_FLOW_PLUG~ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 124
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2282
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 555
ORA-06512: at "SYS.DBMS_SYS_SQL", line 1458
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 544
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 1698
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2206
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 96
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 301
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC", line 340
ORA-06512: at "APEX_200200.WWV_FLOW_ERROR", line 771
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC", line 340
ORA-06512: at "APEX_200200.WWV_FLOW_PROCESS_NATIVE", line 56
ORA-06512: at "APEX_200200.WWV_FLOW_CODE_EXEC_PLSQL", line 124
ORA-06512: at "APEX_200200.WWV_FLOW_DYNAMIC_EXEC", line 2282
ORA-06512: at "SYS.DBMS_SYS_SQL", line 2120
ORA-06512: at "SYS.WWV_DBMS_SQL_APEX_200200", line 635
ORA-06512: at "APEX_200~

and 


- error_statement: begin begin
    if wwv_flow_plugin_dev.has_standard_attribute (
           p_application_id => :FB_FLOW_ID,
           p_plugin_type    => wwv_flow_plugin.c_plugin_type_authentication,
           p_plugin_name    => :P4495_SCHEME_TYPE,
           p_feature        => 'INVALID_SESSION' )
    then
        :P4495_INVALID_SESSION_TYPE := nvl(:P4495_INVALID_SESSION_TYPE, 'LOGIN');
    else
        :P4495_INVALID_SESSION_TYPE := null;
    end if;

    -- if it's not a URL type, clear the page item
    if nvl(:P4495_INVALID_SESSION_TYPE, 'PAGE') <> 'URL' then
        :P4495_INVALID_SESSION_URL := null;
    end if;

    -- if it's not a URL type, clear the page item
    if nvl(:P4495_LOGOUT_TYPE, 'PAGE') <> 'URL' then
        :P4495_LOGOUT_URL := null;
    end if;
end;
end;

The packages/routines referred to do exist, so I'm assuming that there is some kind of an installation error which has failed to grant permissions to the APEX_PUBLIC_USER? We've been through a few APEX upgrades and ORDS installations/back-outs in this database which mught have contributed!
Is there a way to validate and fix an APEX installation?

Processing

Added on Sep 9 2021

#apex-discussions

0 comments

32 views

APEX

APEX 20.2, builder errors when change default authentication schema for an application

Comments

Post Details