Which two must be true when you migrate an Oracle Database 12.1.0.2 non-CDB to a database that is running in a Database as a Service (DBaaS) instance on Oracle Cloud by using the Remote Cloning…

Question

Options

• AThe non-CDB may be opened in READ WRITE mode as long as ARCHIVELOG is enabled.
• BThe database link owner must have the CREATE PDB system privilege.
• CThe source platform must have the same endian format.
• DThe non-CDB must be in archivelog mode.
• EThe non-CDB must be opened in READ ONLY mode.
• FThe database link owner must have the CREATE PLUGGABLE DB system privilege.

• A
  4% (1)
• B
  13% (3)
• C
  4% (1)
• E
  78% (18)

Explanation

To migrate an Oracle Database 12c non-CDB database to a Database Cloud Service database deployment using the remote cloning method, you perform these tasks: 1. On the on-premises database host, invoke SQLPlus and set the on-premises database to 2. On the Database Cloud Service compute node, invoke SQLPlus and create a database link that enables a connection to the on-premises database. 3. On the Database Cloud Service compute node, execute the CREATE PLUGGABLE command to clone the on-premises non-CDB database. 4. On the Database Cloud Service compute node, execute the $ORACLE_HOME/rdbms/admin/script. noncdb_to_pdb.sql 5. On the Database Cloud Service compute node, open the new PDB by executing the ALTER PLUGGABLE DATABASE OPEN 6. Optionally, on the on-premises database host invoke SQL*Plus and set the on-premises database back to READ WRITE mode. You can use this method only if the on-premises platform is little endian, the on-premises database release is 12.1.0.2 or higher, and the on-premises database and Database Cloud Service database have compatible database character sets and national character sets. https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/mig-remote-cloning-non-

No community discussion yet for this question.