41.1.1.2 Parameter Specification
In this step, the following parameters are associated with Rule Types and/or Rule Names:
Figure 41-6 Parameter Specifications on Process Tuning Option Summary page
Partition Type
Partition Type selection is required when table partitioning is used within your instrument tables. This drop-down list displays the following values:
Table 41-3 Partition Codes
|
Partition Type Code |
Description |
| 0 | Single |
| 1 | Cooperative |
| 2 | Dedicated |
If no partitioning is required, then the default selection of “Single” should be selected. If partitioning is required, then users should select either Dedicated or Cooperative. For more information on these selections, refer to the Multiprocessing Options > Unit of Work servicing section
Number of Processes
The number of process selection indicates the number of concurrent subprocesses to be launched by the engine. Typically, the number of subprocesses should be less than or equal to the number of CPUs available on the server. Experiment with the number of processes setting to find the optimal value.
Array Row Size and Commit Frequency
The number in the Array Row Size column sets the number of updates sent to the database. Commit Frequency is the number of rows after which the process commits changes.
The array update enables users to specify the number of rows updated using a single cursor. Array updating accumulates updated rows during processing until the defined update frequency is reached and then sends the updates to the database for processing.
You must do some trials to set these at the optimal level. Commit frequency can be set as 999 and arraysize rows as 500. Setting the array update size to be greater than the commit frequency does not affect because the array update size is limited by commit frequency.
Oracle recommends the following to set commit frequency forALM:
- If only Process Cash Flow writing is applicable as part of process definition then use Commit Frequency optimally greater than 0.
- If Process Cash Flow writing is not applicable but output to
RES_DTL, CONS_DTL,and so on as part of process definition then the Commit Frequency should be set to 0 if the commit is required at end of unit-of-work. - If both Process Cash Flow and output to
RES_DTL, CONS_DTLare applicable then set Commit Frequency greater than 0 to see the benefits of Process Cash Flow Bulk Processing. If the commit is required at end of unit-of-work then set it to 0.