Oracle Application Express (MOSC)

MOSC Banner

Running utl32k.sql Invalidated APEX and XDB in DBA_REGISTRY

edited Nov 15, 2024 4:31PM in Oracle Application Express (MOSC) Question

Database Version 19.25

APEX Version: 22.2.4

This is for increasing varchar2 limit to 32k. MAX_STRING_SIZE=EXTENDED
utl32k.sql ran fine with no errors. Then ran /rdbms/admin/utlrp.sql which generated tons of "ORA-20001: COMPILE FAILURE" errors.
And also, following two components became INVALID.
Oracle XML Database 19.0.0.0.0 INVALID
Oracle APEX 22.2.4 INVALID

I came across “APEX is Invalid After Running utl32k.sql and Setting max_string_size=EXTENDED (Doc ID 2876381.1)”. THIS TOO EXTENSIVE, SO I HAVE NOT DONE THIS AT THIS POINT.


I came across “XDB Invalid After utl32k.sql during activation of extended datatypes (Doc ID 1667684.1)”. Simple fix. I did this.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center