Single Transaction Mode
When sending a series of single-update transactions in normal transaction mode, considerable overhead
is required for sending transaction boundary tags. Because some clients want to send only one update
per transaction, an alternative PDBI connection type is available, called 'single transaction mode.'
When using this connection type, PDBI clients can send updates outside of the 'begin' and 'end'
transaction delimiters. The PDB treats each single transaction mode update as being its own transaction.
However, transaction delimiters are not ignored in 'single mode'. If the PDBI client issues these
delimiters, the series of updates encapsulated by them are treated as one transaction, as they are been
under the default normal transaction mode. For details on the PDBI connect options, refer to the
Connect command on and the txnmode parameter.
Batch-Oriented/Bulk Load
The system can also accept batch files via FTP (File Transfer Protocol) or removable media (that is,
MO, CD-R). The preferred method is FTP.
The format of the batch file looks like a series of normal PDBI commands, such as ent_sub, dlt_sub,
etc. However, the connect/disconnect request and transaction begin/end commands are not included.
During a batch file import, transactions are handled in the same manner as with individual commands:
the write transaction must be released by the client doing the batch file import before a new write
transaction may be granted. Read transactions are always available, assuming the customer's interface
network is available. The import file can contain as many commands as the storage media used to
hold the batch file allows. The PDBA does not have a limit on the number of commands allowed.
The batch file is committed in stages; several transactions are opened to import the entire file. There
is one commit for approximately every 200 entries. Therefore, it is impossible to rollback or abort a
transaction after the import is complete. This also means that the dblevel returned at the end of the
import may be increased by several levels since each transaction would increment it. The time needed
to complete an import of a batch file depends upon several variables, including the size of the file.
Although the import is processed as a series of transactions, the write transaction is unavailable to
other clients for the entire duration of the import, that is until all transactions related to the import
have been processed.
Command Atomicity
Commands are atomic, that is, they cannot be interrupted. Once a command is begun, it is performed
completely or not at all; an atomic command cannot be partly performed or partly completed.
Consequently, if one command in a transaction fails, the results of that one command are not committed
to the database upon execution of the end_txn command. However, all the other commands in the
transaction that did execute successfully are committed upon execution of the end_txn command.
Provisioning Ranges of Subscriber Numbers
Currently, there is no method directly accessible from the PDBI for provisioning ranges of IMSIs (only
individual IMSIs are supported), but provisioning MSISDNs Blocks and IMEIs Blocks is supported.
Note that the EPAP GUI provides menus to provision IMSI Ranges, however these are not equivalent
to MSISDN Blocks or IMEI Blocks. These IMSI Ranges are not provisioned via PDBI and are not
downloaded to the EPAP RTDBs or Service Module RTDBs.
28
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
