Problem

Customer would like to use partition tables for their webMethods DB tables.

Is that supported?

According to Customer:

We are planning to change highly utilized tables into partition tables.

Partitions can be created Daily, Weekly, Monthly and Yearly basis.

Based on table growth creating weekly OR monthly partitions will fit for Boots SAG landscape.

Partitions has to be created in advance and old partitions has to be dropped to free up DB space. Both has to be planned in advance and internal DBA team helps to implement them manually.

Let’s assume we are planning for weekly partition. We will work with DBA to create partitions manually in advance.

Oracle manages to write data belonging to specific week to corresponding partition (each week data written to separate partition) At some point old partitions (containing old SAG data) shall be dropped manually with DBA help.

Creating advance partitions for future use and removing old partitions doesn’t require SAG downtime.

But for changing normal tables to partition table we require SAG downtime and it’s one-time activity

Confirm there is no SAG functional impact because of changing these normal tables to partition tables.