This page (revision-31) was last changed on 26-Nov-2021 10:22 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by JEscott

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
31 26-Nov-2021 10:22 13 KB Kevin Higgs to previous
30 26-Nov-2021 10:22 14 KB Karen Parrott to previous | to last
29 26-Nov-2021 10:22 14 KB Karen Parrott to previous | to last
28 26-Nov-2021 10:22 13 KB Kevin Higgs to previous | to last
27 26-Nov-2021 10:22 13 KB kparrott to previous | to last
26 26-Nov-2021 10:22 14 KB kparrott to previous | to last
25 26-Nov-2021 10:22 13 KB kparrott to previous | to last
24 26-Nov-2021 10:22 13 KB kparrott to previous | to last
23 26-Nov-2021 10:22 13 KB kparrott to previous | to last
22 26-Nov-2021 10:22 13 KB kparrott to previous | to last
21 26-Nov-2021 10:22 12 KB kparrott to previous | to last

Page References

Incoming links Outgoing links
LMTD
LMTD

Version management

Difference between version and

At line 18 changed one line
;:The first line of the file must contain the header of column names that identifies what is to be loaded. The order of data within the file must match the order in the header record. The column names can be in lower or upper case.
The first line of the file must contain the header of column names that identifies what is to be loaded. The order of data within the file must match the order in the header record. The column names can be in lower or upper case.
At line 21 changed one line
;:Within the IMST screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system, which is convenient.
Within the IMST screen, the administrator must define where the Extract and Load files are located and where the load functions are to write the exception files to. These locations are used by the functions to create and retrieve information. The customer can modify these values to represent any directory on their system, which is convenient.
At line 23 changed one line
;:The extract directory is defined using the [EXTRCT DATA FLDR] preference. The load directory is defined using the [LOAD DATA FLDR] preference. The [ATTACHMENTS FLDR] must be specified so the load functions know where to write the report exceptions log to.
The extract directory is defined using the [EXTRCT DATA FLDR] preference. The load directory is defined using the [LOAD DATA FLDR] preference. The [ATTACHMENTS FLDR] must be specified so the load functions know where to write the report exceptions log to.
At line 25 changed one line
;:If the full path is not specified here, then the path used by the HL Application Directory will apply. The user who is running the LMTD must have Read/Write/Create access to this directory on the server.
If the full path is not specified here, then the path used by the HL Application Directory will apply. The user who is running the LMTD must have Read/Write/Create access to this directory on the server.
At line 28 changed one line
;:Launch the LMTD function specifying the appropriate parameters for the Table Data Loader as indicated below.
Launch the LMTD function specifying the appropriate parameters for the Table Data Loader as indicated below.
At line 31 changed one line
;:During the load process, all non-fatal exceptions as well as the number of insertions and updates (by table) are logged in the execution run logs. After the load process completes, a report is written to a text file indicating the number of records read, number of records bypassed, number of records processed, number of records that were bypassed because an identical one already existed in the table, and number of records updated/inserted by table. The report will display all non-fatal business exceptions encountered during the load with a record number indicating for which record the exception occurred. The report will also display the amount of time that was taken for the load process to complete.
During the load process, all non-fatal exceptions as well as the number of insertions and updates (by table) are logged in the execution run logs. After the load process completes, a report is written to a text file indicating the number of records read, number of records bypassed, number of records processed, number of records that were bypassed because an identical one already existed in the table, and number of records updated/inserted by table. The report will display all non-fatal business exceptions encountered during the load with a record number indicating for which record the exception occurred. The report will also display the amount of time that was taken for the load process to complete.
At line 33 changed one line
;:There are 2 tiers of exceptions that can be generated during the load process. The first tier involves extracting and building data from the source file and the second involves processing the extracted data. However, there will only be ONE exception for each failed load. Basically, if the record fails to build data correctly, the program will not bother loading it so you will never see 2 exceptions for a single failed record load.
There are 2 tiers of exceptions that can be generated during the load process. The first tier involves extracting and building data from the source file and the second involves processing the extracted data. However, there will only be ONE exception for each failed load. Basically, if the record fails to build data correctly, the program will not bother loading it so you will never see 2 exceptions for a single failed record load.
At line 35 changed one line
;:Exceptions generated while extracting and building data from the source file will indicate that the exception occurred while "reading data from file". Exceptions generated while processing the extracted data will indicate that the exception occurred while "loading data into the DB".
Exceptions generated while extracting and building data from the source file will indicate that the exception occurred while "reading data from file". Exceptions generated while processing the extracted data will indicate that the exception occurred while "loading data into the DB".
At line 37 changed one line
;:When a Null Pointer Exception (NPE) occurs during the load process, the entire stack trace to the NPE is captured and displayed as part of the exception message in the load report.
When a Null Pointer Exception (NPE) occurs during the load process, the entire stack trace to the NPE is captured and displayed as part of the exception message in the load report.
At line 39 changed one line
;:The report text file will be located in the directory which was specified in the [IMST] preference [LOAD DATA FLDR].
The report text file will be located in the directory which was specified in the [IMST] preference [LOAD DATA FLDR].
At line 42 changed one line
;:If there are no exceptions in the report, you should navigate to the table where the data was loaded and verify that the load was done correctly.
If there are no exceptions in the report, you should navigate to the table where the data was loaded and verify that the load was done correctly.
This page (revision-31) was last changed on 26-Nov-2021 10:22 by Kevin HiggsTop