Data Import
This function makes it possible to integrate into a folder the data previously extracted with the aid of the extraction utility. The files in question must have been placed beforehand in a sub-directory of the integration folder (SVG by default). It consists of a physical integration (in some ways comparable to an Oracle import: the structure and all the data in the table will be replaced by the contents of the corresponding file, without the possibility to return to the previous position). For each XXX table in the database, four to six files must be present in the directory and these will be read:
- a XXX.dat file, which contains the data in the form of a file constructed of fixed length records.
- a XXX.srf file, which contains the description of the file structure (ASCII format).
- a XXX.fde file, which contains the description of the file structure (in a compiled format directly usable by the Adonix engine: This file also exists in the FIL directory of the folder).
- a XXX.blb file, which contains the data linked to the image files (BLOBS) and text files (CLOBS) stored in the table if it has any.
- a XXX.seq file, which contains the next sequence number associated with the table. This information is important insofar as each table is associated with a sequence number that makes it possible to create unique numbers (this corresponds to the Adonix function uniqid([abv]), where abv is the table abbreviation).
- a XXX.cfg file, which contains the table configuration information in the database. This file is optional, its taking into account depends in addition on the integration options selected. To have more information on the configuration file structure, it is advisable to consult the corresponding technical annex.
Legal notice
This type of function is a development function whose use is probibitted in a standard use framework.
Any legal consequences arising from the use of development tools on databases containing data which it is prohibitted by law to modify will be under the full responsibility of the customer. For further information, refer to the corresponding annex.
Refer to documentation Screen management
Entry screen
When entering the function, an entry screen is displayed used to define the data to extract and the setups applied to this extraction.
Validation starts the function, after a confirmation request in a box giving the following message:
|
|
Number of tables to be integrated: NNN |
A log file is created and viewed in order to know the result (and any possible errors in the extraction).
Block number 1
| Folder (field DOSSIER) |
|
Define the folder code, as it is defined in the folders table, in which the work will be carried out. |
| Historized (field HISTO) |
|
If the folder where the tables are integrated possesses an archive folder, there is the choice to integrate into the archive table (by checking the box) or in the table in the live folder (not checked). |
| Backup volume (field STOVOL) |
| Tables to import (field FICHIER) |
|
Defines the name of the table to be integrated or a template characterising the name of the tables to be integrated. If for example, all the tables present in the SVG directory are to be integrated, all that is necessary is to enter * in this field. |
| Reason (field MOTIVE) |
Block number 2
| Original configuration files (field CFG) |
|
When this box is checked, the file with extension cfg present in the SVG directory is used to define the table, taking into account the configuration directives such as the size of the extents. Its structure is described in an annex. |
| Size of origin (field SIZ) |
|
When this box is ticked, the sizing information (from the file with the extension srf) found in the integration directory is ignored and instead the information found in the FIL directory (if it exists) is used. |
Practical use
Technical limits
This function is linked to the adonix engine and not to the standard databases. As a consequence, it should not be used as a habitual backup procedure, since it does not have the guarantees of security or performance. A backup with the standard database tools is strongly recommended before every use of this type of function.
Amongst the limitations of this type of function, it should be noted that, if it is launched for several database tables, it can lead to a database image that is not globally coherent if updates take place during the export (unlike the standard tools associated with the databases). If the function is to be used to import all the tables extracted in a coherent way, it is necessary to ensure that nobody else is connected to the folder during the integration.
Batch task
This function can be run in batch mode. The standard task DOSINTEG is provided for that purpose.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
XXX folder
Error when accessing table AUTILIS
Non-existent file
This error message leans that the selected folder was not created or does not exist anymore (in any case, the user table could not be found in this folder).
Other error messages
At the time of the integration, a log file is created. Errors can arise: They appear in the form of an error line (in red) in the log file, followed by additional information.