Tablespace Encryption Errors after Standby Switchover
Last updated on SEPTEMBER 29, 2016
Applies to:Advanced Networking Option - Version 126.96.36.199 and later
Information in this document applies to any platform.
Database alert log shows the following after being switched over from standby to primary.
Dictionary check beginning
Data dictionary says tablespace '<tablespace_name>' #<TS_number> 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 switch over 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms