Which two are prerequisites for creating a standby database using Enterprise Manager cloud control?

A.
The primary database must have FORCE LOGGING enabled.

B.
The primary database must be in archivelog mode.

C.
A backup of the primary database must exist.

D.
The primary host and the proposed standby database host must run the same operating system.

E.
The primary database instance must be started using an SPFILE.

F.
The primary database must have flashback enabled.

Explanation:
A: Before you create a standby database you must first ensure the primary database is properly configured.
Place the primary database in FORCE LOGGING mode.
B: If archiving is not enabled, issue the following SQL statements to put the primary database in ARCHIVELOG mode and enable automatic archiving:
SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE OPEN;

https://docs.oracle.com/database/121/SBYDB/create_ps.htm#SBYDB4719

Show Hint

← Previous question

Next question →

Leave a Reply 8

Wim J

A is not correct, force logging is just a best practice…
I would not recommend it, but, it’s allowed

9.3.4 Use FORCE LOGGING Mode
When the primary database is in FORCE LOGGING mode, all database data changes are logged. FORCE LOGGING mode ensures that the standby database remains consistent with the primary database. If this is not possible because you require the load performance with NOLOGGING operations, then you must ensure that the corresponding physical standby data files are subsequently synchronized. To synchronize the physical standby data files, either apply an incremental backup created from the primary database or replace the affected standby data files with a backup of the primary data files taken after the nologging operation. Before the file transfer, you must stop Redo Apply on the physical standby database.

wimj

https://docs.oracle.com/cd/E24628_01/em.121/e27046/prov_standby_database.htm#EMLCM93215

Note:
If you choose to create a new physical or logical standby database, Data Guard checks the following when you click Continue:

Server parameter file (SPFILE) — Data Guard requires that all databases in a configuration use a server parameter file (SPFILE). If the wizard encounters a primary database that does not use an SPFILE, the wizard stops and returns a message asking you to create one. You can create one with a non-default name. Data Guard only requires that the primary database uses an SPFILE.

NOARCHIVELOG mode — Regardless of what method you choose to add the standby database, the primary database must be in ARCHIVELOG mode. If the primary database is in NOARCHIVELOG mode, you will be asked to exit the wizard and put the primary database into ARCHIVELOG mode.

B, E

PeraDetlic

Correct: B,D,E

https://docs.oracle.com/cd/E24628_01/em.121/e27046/prov_standby_database.htm#EMLCM93217

The standby database can be created in any Oracle home that was discovered by Oracle Enterprise Manager. Only Oracle homes on hosts that match the operating system of the primary host are shown. You must select a discovered Oracle home and provide a unique instance name for the standby database. Standby host credentials are required to continue.

indeed, D is also correct

Enterprise Manager can not be used for standby database creation or other administrative functions in any configuration where PLATFORM_IDs are not identical. Oracle recommends using the Data Guard Broker command line interface (DGMGRL) to administer mixed platform combinations from Oracle Database 11g onward and SQL*Plus command line for configurations that pre-date Oracle Database 11g.