Database Won't Start After Varchar2(32k) Upgrade

(Doc ID 1610329.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

Oracle Database - Enterprise Edition - Version and later
Information in this document applies to any platform.
***Checked for relevance on 13-Sep-2016***


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:



Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms