Standalone Non-Data Guard Database Server created from Primary Data Guard Server showing various Tablespaces encrypted related messages in its Alert log file
(Doc ID 2545651.1)
Last updated on FEBRUARY 19, 2020
Applies to:Advanced Networking Option - Version 220.127.116.11 and later
Information in this document applies to any platform.
Messages seen in alert log file for various datafiles when a Standalone Database server was created from a Primary (Data Guard Setup) Database Server. This Standalone server though is NOT on Data Guard.
"Data dictionary says tablespace 'USERS' #8 is encrypted, but the control file says some data files are not encrypted. This could happen if the primary tablespace is encrypted first, and a switchover is performed before encrypting the tablespace on the standby. If this is the case, please bring the tablespace offline or bring the database into mount mode, and encrypt all data files of this tablespace. If not and if all data files of this tablespace are unencrypted, this tablespace will no longer be considered as an encrypted tablespace."
1. Using RMAN, a backup is made from the Primary (Data Guard) Production Database to a Backup Device. This backup is restored to from the backup device to a New database where Data Guard is NOT configured. DUPLICATE command is used.
2. The Data Guard settings were removed from this Duplicate database and it was made a normal Standalone Server.
3. Duplicate database was encrypted using commands like below:
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