Troubleshooting Oracle Data Loader On Demand

This chapter provides troubleshooting information for Oracle Data Loader On Demand. It includes the following topics:

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.

Troubleshooting Oracle Data Loader On Demand

The following table provides guidelines for helping you to resolve problems using Oracle Data Loader On Demand.

Table Troubleshooting Oracle Data Loader On Demand

Symptom	Cause	Solution
Authentication Error	Your account does not have the right privileges.	Check the following conditions, and resolve them if necessary: Make sure that your login name and password are specified correctly. Make sure your account has the Admin Import privilege. Make sure your account has the Enable Web Services Access privilege and that you are impersonating an administrator. Make sure you are not using SSO credentials. Oracle Data Loader On Demand does not support SSO authentication.
Import fails	The import process cannot find the owner of a record.	Check the following conditions, and resolve them if necessary: Make sure that the owner record exists in Oracle CRM On Demand. Make sure that the data file contains the user sign-in ID for owners.
Picklist not populated	Picklist values are not found.	Check the following conditions, and resolve them if necessary: Make sure the picklist values exist in Oracle CRM On Demand. Make sure the picklist values match exactly the values in Oracle CRM On Demand. Check the case of the picklist values. Picklist values are case sensitive. Make sure picklist values in Oracle CRM On Demand have neither leading nor trailing blank spaces. Check if cascading picklists rules are affecting the picklist values available.
Records not imported	The import process cannot find your associated records.	Check the following conditions, and resolve them if necessary: Make sure that associated records exist in Oracle CRM On Demand before the import process starts. Make sure that associated record values match exactly the value in Oracle CRM On Demand. Check all entries for proper case. Entries are case sensitive. Make sure the associated record names in Oracle CRM On Demand have neither leading nor trailing blank spaces.
The downloaded ZIP file for Oracle Data Loader On Demand is unusable	Corrupted or damaged ZIP file.	Either restart your browser, or try a different supported browser such as FireFox. If you are using Internet Explorer, change the following setting: Internet Options, Advanced tab, clear the check box for Use HTTP 1.1.
Validation failed error	The operating system cannot create a required file.	Check the following conditions, and resolve them if necessary: Do not use forward slashes (/) in path names. For example, use `d:\temp` instead of `d:/temp`. Use either the full path with backslashes (\) or put the CSV and map files in the same folder as the JAR file. If you have the CSV and map files in a subdirectory, then include the name of subdirectory as well. For example, if your JAR file is in `d:\dl` and your data and map files are in a subdirectory called data, then specify the path to be `data\myFile.csv` or `d:\dl\data\myFile.csv`.
You receive the following message when submitting an import job: "Processing this request will exceed your current storage allotment, therefore your request cannot be processed. Please reduce the number of records and try again or contact your Company Administrator."	Your storage allotment is almost full.	To reduce the allotment usage you can delete data you no longer need. To purchase additional capacity or licenses, contact your sales representative.
You receive the following message: "String index out of range: -1"	A required field is blank, possibly the first field in a record.	Make sure all required fields have valid data. If there legitimately is no data for a field, enter a blank by using a pair of quotation marks.