Database Won't Start After Varchar2(32k) Upgrade
(Doc ID 1610329.1)
Last updated on JANUARY 03, 2020
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Why the database fails to start after upgrading from varchar2(4000) to varchar2(32k), that is applying MAX_STRING_SIZE='EXTENDED' procedure as clarified in the
Oracle® Database Reference 12c Release 1 (12.1)
Similar errors are seen:
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