ORA-16485
protection mode modification not allowed at this time
Cause
This exception occurred because of one of the following circumstances:
- If the DG_CONFIG attribute of the LOG_ARCHIVE_CONFIG parameter was not defined, the protection mode could not be modified if any instance of the database was open. See the Data Guard documentation for details on the DG_CONFIG attribute.
- If the current instance was not open, then the protection mode could not be modified if any other instance was open.
- Once the database instance was opened, directly upgrading from MAXIMUM PERFORMANCE mode to MAXIMUM PROTECTION mode was not allowed, even if the DG_CONFIG attribute was defined. Instead, upgrade first to MAXIMUM AVAILABILITY protection mode, and wait until there was at least one synchronized destination before attempting to move to MAXIMUM PROTECTION mode. To determine if there were any synchronized destinations, refer to the Data Guard documentation.
Action
Retry the operation after addressing the applicable issues as described in the Cause.