Partitioning an Oracle database for improved performance

The high input and output associated with large volumes of data in an Oracle database can prevent the database server from effectively operating on data. Database partitioning can enhance database server performance, improving data manageability and availability.

Users are advised to work with their own DBAs to identify and implement database optimizations, including partitioning, best suited to their environment. OpenText does not validate or provide technical support for specific database optimizations or enhancements.

Before implementing database partitioning or other database optimizations, OpenText strongly recommends that you do the following:

1. Back up your database.
2. Test and validate any changes in a non-production environment before modifying your production database.

Though OpenText does not provide guidance for customer database optimizations when partitioning a database, ensure the following:

1. Number of partitions must allow for growth in your data.
2. Consider a record distribution of less than one million records per partition.
3. Partitioning a database can take time, ensure you allocate enough application downtime in order to partition the data.
4. After partitioning, consider increasing the number of job execution threads for optimization. 
   1. Job execution threads are configured in the <fortify.home>/<app_context>/conf/app.properties file by the jobs.threadCount property.
5. Partition optimizations have the possibility of conflicting with migrations scripts.  In those cases, the customer's DBA may need to manually adjust the migration scripts and/or partition scripts to work with any applied optimizations during upgrades of the product.