...
NAME | VALUE | TYPE | OPTIONAL | DESCRIPTION |
|---|---|---|---|---|
MOVE_INVALID_FILE | true|false | String | Yes | Defines whether the engine should move files if they do not meet the pattern name criteria |
MAX_FILES_TO_LOAD | integer bigger than 0 | Integer | Yes | Defines the number of files that are processed in a single engine iteration. If not present, the default value is 50 |
BATCH_SIZE | integer bigger than 0 | Integer | Yes | Number of SQL statements size used to load in batch. If not present, the default value is 100 |
DB_SYS_PACKAGE_NAME | SYS/CORE_SYS | String | Yes (Mandatory if CORE_SYS package is used) | Defines the name of the sys package to be used in SQL-statements Default SYS (if this parameter is not defined) |
| CHARACTER_ENCODING | <Valid character encoding> | String | Yes | Defines the character encoding to be used while importing the files. If this parameter exists, the encoding specified in this parameter will be used to read the file. Otherwise the default encoding will be used. |
5 MONITORING
5.1 File Generator
If the File Processor engine cannot generate the file due to an exception, it will insert an entry into EXCEPTION_LOG table. The ID from EXCEPTION_LOG.EXCEPTION_STACK_TRACE_ID can be used to find the corresponding entry from EXCEPTION_STACK_TRACE, which contains the stack trace of the exception.
| Code Block | ||
|---|---|---|
| ||
select * from EXCEPTION_LOG where TABLE_NAME = 'CDR_FILE_PROCESSOR' and SOURCE_KEY = '<CDR_FILE_PROCESSOR.NAME for corresponding CDR_FILE_PROCESSOR entry>' order by id desc; |
5.1 File Loader
If the File Processor engine cannot load the file due to an exception or due to errors while parsing the file, it will insert an entry into LOAD_ERRORS table.
File Processor engine inserts an entry into CDR_FILE_PROCESSOR_LOG table upon successful loading of the file.