Any errors encountered while processing the file are logged in the error log file of the PDBA. The
processing of the import file continues. When the file is completely processed, the user interface
displays a warning that errors were encountered. The error log file of the PDBA can then be viewed
through the EPAP user interface. (For more information, refer to the EPAP Administration Manual.)
Commands in the import file are handled as though they were received across a normal PDBI
connection. It is important that dependencies are listed in the file in the correct order. For example, if
a DN is to be created and assigned to a specific NE (either SP/RN), that NE must exist before the DN
can be created. The NE could either already exist in the database before the import file was sent, or it
could be created in the import file before any DNs that need it.
Since there is limit to the number of commands that can be contained in a single transaction (see
Transaction Too Big Response), the PDBA may have to break up the import into several separate
transactions. This is handled internally in the PDBA. The user may notice only that the database level
has grown by more than one.
Blank lines and lines beginning with the '#' character are skipped.
If any PDBI commands other than the six mentioned above are placed in an import file, each occurrence
generates a BAD_IMPORT_CMD error internally while parsing the file. The total import error count is
incremented, and the processing of the import file continues with the next line. The BAD_IMPORT_CMD
return code never actually is returned to the PDBI client, but it may be seen in the PDBA error log file.
Export File
It is possible to export the contents of the PDB to an ASCII file. Perform this through the Export option
on the EPAP user interface. (For more information, refer to the EPAP Administration Manual.) The
data can be formatted in two ways, either as PDBI commands or as raw delimited ASCII.
Three modes of export are supported in the EPAP software. Depending on the mode of export selected,
the EPAP may be blocked from performing database updates or allowed to provision new data and
data retrieve operations on the EPAP provisioning database PDB) during the export.
EPAP provides the following modes of operation:
• Blocking mode
The Blocking mode blocks write requests to the EPAP database during a database export. Writes
will not be allowed until the export completes.
• Snapshot mode
Note: This mode causes the server to run increasingly slower as updates are received on the other
connections.
The Snapshot mode allows write operations on the database during a database export. This mode
provides the exported database as a complete snapshot of the database at the time the export started.
This implies that changes to the database after the export started are not reflected in the exported
database. This allows for a logically complete export file.
• Real Time mode
The Real Time mode allows write operations during a database export, and provides the export
file in real-time fashion rather than as a snapshot. Changes to the DB after the export has started
may or may not be reflected in the export file, depending whether the changes are to an area of the
DB that has already been exported. This mode also provides a file that could be imported back into
the database later, but is less than ideal, since it is not a complete snapshot of a given time. As an
34
910-6022-001 Revision A, March 2011
Functional DescriptionProvisioning Database Interface Manual
To Next Page
Loading...
