How do I import using the external data loader client?

This topic describes how to import using the External Data Loader Client tool.

You can use the tool to split a source file into multiple smaller files for upload and then import. This lets you import large files that exceed the import size limits. You can split a CSV file in one of two ways:

Independently - the specified CSV file can be split based on selected parameters and no import is performed
As part of import - the specified CSV file is split and then each of the resulting files is uploaded and then imported

The following steps are involved in using the tool:

Submit Import Jobs
Review Status of Import Jobs
Retrieve Log Files

Submit Import Jobs

The submit operation, takes the source single CSV file, splits the file into smaller files (if necessary), uploads those files to the Webcenter Content Repository and then imports the files. When executing the client from the command line, you must provide the URL of the pod to run the import, the user credentials for authentication, the import object name, the import map number, and the import source file name.

> java -jar oscdataloader.jar submit -target-url https://mypod.oracle.com -username importuser -input-file Account.csv -import-name "Account Import" -object Account -mapping-number 123565

If multiple import activities are created due to splitting of files, then import activity name values are the same. The file name values are suffixed with a count value. For example, if the source file Account.csv is split into two files, then file name values are called Account_1.csv and Account_2.csv.

Note: If the target isn't open through public internet, it wouldn't be accessible through public internet.

You can retrieve the list of imports that have recently run on a server using the listimports command. For example,

> java -jar oscdataloader.jar listimports -target-url https://mypod.oracle.com -username importuser

lists the imports as a table in the command window. An example of the output would contain the following information:

Identifier	Name	Object	Attachment Object	Start Time	End Time	Status	Submitted By	Activate
0123456789012345	Account Import 20170410	Account	N/A	20170410 14:56T05:00	20170410 16:56T05:00	Completed	John.Doe	Yes
7878787878787878	Opportunity Sync	Opportunity	N/A	20170411 17:06T05:00	20170411 20:06T05:00	Completed with errors	John.Doe	Yes

Note: You should place the import source files in local folders while using EDLC. Remotely mounted files might cause performance issues.

Review Status of Import Jobs

To get the status of an import activity, enter the identifier value of the import on the command line. For example:> java -jar oscdataloader.jar getlogs -target-url https://mypod.oracle.com -username importuser -log-type Exception -import-activity 012345678912345

This command displays the detailed status of the matching import request (if no matching request is found, then an error is displayed). An example of the output contains the following information:

Object	Attachment Object	Status	Start Time	End Time	Number of File Splits	Records Read	Successfully Loaded	Errors Reported	Warnings Reported
Account	N/A	Completed	20170410 14:56T05:00	20170410 17:36T05:00	2	50,000	49,950	50	0

Retrieve Log Files

You can get the log files generated by an import activity using the getlogs command. For example,

> java -jar oscdataloader.jar getlogs -target-url https://mypod.oracle.com -username importuser -log-type Exception -import-activity  012345678912345

Log files retrieved by the getlogs command are stored in the importlogs folder by default. Log file of the External Data Loader Client is stored in the oscdataloaderlogs folder.