Changing the undo_tablespace parameter in a Data Guard/Active Data Guard Physical Standby environment
(Doc ID 1967747.1)
Last updated on JANUARY 17, 2023
Applies to:
Oracle Database Exadata Cloud Machine - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Goal
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.
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 |