Database Administration (MOSC)

MOSC Banner

Running utl32k.sql Invalidated APEX and XDB in DBA_REGISTRY

Note:

This question has been posted first in APEX Forum. No responses. I do not know how to delete this post in APEX forum.

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)”. BUT I HAVE NOT DONE 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

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center