A query on the view DBA_LOGSTBY_UNSUPPORTED on your primary database returns no rows.
As a result of this, you decide that an upgrade may use logical standby databases.
Which two are true about upgrading Data Guard environments consisting of one logical standby database
running on a separate host from the primary?
A.
The upgrade always requires downtown until the upgrade of the logical standby is completed.
B.
Using manual upgrade, catctl.pl can be executed in some cases on the primary and standby database
simultaneously.
C.
The upgrade always required downtime until the upgrade of the primary is completed.
D.
Using manual upgrade, catupgr.sql needs to run on the primary database only.
E.
SQL Apply on the local standby database must be stopped while the primary database is upgraded.
F.
Fast-Start Failover can be used to protect the primary database during the upgrade.
Explanation:
B (not D): Oracle Database 12c introduces the new Parallel Upgrade Utility, catctl.pl. This utility replaces the
catupgrd.sql script that was used in earlier releases. Although you can still use the catupgrd.sql script, it is
deprecated starting with Oracle Database 12c and will be removed in future releases. Oracle recommends
database upgrades be performed with the new Parallel Upgrade Utility, catctl.pl.
E: Once the database is started in upgrade mode, only queries on fixed views execute without errors until after
the catctl.pl script is run.https://docs.oracle.com/database/121/UPGRD/upgrade.htm#UPGRD52867
https://docs.oracle.com/database/121/UPGRD/deprecated.htm#UPGRD60034
If you are using Traditional method (as below) in Logical standby then seems E & A.
I think it may be E, B
Perform the following steps to upgrade to Oracle Database 12c Release 1 (12.1) when a logical standby database is present in the configuration:
1. Review and perform the steps listed in the “Preparing to Upgrade” chapter of the Oracle Database Upgrade Guide.
2. Set the data protection mode to MAXIMUM PERFORMANCE at the primary database, if needed: SQL> ALTER DATABASE SET STANDBY DATABASE TO MAXIMIZE PERFORMANCE;
3. On the primary database, stop all user activity and defer the remote archival destination associated with the logical standby database (for this procedure, it is assumed that LOG_ARCHIVE_DEST_2 is associated with the logical standby database): SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=DEFER SCOPE=BOTH;
SQL> ALTER SYSTEM ARCHIVE LOG CURRENT;
4. Stop SQL Apply on the logical standby database:
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
5. On the primary database install the newer release of the Oracle software as described in the Oracle Database Upgrade Guide.
6. On the logical standby database, install the newer release of the Oracle software as described in Oracle Database Upgrade Guide. (Note: 5 & 6 can run in parallel)
7. On the upgraded logical standby database, restart SQL Apply. If you are using Oracle RAC, start up the other standby database instances: SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
8. Open the upgraded primary database and allow users to connect. If you are using Oracle RAC, start up the other primary database instances. Also, enable archiving to the upgraded logical standby database, as follows: SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE;
9. Optionally, reset to the original data protection mode if you changed it in Step 2.
10. Optionally, modify the COMPATIBLE initialization parameter
https://docs.oracle.com/database/121/SBYDB/upgrades.htm#SBYDB4933
B,E
B,E