Database Growth

The PCA application does not support growth of the Session or Binding databases after the P-DRA or OC-DRA functions are enabled.

Note: The percentages of different types of Policy Diameter messages in the overall Policy Diameter traffic load is referred to as the call model.

This has the following implications:

The number of Server Groups that will host the Session database for each mated pair (or single site if no mated pair is planned) must be determined prior to P-DRA or OC-DRA functions being enabled.
The number of Session Server Groups required depends on the expected Diameter traffic rate in MPS for PCA signaling and the ratio of Diameter MPS to Session stack events determined by the call model.
The number of Policy Binding database Server Groups for the entire planned PCA network must be determined prior to P-DRA or OC-DRA functions being enabled.
The number of Policy Binding Server Groups required depends on the number of Policy subscribers and the expected Diameter traffic rate in MPS for Policy signaling and the ratio of Diameter MPS to Binding stack events determined by the call model.
After the number of Policy Binding and Policy Session Server Groups has been configured and the function(s) is/are enabled, these numbers cannot be changed without disable the function(s).
Disabling the P-DRA function truncates all the Policy related tables and frees the policy database parts on Binding SBR and Session SBR, resulting in an outage for all Policy signaling that traverses all PCA DSRs in the PCA network.

Disabling the OC-DRA function truncates all the Online Charging related tables and free the Online Charging database parts on Session SBR, resulting in an outage for all Online Charging signaling that traverses all PCA DSRs in the PCA network.

Deactivation of the Policy DRA feature results in an outage for all Policy and Charging signaling that traverses all PCA DSRs in the PCA network.