Database partitioning is the process of splitting tables or indexes into smaller and manageable pieces. Logically there is only one table or index when the application access the database. But due to partitioning, that table or index consists of many physical partitions. Each partition is an independent object controlled either by itself or as part of the larger object.

Interval Partitioning performs Data Archival in Oracle Banking Payments. It is one of the nine schemes of partitioning in Oracle Database.

To understand the Interval Partition, take an example to archive data of 13 months. Assume that the 13 months data need to be archived quarterly. The transaction table must contain a date datatype column to perform interval partitioning of the table. Let’s call this the Booking Date column. Each time a data transaction happens, the transaction creation date goes into the Booking Date column. In the Transaction-processing tables, the partition criterion must set quarterly to segregate each quarter data into separate partitions within the same table. Therefore, for 13 months, data segregates into five different tables.