Figure 1: Example EPAP/PDBA Network
Each Service Module card contains an identical database. The RTDB on the Service Module cards must
be identical to the RTDB maintained by the EPAPs. However, there are several reasons why the various
databases might not be identical. When a Service Module card is initialized, it has to download a
current copy of the B-Tree RTDB file from the EPAP. While that card is being downloaded, it cannot
be used to provide VSCCP services. Another condition that leads to the databases being out-of-sync
occurs when the EPAP processes an update from its provisioning source. These updates are applied
immediately to the Active EPAP PDB as they are received, but there is a delay before sending the
updates to each EPAP RTDB and then subsequently to the Service Module cards.
Two possible scenarios lead to the condition where a Service Module card might not have enough
memory to hold the entire database:
• The database is downloaded successfully to Service Module card, but subsequent updates eventually
increase the size of the database beyond the Service Module card memory capacity. In this situation,
17
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
