Modify Input Files for Partitioned Tables

This topic is part of Preparing Your Data for Conversion to UTC.

As the UTC conversion utility processes input files, it typically processes each table as a whole. However, tables with very large record counts might encounter errors due to constraints on log space at the database level.

The UTC conversion utility prevents errors that could occur due to insufficient log space at the database level, by using multiple input files to partition large tables into subsets of records for processing. The utility updates each record set individually to convert all of the rows in a partitioned table.

The UTC conversion utility uses partition keys to control how a table is divided into record sets. For example, large tables might be divided based on the calendar month in which each record was created, resulting in twelve approximately equal-sized partitions.

Partition keys are supplied for tables that are typically very large and that generally use a lot of log space if updated as a single input file. The following tables are delivered with partition keys:

• S_CAMP_CON

• S_COMMUNICATION

• S_EVT_ACT

• S_SRV_REQ

• S_ORG_EXT

• S_CONTACT

The default value for each key is customizable. You determine the way that your tables are partitioned, and you can partition your own tables that you know to have large record counts by adding or modifying the input files.

Note: If you create additional partitioned files, then you might decrease performance. If you require a different partitioning method, or if you want reduced partitioning in order to optimize performance, then create a service request (SR) on My Oracle Support. Alternatively, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle’s Application Expert Services.

The input file includes a WHERE clause, which defines the parameters that will be used as partition keys to divide large tables into appropriately sized sections. This WHERE clause represents standard SQL that will be used to filter which records are to be updated by each input file. Verify that you are using the correct SQL syntax.

The following example is from the file s_evt_act_00.inp. This particular file is used to define one partition of the activities table that includes all of the records created in the month of January (the month indicated by 1) or February (the month indicated by 2).

[S_EVT_ACT]
Clause = where month(CREATED) = 1 or month(CREATED) = 2
Column = APPT_START_DT, CREATED_BY
Column = TODO_ACTL_END_DT, CREATED_BY
Column = TODO_ACTL_START_DT, CREATED_BY
Column = TODO_AFTER_DT, CREATED_BY
Column = TODO_DUE_DT, CREATED_BY
Column = TODO_PLAN_END_DT, CREATED_BY
Column = TODO_PLAN_START_DT, CREATED_BY

Note: If the WHERE clause is blank, then the table will not be partitioned, and will be processed as a whole.