I think CG http://ora-srv.wlv.ac.uk/oracle19c_doc/multi/introduction-to-the-multitenant-architecture.html#GUID-47847140-8DE4-4C4E-8C93-4E9C197D1402
A, B incorrects -> http://ora-srv.wlv.ac.uk/oracle19c_doc/multi/introduction-to-the-multitenant-architecture.html#GUID-47847140-8DE4-4C4E-8C93-4E9C197D1402
C correct, D,E,F incorrect -> https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/cloning-a-pdb.html#GUID-B00A0E48-C892-4DC8-8455-C6F2ABC8EF91
G -> correct -> A clone from a PDB snapshot is a full, standalone PDB. -> https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/cloning-a-pdb.html#GUID-22118625-3157-4C38-8A88-79A561A3E6ED
I'm sure of CG after looking at https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/cloning-a-pdb.html#GUID-F26C8A55-2465-475A-905A-83BD2E68AE6E
First of all they are talking about 19c+ versions. In 19c docs they say:
A PDB snapshot is a point-in-time copy of a PDB. The source PDB can be open read-only or read/write while the snapshot is created. You can create snapshots manually using the SNAPSHOT clause of CREATE PLUGGABLE DATABASE (or ALTER PLUGGABLE DATABASE), or automatically using the EVERY interval clause. If the storage system supports sparse clones, then the preceding command creates a sparse copy. Otherwise, the command creates a full copy.
So, A and B are false from my point of view.
indeed A, B are false as you argumented well
in my opion, correct answer C, G
G:
https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/cloning-a-pdb.html#GUID-F26C8A55-2465-475A-905A-83BD2E68AE6E
and then create a SNAPSHOT COPY PDB from the standalone PDB.
C:
Storage requirements depend on the setting of the CLONEDB initialization parameter:
CLONEDB=FALSE
The underlying file system for the source PDB files must support storage snapshots. Such file systems include Oracle Automatic Storage Management Cluster File System (Oracle ACFS) and Direct NFS Client storage. Oracle Exadata supports snapshot copy functionality on ASM configured with sparse ASM grid disks.
CLONEDB=TRUE
The underlying file system for the source PDB files can be any local file system, network file system (NFS), or clustered file system that has Direct NFS enabled and supports sparse files. Most UNIX systems meet these requirements, including Oracle ACFS and ZFS. However, when CLONEDB=TRUE, the source PDB must remain in open read-only mode when clones exist.
Full and Sparse Snapshots
The content of snapshots generated by ALTER PLUGGABLE DATABASE ... SNAPSHOT depends on the underlying file system. If the underlying file system supports sparse copies, then the PDB-level snapshots are sparse. Only the first PDB-managed PDB snapshot is full. Otherwise, the PDB snapshots contain full copies of the data files. The snapshot includes other files necessary to create a PDB from the snapshot.
If the file system supports sparse files, then all PDB snapshots in the carousel except the first one are sparse. The source PDB can remain in read/write mode. Sparse files significantly reduce the carousel storage space.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ald85
Highly Voted 2 years, 11 months ago_gio_
Most Recent 6 days, 2 hours agohilaire
4 months, 3 weeks agoBio12345
1 year, 3 months agoCyborgQ
2 years, 10 months agojulica
2 years, 10 months agojanw
2 years, 9 months agojanw
2 years, 9 months agojulica
2 years, 10 months agoklever35
2 years, 11 months agotaotsumiau
2 years, 12 months agoveginha
2 years, 12 months ago