My Oracle Support Banner

All About the Initialization Parameter MAX_STRING_SIZE and Related Issues (Doc ID 2673210.1)

Last updated on JUNE 04, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Information in this document applies to any platform.

Purpose

This document is included in the DB:Parameters Automation and hence is required to be customer visible. Please contact the DB:Admin Automation lead before changing the document status.

This document is a one-stop solution for all queries related to MAX_STRING_SIZE initialization parameter. The details such as the impact of the parameter, how to set it and related issues are all discussed here.

Questions and Answers

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
Purpose
Questions and Answers
 1. MAX_STRING_SIZE Parameter - Explanation
 2. After changing parameter MAX_STRING_SIZE=EXTENDED can I rollback it to STANDARD?
 3. How to set MAX_STRING_SIZE=EXTENDED in non CDB single instance database?
 4. How to set MAX_STRING_SIZE=EXTENDED in non CDB RAC database?
 5. How to set MAX_STRING_SIZE=EXTENDED in a container database?
 6. ORA-30556 and/or ORA-54031 reported while executing utl32k.sql script
 7. ORA-14415 reported while executing utl32k.sql script
 8. ORA-02019 reported while executing utl32k.sql script
 9. ORA-30556 or ORA-01404 or ORA-01450 reported while modifying the table column(s) length to greater than 4000 characters
 10. Wrong results using max_string_size=extended and indexes
 11. ORA-01467 In Oracle 12c when max_string_size is Extended Data Types used
 12. RMAN Recover Table Command Fails When Parameter Max_string_size=EXTENDED
References

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