Oracle数据库pdb管理-Database Won‘t Start After Varchar2(32k) Upgrade (Doc ID 1610329.1)

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:

SQL> startup
ORACLE instance started.
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-14696: MAX_STRING_SIZE migration is incomplete for pluggable database
PDB$SEED
Process ID: 2845
Session ID: 1 Serial number: 5

SOLUTION

This is because the seed still not upgraded.
Even if you don’t have any running PDBS, you’re still going to need to upgrade the seed…
So please do the upgrade for the seed and try again.
Similar to:

SQL> startup mount
SQL> alter database open migrate;
Database altered.
SQL> select con_id, name, open_mode from v$pdbs;
CON_ID NAME OPEN_MODE
---------- ------------------------------ ----------
2 PDB$SEED MIGRATE
SQL> alter session set container=PDB$SEED;
Session altered.
SQL> alter system set max_string_size = EXTENDED;
System altered.
SQL> @?/rdbms/admin/utl32k.sql
PL/SQL procedure successfully completed.