Which three steps are prerequisites for the creation of a physical standby database on a separate server using the RMAN active database duplication method?
A.
Set the DB_UNIQUE_NAME parameter on the primary database to a different value than that of the DB_NAME parameter.
B.
Put the primary database into archivelog mode.
C.
Startup nomount the standby database instance.
D.
Configure Oracle Net connectivity on the primary host to the standby database instance.
E.
Establish user equivalence for the database software owner between the primary host and standby host.
Explanation:
C: Shut down and restart the auxiliary database instance on the destination host in NOMOUNT mode.
D: When a database must be accessed from another host, you must set up a password file and Oracle Net connectivity.
E: When instructed to connect to the necessary instances, connect to the root as a user with SYSDBA or SYSBACKUP privilege. On both instances, the password
for the user performing the duplication must be the same.https://docs.oracle.com/database/121/BRADV/rcmdupdb.htm
incorrect answers!
E: the pwd file must be the same (same pwd for e.g. sys-user). The software owner is not needed to be the same!
beter: A, C, D. However (I think): A is not a must if you’re running on a different host
BCD. Creating a standby without having archivelogs enabled makes no sense.
Agree that given answer is incorrect.
A – FALSE. not required if standby on a different server.
B – TRUE. Not possible to do active database duplication unless running in archivelog mode
C – TRUE. Nothing exists on the standby side except the SPFILE and password file.
D – TRUE. Primary must be able to connect to Standby in order to do anything.
E – FALSE. Software owner only matters locally. Primary connects via Oracle net using SYS credentials. This is only equivalence required.
Correct: A,B,C,D
E.2.2.2 DB_UNIQUE_NAME Values in an RMAN Environment
A database in an Oracle Data Guard environment is uniquely identified by means of the DB_UNIQUE_NAME parameter in the initialization parameter file. The DB_UNIQUE_NAME must be unique across all the databases with the same DBID for RMAN to work correctly in an Oracle Data Guard environment.
A – DB_UNIQUE_NAME change is not on primary, but on the Standby Databases!
E.3.1 Creating a Standby Database with Active Database Duplication
The following example illustrates how to use DUPLICATE for active duplication. This example requires the NOFILENAMECHECK option because the primary database files have the same names as the standby database files. The SET clauses for SPFILE are required for log shipping to work properly. The db_unique_name must be set to ensure that the catalog and Oracle Data Guard can identify this database as being different from the primary.
DUPLICATE TARGET DATABASE
FOR STANDBY
FROM ACTIVE DATABASE
DORECOVER
SPFILE
SET “db_unique_name”=”foou” COMMENT ”Is a duplicate”
SET LOG_ARCHIVE_DEST_2=”service=inst3 ASYNC REGISTER
VALID_FOR=(online_logfile,primary_role)”
SET FAL_SERVER=”inst1″ COMMENT “Is primary”
NOFILENAMECHECK;
BCD is correct.
agree with BCD
B,C,D