Bulk Load Logging

There are four types of log files created for each data input file. The bulk load process logs the various stages of execution. A unique ID is generated for each load.

The log files for the bulk load will be created in the same directory where the bulk load files are placed (the directory created in step 2 in Configuring for the Bulk Load).

The following log files are generated for the particular load process:
Log File
This file is used by Oracle to log information about the process used to create the external table. The log file name has the following format: Log_<EntityName>_<LoadId>.log (for example, Log_Item_001.log) This file contains the logs generated by the ACCESS driver and is created by the Oracle server.
Bad File
This file contains records which cannot be loaded because of errors. For example, a record was written to the bad file because a field in the datafile could not be converted to the datatype of a column in the external table. The bad file name has the following format: Bad_<EntityName>_<LoadId>.bad (for example,Bad_Item_001.bad). This file will only be created if any bad records are encountered. This file contains bad records as detected by the ACCESS driver as well as the insert process and is created by the Oracle server.
Discard File
This file contains records that fail the condition in the LOAD WHEN clause of the statement used to create the external table. This file will only be created if any records that fail the LOAD WHEN condition. The discard file name has the following format: Discard_<EntityName>_<LoadId>.discard (For example, Bad_Item_001.bad).
Stored Procedure logs
This file is created by the procedures which copy the records from the external table to the actual table. This file will display any errors encountered during the copying process. It also displays the current status of the load. The file name has the following format: Log_SP_<EntityName>_<LoadId>.log. The following is an example of the contents of this log file:
05-Jan-2016 17:09:50.430000000 - Load has started with commit frequency 10
05-Jan-2016 17:10:05.510000000 - Committed Inventory items after processing 2000(1-2000) records
05-Jan-2016 17:10:11.698000000 - Committed Inventory items after processing 2000(2001-4000) records
05-Jan-2016 17:10:12.712000000 - Committed Inventory items after processing 2000(4001-6000) records
05-Jan-2016 17:10:38.226000000 - Committed Inventory items after processing 2000(6001-8000) records
05-Jan-2016 17:10:39.492000000 - Committed Inventory items after processing 2000(8001-10000) records
…
…
… (truncated for brevity)
…
…
05-Jan-2016 17:13:19.685000000 - Committed Inventory items after processing 1156(102001-103156) records
05-Jan-2016 17:13:19.686000000 - Completed load of Inventory items after loading 103156 records out of 103156 records.
05-Jan-2016 17:13:19.688000000 - Load has ended