Create Tablespace cdr_data_ts

Create a separate tablespace cdr_data_ts for the LOB storage. You must calculate an estimated size of the old implementation of the LOB basic file and allocate 25% more tablespace size for the tablespace cdr_data_ts. This tablespace will store the migrated secure file implementation.

1. Connect to Oracle DMW PDB as SYS or SYSTEM user.
2. Make sure there is enough space available in the ASM disk group. In case you do not use the ASM disk group, make sure there is enough disk space available at the operating system directory where the datafiles will be created.
3. Create the tablespace cdr_data_ts by executing the following command:

   CREATE TABLESPACE cdr_data_ts DATAFILE
       '<fully qualified datafile path>' SIZE 500M
       AUTOEXTEND ON NEXT 100M MAXSIZE <max size limit of the file, typically 30G on Linux OS>
       EXTENT MANAGEMENT LOCAL UNIFORM SIZE 100M SEGMENT SPACE MANAGEMENT AUTO;

   For example, assuming 30GB operating system file size limit using ASM storage "+DATA":

   CREATE TABLESPACE cdr_data_ts DATAFILE '+DATA' SIZE 500M
      AUTOEXTEND ON NEXT 100M MAXSIZE 30G
      EXTENT MANAGEMENT LOCAL UNIFORM SIZE 100M SEGMENT SPACE MANAGEMENT AUTO;

4. Add the datafiles, as required by executing the following command:
   ALTER TABLESPACE cdr_data_ts ADD DATAFILE 'fully qualified datafile name' SIZE 500M AUTOEXTEND ON NEXT 100M MAXSIZE max size limit of the file, typically 30G on Linux OS;
   For example, assuming 30GB operating system file size limit using ASM storage "+DATA":

   ALTER TABLESPACE cdr_data_ts ADD DATAFILE '+DATA' SIZE 500M
      AUTOEXTEND ON NEXT 100M MAXSIZE 30G;

5. Assign a quota for the tablespace cdr_data_ts to the user CDR and optionally to APPS.
   ALTER USER CDR QUOTA UNLIMITED ON cdr_data_ts;
   ALTER USER APPS QUOTA UNLIMITED ON cdr_data_ts;