Changing the undo_tablespace parameter in a Data Guard/Active Data Guard Physical Standby environment
Last updated on FEBRUARY 17, 2015
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.5 and later
Information in this document applies to any platform.
Maintain the viability of all physical standby databases in a Data Guard/Active Data Guard configuration when changing the UNDO Tablespace at the Primary database.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms