RE: Max_string_size to Standard

Not in the database you converted.

As the Support note states you can recover a backup from before the change was made.

You of course can build a new database and port the data, but you have to deal with all the object definitions that changed from the original standard to extended change  

https://docs.oracle.com/database/121/REFRN/GUID-D424D23B-0933-425F-BC69-9C0E6724693C.htm#REFRN10321

Altering MAX_STRING_SIZE will update database objects and possibly invalidate them, as follows:

• Tables with virtual columns will be updated with new data type metadata for virtual columns of VARCHAR2(4000), 4000-byte NVARCHAR2, or RAW(2000) type.
• Functional indexes will become unusable if a change to their associated virtual columns causes the index key to exceed index key length limits. Attempts to rebuild such indexes will fail with ORA-01450: maximum key length exceeded.
• Views will be invalidated if they contain VARCHAR2(4000), 4000-byte NVARCHAR2, or RAW(2000) typed expression columns.
• Materialized views will be updated with new metadata VARCHAR2(4000), 4000-byte NVARCHAR2, and RAW(2000) typed expression columns

And of course any place that anyone has used the extended character length and any data that might be stored in any of those extended character length columns.    

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Arpit Aggarwal Sent: Thursday, November 28, 2019 7:48 PM To: oracle-l_at_freelists.org
Subject: Max_string_size to Standard  

Hi Friends,  

Can someone confirm me if there is any alternative way to change max_string_size from extended to standard ?  

I understand from Oracle docs that it's not possible to change it back once it has been updated from standard to extended.  

Just wanted to check if someone else has come across this issue ?    

Regards,

Arpit

--
http://www.freelists.org/webpage/oracle-l