Starting with 18c is possible to duplicate one PDB from an active database. This is a cool feature that helps a lot in daily activities. But recently I got one error when the destination is using ASM, and the files (of course) are managed using OMF. The solution is simple and is related to a bug that is affecting the 18c, 19c, and 21c versions.
Duplicating pluggable databases can be done for a long time and have some rules. But the duplicate PDB from an active database to a new CDB helps a lot because everything can be done online. We don’t need to create an intermediate CDB to export this PDB doing the unplug/plug, or cloning the source locally to read-only PDB and create a new one using dblink, or even using rman backups.
Current Environment
My current environment is:
- Source CDB: ORAS19C.
- Destination CDB: ORAB19C.
- PDB that will be duplicated: PDBS19C.
- Version: 19.14 for all CDB’s.
- All (source and target) use ASM (+DATA and +RECO for both sides) and OMF to manage the files.
- Databases are not encrypted.
Cloning process
Requirements
The destination needs to have tnsnames pointing to all CDB’s:
[oracle@bronzen1 ~]$ tnsping ORAB19C TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 27-MAR-2022 13:53:10 Copyright (c) 1997, 2021, Oracle. All rights reserved. Used parameter files: Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = bronze-scan)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = orab19c))) OK (0 msec) [oracle@bronzen1 ~]$ [oracle@bronzen1 ~]$ tnsping ORAS19C TNS Ping Utility for Linux: Version 19.0.0.0.0 - Production on 27-MAR-2022 13:53:17 Copyright (c) 1997, 2021, Oracle. All rights reserved. Used parameter files: Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = silver-scan)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = oras19c))) OK (10 msec) [oracle@bronzen1 ~]$
And the remote_recovery_file_dest parameter needs to be set at destination CDB (point to some path or – in this case – ASM diskgroup):
SQL> show parameter REMOTE_RECOVERY_FILE_DEST NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ remote_recovery_file_dest string SQL> SQL> alter system set remote_recovery_file_dest = '+RECO' scope = both sid = '*'; System altered. SQL>
Cloning and the error
So, with all defined we can try to clone. In this case, both use ASM and the diskgroups names are the same (+DATA and +RECO). So, we don’t need to use DB_FILE_NAME_CONVERT to convert files, and since all the names are generated automatically due to the OMF the command will be simpler.
To do that we connect as TARGET to the source CDB, and as AUXILIARY to the destination CDB (CDB that will receive the new PDB):
[oracle@bronzen1 ~]$ rman target=sys/oracle@ORAS19C auxiliary=sys/oracle@ORAB19C Recovery Manager: Release 19.0.0.0.0 - Production on Sun Mar 27 14:06:11 2022 Version 19.14.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORAS19C (DBID=2948429743) connected to auxiliary database: ORAB19C (DBID=1895927860) RMAN>
And we call the duplicate:
RMAN> RUN{
2> DUPLICATE PLUGGABLE DATABASE pdbs19c AS pdbs19c TO orab19c
3> FROM ACTIVE DATABASE
4> NOFILENAMECHECK
5> SECTION SIZE 100M;
6> }
Starting Duplicate PDB at 27/03/2022 14:07:36
using channel ORA_AUX_DISK_1
current log archived
duplicating Online logs to Oracle Managed File (OMF) location
duplicating Datafiles to Oracle Managed File (OMF) location
current log archived
contents of Memory Script:
{
sql clone 'alter database flashback off';
set newname for clone datafile 10 to new;
set newname for clone datafile 11 to new;
set newname for clone datafile 12 to new;
set newname for clone datafile 13 to new;
set newname for clone datafile 14 to new;
set newname for clone datafile 15 to new;
restore
from nonsparse section size
100 m clone foreign pluggable database
"PDBS19C"
from service 'ORAS19C' ;
}
executing Memory Script
sql statement: alter database flashback off
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 27/03/2022 14:07:57
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:00
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441281' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 10 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441281' contains an invalid file number
continuing other job steps, job failed will not be re-run
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441283' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 11 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441283' contains an invalid file number
continuing other job steps, job failed will not be re-run
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441285' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 12 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441285' contains an invalid file number
continuing other job steps, job failed will not be re-run
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441287' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 13 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441287' contains an invalid file number
continuing other job steps, job failed will not be re-run
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441289' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 14 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441289' contains an invalid file number
continuing other job steps, job failed will not be re-run
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441291' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 15 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441291' contains an invalid file number
continuing other job steps, job failed will not be re-run
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate PDB command at 03/27/2022 14:08:01
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441291' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 15 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441289' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 14 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441287' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 13 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441285' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 12 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:01
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441283' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 11 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19
RMAN-03009: failure of IRESTORE command on ORA_AUX_DISK_1 channel at 03/27/2022 14:08:00
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19C/DATAFILE/.276.1100441281' contains an invalid file number
ORA-19660: some files in the backup set could not be verified
ORA-19661: datafile 10 could not be verified
ORA-19504: failed to create file "+DATA"
ORA-17502: ksfdcre:4 Failed to create file +DATA
ORA-15122: ASM file name '+DATA/ORAB19
RMAN>
As you can see above we got errors. First, check above that datafiles and online logs uses OMF as location, so the files will be generated automatically. But even with that, we got errors like:
- ORA-19504: failed to create file “+DATA”.
- ORA-17502: ksfdcre:4 Failed to create file +DATA.
- ORA-15122, ORA-19660, and ORA-19661.
And you can see in the report above that the error is clear because ORA-15122 shows that the generated OMF file became wrong: ORA-15122: ASM file name ‘+DATA/ORAB19C/DATAFILE/.276.1100441281’ contains an invalid file number.
And we can try several changes (but all will have the same result – you can click and see the outputs):
- Removing NOFILENAMECHECK.
- Changing the PDB name and cloning with a new name at target.
- Use the DB_FILE_NAME_CONVERT to change the CDB name.
- Dedicated rman channels are set manually.
Cloning correctly
So, the error is related to BUG 32606531 – ASM FILESYEM: RESTORE FOREIGN TABLESPACE/PDB FROM SERVICE SECTION SIZE IS FAIING BUT SUCCESSFULL WITH NON-MULTISECTION. So, the error is the SECTION SIZE defined at the command. If we remove it the duplicate occurs correctly:
RMAN> RUN{
2> DUPLICATE PLUGGABLE DATABASE pdbs19c AS pdbs19c TO orab19c
3> FROM ACTIVE DATABASE;
4> }
Starting Duplicate PDB at 27/03/2022 14:36:44
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=67 instance=orab19c1 device type=DISK
current log archived
duplicating Online logs to Oracle Managed File (OMF) location
duplicating Datafiles to Oracle Managed File (OMF) location
current log archived
contents of Memory Script:
{
set newname for clone datafile 10 to new;
set newname for clone datafile 11 to new;
set newname for clone datafile 12 to new;
set newname for clone datafile 13 to new;
set newname for clone datafile 14 to new;
set newname for clone datafile 15 to new;
restore
from nonsparse clone foreign pluggable database
"PDBS19C"
from service 'ORAS19C' ;
}
executing Memory Script
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 27/03/2022 14:37:02
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring foreign file 10 to +DATA/ORAB19C/DB323639F62F0B70E0530A08A00A42BE/DATAFILE/system.276.1100443025
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:35
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring foreign file 11 to +DATA/ORAB19C/DB323639F62F0B70E0530A08A00A42BE/DATAFILE/sysaux.277.1100443061
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:35
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring foreign file 12 to +DATA/ORAB19C/DB323639F62F0B70E0530A08A00A42BE/DATAFILE/undotbs1.278.1100443097
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:16
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring foreign file 13 to +DATA/ORAB19C/DB323639F62F0B70E0530A08A00A42BE/DATAFILE/undo_2.279.1100443111
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:25
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring foreign file 14 to +DATA/ORAB19C/DB323639F62F0B70E0530A08A00A42BE/DATAFILE/users.280.1100443137
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring foreign file 15 to +DATA/ORAB19C/DB323639F62F0B70E0530A08A00A42BE/DATAFILE/tbs01.281.1100443139
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:01:05
Finished restore at 27/03/2022 14:40:02
contents of Memory Script:
{
set archivelog destination to '+RECO';
restore clone force from service 'ORAS19C'
foreign archivelog from scn 2637314;
}
executing Memory Script
executing command: SET ARCHIVELOG DESTINATION
Starting restore at 27/03/2022 14:40:03
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=41
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=42
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=1 sequence=43
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=2 sequence=27
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=2 sequence=28
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=2 sequence=29
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
channel ORA_AUX_DISK_1: starting archived log restore to user-specified destination
archived log destination=+RECO
channel ORA_AUX_DISK_1: using network backup set from service ORAS19C
channel ORA_AUX_DISK_1: restoring archived log
archived log thread=2 sequence=30
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
Finished restore at 27/03/2022 14:40:12
Performing import of metadata...
Finished Duplicate PDB at 27/03/2022 14:40:51
RMAN>
So, removing SECTION_SIZE solved the issue. Even if you try different values for section size (like 400M, 10M, 1G) you will get the error. The solution is not to use it.
Conclusion
Be careful when cloning PDB from an active database and you got errors related to filename generation. Until the bug is solved, please avoid using SECTION_SIZE. Since the bug is not open is not clear what the affected releases are, but I got the same error from 19.10, 19.11, and 19.14. Probably most of the versions (18c, 19c, and 21c) are affected.
Disclaimer: “The postings on this site are my own and don’t necessarily represent my actual employer positions, strategies or opinions. The information here was edited to be useful for general purposes, specific data and identifications were removed to allow reach the generic audience and to be useful for the community. Post protected by copyright.”
Hello Fernando,
Recently I hit probably the same with when I tried to do transport tablespace with section size parameter.
Backup created with this parameter was not possible to restore on 19.8. Every time I had ORA-19563: datafile header validation failed.
I restored it on ASM, ext3, ext4 and xfs, every time was the same.
It works on 19.14 even when source in was 12.2 or 19.8.
We needed to remove section size parameter from backup 8TB bigfile tablespace for TTS.
Section size parameter is nice improvement but sometimes does not work.
Regards
Witek
Hi Fernando,
As I told you on Linkedin, thanks for sharing this information, since not being able to use the Section Size option in large PDBs that use Big File tablespaces with files of several terabytes is an important limitation to keep in mind.
We could cook up some solution to improve the performance of the duplicate operation, especially for projects in Exadata environments with hundreds of terabytes.
It might work, use the duplicate at the CDB level, filtering the PDB to duplicate.
Example:
1. Create the auxiliary intance (orac19c) to support a new CDB with only the PDB to duplicate.
2. RMAN>
RUN{
2> DUPLICATE DATABASE TO orac19c PLUGGABLE DATABASE pdbs19c;
3> FROM ACTIVE DATABASE
4> NOFILENAMECHECK
5> SECTION SIZE 100M;
6> }
Of course, doing this we have to manually create the auxiliary instance to create a new CDB, init.ora,enable_pluggable_database=TRUE, orapw etc.
Well, if this works, (you have to try it), but I think that the duplicate DATABASE command must be free of this bug that you mention. Once the PDB is duplicated in this new CDB, we can do an unplug/plug operation to the orac19c CDB.
Well, if this works, (you have to try it), but I think that the duplicate DATABASE command must be free of this bug that you mention. Once the PDB is duplicated in this new CDB, we can do an unplug/plug operation to the orac19c CDB.
It’s an idea, I haven’t tested it.
Best Regards
Arturo
Hi,
Yes, it works and I already used it several times.
The point is, as you wrote, you need to create one intermediate CDB (besides the preparation for init and other things) and this was not desired in this particular case.
The direct clone of PDB is faster because we don’t need to prepare this intermediate CDB, is just a simple command to duplicate PDB directly.
The idea of the post was to share the information about the issue with SECTION SIZE in this particular command.
Best regards.
Fernando Simon
Simon, this is perfect and easiest time saving steps as we no need the backup as well, backup it’s takes huge time if we have multi terabytes databases as I use to refresh one is around 15 TB. The only issue is if we have both the source and target is in different data center and we can’t enable direct connection in that case we need to follow the backup duplicate database restore to container and plugin/plug out method.