Effect of Max_String_Size on Data guard
(Doc ID 2010497.1)
Last updated on DECEMBER 18, 2023
Applies to:
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.1.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Goal
This Article Explains the Effect of Max_String_Size on Dataguard Environment. From 12c onwards we can extend the Datatype Maximum Size of VARCHAR2, NVARCHAR2, and RAW Columns to 4k bytes in 12C Database using MAX_STRING_SIZE i.e If MAX_STRING_SIZE=EXTENDED on primary what will be effect on Physical and Logical Standby.
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 |
| I.PHYSICAL STANDBY |
| II.LOGICAL STANDBY |
| III. For a non CDB Dataguard Environment |
| Primary: |
| References |