APEX is Invalid After Running utl32k.sql and Setting max_string_size=EXTENDED
(Doc ID 2876381.1)
Last updated on MARCH 20, 2025
Applies to:
Oracle Application Express (APEX) - Version 20.1 and laterAPEX Application Development - Version NA and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After running utl32k.sql script and setting the max_string_size=EXTENDED parameter, APEX component is INVALID in the DBA_REGISTRY
ERROR
-----------------------
Errors in file <oracle_home>\diag\rdbms\...\trace\<trace_file>.trc:
ORA-12012: error on auto execute of job "APEX_200100"."ORACLE_APEX_DICTIONARY_CACHE"
ORA-04063: package body "APEX_200100.WWV_FLOW_FACETED_SEARCH_DEV" has errors
ORA-06508: PL/SQL: could not find program unit being called: "APEX_200100.WWV_FLOW_FACETED_SEARCH_DEV"
ORA-06512: at "APEX_200100.WWV_DICTIONARY_CACHE_DEV", line 2175
ORA-06512: at "APEX_200100.WWV_DICTIONARY_CACHE_DEV", line 2175
ORA-06512: at "APEX_200100.WWV_DICTIONARY_CACHE_DEV", line 2787
...
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run the "utl32k.sql" script
2. Set "max_string_size=EXTENDED"
3. APEX component became invalid in DBA_REGISTRY
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |