Oracle Data Loader On Demand Guide > Troubleshooting Oracle Data Loader On Demand >

Log Files for Oracle Data Loader On Demand

Oracle Data Loader On Demand creates a directory named manifest while it is running. The files it places in that directory are temporary and are used only by Oracle Data Loader On Demand while the application is running. These files are not normally used for troubleshooting.

Two different log files are generated as part of your data load:

• Client log file. This file is specified as part of the command-line or the properties file, by specifying its path using the following parameter: -clientlogfiledir. The client log file captures error messages related to the client connecting to the server. No error messages are generated for processing of data. The amount of information in this log level can be controlled by the following parameter: -clientloglevel. The naming convention for the log file is a concatenation of the application name (OracleDataLoaderOnDemand) and a date timestamp, for example:

  OracleDataLoaderOnDemand_20090928.154115.log

  If you set -clientloglevel to all or detailed then the command-line parameters are copied to the log file. For a sample log file, see Sample Log File.

• User log file. This file is attached to the request record in Oracle CRM On Demand. It is a comma-separated value (CSV) text file and contains details about failed records. The user can open the log file in a text editor or a CSV editor. This file can be accessed during the processing of data loads by navigating to the detail page of the request record in Oracle CRM On Demand. You can control the amount of information in this log file by using the following parameter:
  - importloglevel.