•
upd_eir
•
dlt_eir
Note: Do not include rtrv_sub, rtrv-entity, or rtrv_eir commands in an import file. The
inclusion of rtrv commands causes an import to take a very long time to complete. During an import,
a write transaction lock is in place for the entire import for a manual import, and intermittently in
place for an automatic import. While the write transaction lock is in place during an import, no other
updates to the database can be made.
Data can be imported manually or automatically, as described in the following sections:
•
Manual Import
•
Automatic Import
The syntax of the imported file data is described in Import File Syntax.
Manual Import
The manual import mode is used to import data typically on a one-time basis or as needed and is
configured by the Import File to PDB Screen. The selected file is processed immediately. A manual
import locks the PDB write transaction; other users will not be able to obtain the write transaction
until the import operation is complete.
Automatic Import
As long as the PDB is active, the automatic import searches the/var/TKLC/epap/free/pdbi_import directory
for new files on a remote system for import every 5 minutes. If a file exists in the directory and it is
not being modified or in the process of being transferred when it is polled, the import will run
automatically at that time. If the file is being modified or is in the process of being transferred, the
automatic import tries again after five minutes. Delaying when a file is being modified or in the process
of being transferred prevents the import of incomplete files.
The automatic import option can import up to 16 files at a time. This is limited by the available number
of PDBI connections. If more than 16 files exist in the directory, as soon as one file completes, another
file is started until all files have completed. The results of the import are automatically exported to
the remote system specified by the Configure File Transfer Screen (described in the EPAP Administration
Manual).
Once the import is complete, the data file is automatically removed and a results file is automatically
transferred back to the remote system. An automatic import obtains the PDB write transaction and
processes several of the import file commands. Then the write transaction is released, allowing other
connections to provision data. An automatic import obtains the write transaction repeatedly until all
the import file commands have been processed.
Automatic import is also called "Batch-oriented/bulk load" (see Batch-Oriented/Bulk Load).
Import File Syntax
There is no need to place any other commands, such as begin_txn, in the file. If the PDBI user interface
is used to send the import command, the user interface automatically handles establishing a connection
with an open write transaction. Because the import operation has the write operation throughout
its entire duration, normal updates from other PDBI users cannot obtain the write transaction until
the import operation is finished.
33
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
