Notes on Secondary Data Files (CLOB Data)

Secondary data file is loaded simultaneously with the primary data file. The CLOB data extract should contain exactly the same number of records as a primary file.

Note:

When splitting the extract into multiple data files, make sure that the numbers of extracted records in the primary and secondary files are matching.

It is applicable for both table-level and maintenance-object level load.

Sample Scenario:

Table CI_​​PER includes CLOB column C1_​​PER_​​DATA_​​AREA.The CLOB field is used to store customer’s resume.

The legacy table contain 10K records and the CLOB data is available for some of the records

The primary data file, CI_​​PREM.csv contains 10K lines, one line per record

The secondary data file, CI_​​PREM_​​CLOB, contains 10K records too. The records with the empty CLOB are represented by CLOB delimiter.

The CLOB data extract contains exactly the same number of records as a primary file. The application loads the Secondary data file simultaneously with the primary data file.

Splitting single table data extract with CLOB

The following example illustrates how to split the single table large volume extract correctly if the CLOB data is supplied in the secondary file:

Assuming the table has 10K records, split into two equal parts. The following files should be created:

  • Primary File 1 with 5K records

  • Secondary File 1 with 5K CLOB entries

  • Primary File 2 with 5K records

  • Secondary File 2 with 5K CLOB entries

Splitting maintenance object data extract with CLOB

The following example illustrates how to split the maintenance object large volume extract correctly if the CLOB data is supplied in the secondary file:

Assuming the maintenance object has two tables, one of the tables includes CLOB column and the primary table has 10K records. The data supposed to be split into two equal parts. The following files should be created:

  • Primary File 1 with 5K records for the primary table and corresponding records for the child table

  • Secondary File 1 with CLOB entries corresponding to the table in the Primary File 1

  • Primary File 2 with 5K records for the primary table and corresponding records for the child table

  • Secondary File 2 with CLOB entries corresponding to the table in the Primary File 2

Note:

For Maintenance Object-level load consider supplying CLOB data in the primary file, to avoid complicated logic of data splitting.

Refer to CLOB Data - XML for limitations concerning XML CLOB data