My Oracle Support Banner

ORA-64204: encountered partial multibyte character - trying to run utl32k.sql script but a long time after setting MAX_STRING_SIZE=EXTENDED parameter (Doc ID 2977382.1)

Last updated on JULY 20, 2024

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database - Standard Edition - Version 19.17.0.0.0 and later
Oracle Database - Enterprise Edition - Version 19.17.0.0.0 and later
Gen 2 Exadata Cloud at Customer - Version N/A and later
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.

Symptoms

You are changing the MAX_STRING_SIZE=EXTENDED but you did not run the utl32k.sql script immediately following the change (so when the DB was still in UPGRADE mode).


Now you try and run the script but get an error:





Changes

Changed the MAX_STRING_SIZE to EXTENDED from STANDARD but utl32k.sql script was not run at the same time.

Cause

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
Symptoms
Changes
Cause
Solution
References


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