Home > Workload Solutions > Oracle > White Papers > Dell PowerMax 2500 and 8500 Best Practices for Mission Critical Oracle Databases > Review of storage allocations after the copy
Once the copy operation completes, the SLOB tablespace was copied to the new PDB (‘auxpdb’) with a size of 1,355 GB.
SQL> alter session set container=auxpdb;
Session altered.
SQL> select tablespace_name, file_name, bytes/1024/1024/1024 GB from dba_data_files;
TABLESPACE FILE_NAME GB
---------- -------------------------------------------------------------------------------- ----------
SYSTEM +AUX_DATA/system1.dbf .300003052
SYSAUX +AUX_DATA/sysaux1.dbf .300003052
UNDOTBS1 +AUX_DATA/undotbs1.dbf 10
UNDOTBS2 +AUX_DATA/undotbs2.dbf 10
UNDOTBS3 +AUX_DATA/undotbs3.dbf 10
UNDOTBS4 +AUX_DATA/undotbs4.dbf 10
SLOB +AUX_DATA/SLOB/EDEDD79C60157B44E053FBF4E40A4C85/DATAFILE/SLOB.262.1121344145 1355
7 rows selected.
Looking at the two storage groups shows that only 3.2 GB of new data was added after the copy, demonstrating the dedupe activity that took place:
symcfg -sid 304 list -sg_compression -by_compressibility -all
S T O R A G E G R O U P S
Symmetrix ID: 000120200304
Name : SRP_1
Flags Number Effective Physical Estimated
Storage Group Name C Devices Used (GB) Used (GB) Ratio
----------------------------------------------------------------------
OraRAC_DB_data X 32 1402.3 27.7 26.3:1
OraAux_data X 8 1395.8 27.8 26.3:1
OraRac_GI . 3 1.0 1.0 22.4:1
…
Legend:
Flags:
(C)ompression X = Compression Enabled, . = N/A