You can still reuse your existing scripts for these operations, with some minor tweaks, even after you have moved to the multitenant architechture.
My target server is called prodserver
My auxiliary server is called testserver
On prodserver, the container database is called "cdb" and for the time being, there is only one pluggable database running there, called "pdbprod", as shown below:
orasoft@prodserver:[pdbprod] sqlplus / as sysdba SYS@CDB$ROOT SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 pdbprod READ WRITE NOOn my auxiliary server testserver, I also have a container database called "cdb", and a PDB called "pdbtest":
orasoft@testserver:[pdbtest] sqlplus / as sysdba SYS@CDB$ROOT SQL> show pdbs CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 pdbtest READ WRITE NOFirst, I recommend to configure a wallet, to avoid exposing your passwords in scripts or in on the Linux shell prompt.
Add a global user that exists in both container database and make sure it has SYSDBA privileges.
In this example, I add a user called c##cloneadmin and use the alias "cdbprod" and "cdbtest" for both:
mkstore -wrl $TNS_ADMIN/wallet -createCredential cdbprod c##cloneadmin mkstore -wrl $TNS_ADMIN/wallet -createCredential cdbaux c##cloneadminAdd the connect descriptions to your tnsnames.ora file, on both source and target.
Make sure the passwordless connections work before you attempt cloning. Test like this:
rman connect target /@cdbprod connect auxiliary /@cdbaux run{ allocate channel c1 type disk; allocate channel c2 type disk; allocate auxiliary channel aux1 type disk; allocate auxiliary channel aux2 type disk; } exitDo not proceed until you connect successfully to both.
Create a minimal initcdb.ora file, containing only these two parameters:
*.db_name='cdb' *.enable_pluggable_database=TRUEStartup your auxiliary container database in nomount mode using the initcdb.ora file above:
sqlplus / as sysdba startup nomount pfile=initcdb.oraCreate an RMAN script for your duplication, in my example I put it in a file called run_duplication.cmd:
connect target /@cdbprod connect auxiliary /@cdbaux run{ allocate channel c1 type disk; allocate channel c2 type disk; allocate auxiliary channel aux1 type disk; allocate auxiliary channel aux2 type disk; configure device type disk parallelism 2; debug io; DUPLICATE DATABASE TO cdb FROM ACTIVE DATABASE USING BACKUPSET SPFILE set db_file_name_convert='pdbprod','pdbtest' set audit_file_dest='/oraadmin/oracle/admin/cdb/adump' set core_dump_dest='/oraadmin/oracle/diag/rdbms/cdb/cdb/cdump' set control_files='/dbfiles01/oradata/CDB/control01.ctl','/dbfiles02/fra/CDB/control02.ctl' set sga_target='33621540864' set sga_max_size='33621540864' set pga_aggregate_target='12773752832' set shared_pool_size='2751463424' set streams_pool_size='268435456' set service_names='cdb,pdbtest' set db_recovery_file_dest_size='3221225472000' NOFILENAMECHECK ; debug off; } exitRemember that the NOFILENAMECHECK is required when using the same data file names but on different hosts. Without it, RMAN throws the error below and aborts your script:
RMAN-05001: auxiliary file name /dbfiles02/oradata/CDB/undotbs01.dbf conflicts with a file used by the target databaseCreate a shell script that calls the RMAN script, for example run_duplication.sh:
rman cmdfile='run_duplication.cmd' debug trace='duplicate.trc' log='duplicate.log'Make the script executable, and execute it. If the source database is very large, and you expect the duplication to take more than 2-3 hours, you may want execute it in the background:
chmod 755 run_duplication.sh nohup ./run_duplication.sh &When the duplication was finished, the cdb + pdbprod was opened on the remote server. The last lines of the logfile states:
RMAN-06400: database opened
RMAN-06162: sql statement: alter pluggable database all open
RMAN-03091: Finished Duplicate Db at 29-APR-23
Sources:
Duplicating a CDB from the Oracle 19c documentation.