Which two statements are true for Data Guard environmen…

Which two statements are true for Data Guard environments with multi-tenant databases?

Which two statements are true for Data Guard environments with multi-tenant databases?

A.
DB_UNIQUE_NAME must be specified differently for each pluggable database within a multitenant standby database.

B.
Each pluggable database within a multi-tenant physical standby database has a minimum of one associated Oracle Net service name.

C.
Each pluggable database within a multi-tenant physical standby has one MRP background process running during redo apply.

D.
A pluggable database within a multi-tenant standby database can have a different open mode than the container database

E.
A pluggable database within a multi-tenant standby database can have a different database role than the container database.



Leave a Reply 5

Your email address will not be published. Required fields are marked *


Wim J

Wim J

A can not be correct, as this parameter is not pdf modifiable, see below
C is not correct, MRP is at instance level
E is not correct, role (primary/stdby) is at instance level

D: correct (cdb can be read only (real time query), but a pdb can be mounted)
B? each pdb gets a dedicated service, as per default in multitenancy.

1.74 DB_UNIQUE_NAME
Property Description
Parameter type

String

Syntax

DB_UNIQUE_NAME = database_unique_name

Default value

Database instances: the value of DB_NAME

Oracle Automatic Storage Management instances: +ASM

Modifiable
No

Modifiable in a PDB
No

Basic
Yes

Oracle RAC
Multiple instances must have the same value.

JFK

JFK

Agree on B, D

edge

edge

Hi Wim J

Agree with you

I will say B and D

Regards

Chunn

Chunn

B, D

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

http://www.oracle.com/technetwork/articles/database/multitenant-part1-pdbs-2193987.html

When you create a PDB, Oracle automatically adds it as a service in the listener. You can confirm it by looking at the listener status:

[oracle@prosrv1 trace]$ lsnrctl status
LSNRCTL for Linux: Version 12.1.0.1.0 – Production on 24-FEB-2013 12:20:14
Copyright (c) 1991, 2013, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
————————
Alias LISTENER
Version TNSLSNR for Linux: Version 12.1.0.1.0 – Production
Start Date 19-FEB-2013 21:09:05
Uptime 4 days 15 hr. 11 min. 9 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File
/u02/app/oracle/product/12.1.0/grid/network/admin/listener.ora
Listener Log File
/u02/app/oracle/diag/tnslsnr/prosrv1/listener/alert/log.xml
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=prosrv1.proligence.com)(PORT=1521)))
Services Summary…
Service “+ASM” has 1 instance(s).
Instance “+ASM”, status READY, has 1 handler(s) for this service…
Service “CONA” has 1 instance(s).
Instance “CONA”, status READY, has 1 handler(s) for this service…
Service “CONAXDB” has 1 instance(s).
Instance “CONA”, status READY, has 1 handler(s) for this service…
Service “pdb1” has 1 instance(s).
Instance “CONA”, status READY, has 1 handler(s) for this service…
The command completed successfully
The service “pdb1” actually points to the PDB called PDB1. It’s very important to note that that this is not a service name in initialization parameter of the database, as you can see from the service_names parameter of the database.

JorgeZG

JorgeZG

B and D are Good !