Partitioning is not an good option for highly OLTP database.
You need to identify top resource-consuming
SQL statements and see if they can benefit from partitioning corresponding tables. The types of queries that benefit
from table partitioning include full table scans, joins between several large tables and index range scans, which return
relatively large percentage of rows. On the other hand when the index scan returns only a handful of rows the table
partitioning will not bring significant benefits, because these few rows will be accessed by rowid. The latter situation
can be a candidate for index partitioning even when the table itself is not partitioned. The main performance gain is
in I/O reduction while traversing the B*Tree indexes. Only indexes on very large tables can produce sizable gains,
because the I/O reduction can only occur when the height of the index is reduced.

thanks
GP