My Oracle Support Banner

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.

Goal

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)

http://docs.oracle.com/cd/E16655_01/server.121/e17615/refrn10321.htm#REFRN10321
 

Similar errors are seen:

  

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.