Importing Data from Oracle Cloud Infrastructure Object Storage Classic

Import data stored in Oracle Cloud Infrastructure Object Storage Classic to .

To import data from Oracle Cloud Infrastructure Object Storage Classic to the NoSQL database that comes with the service you need access to the following information:
  • The name of the object that contains the data in .

  • A NoSQL link. This link specifies the table where to store the data as well as the credentials to access the database. For more information, see Use Links to Access Oracle NoSQL Database Cloud.

  1. Go to your IoT application.
  2. From the main menu, select Analytics, and then select Import Data.
  3. If this is your first import job, click Create Data Import Job, otherwise click Create Add icon located next to the Search`field.
  4. Enter a name to identify your import job.
  5. (Optional) Enter a description for your import job.
  6. Click Create.
  7. In the Object field located in the Source section, enter the name of an object located in the iota-user-uploads-container in Oracle Storage Cloud Service.
  8. From the NoSQL Link list located in the Target section, select the NoSQL link to use when importing the data to .
  9. From the Data Format Profile list, select a CVS file format.
    Available options are:
    • Default: standard comma separated values format. Allows empty lines.
    • MySQL: tab-delimited format that uses an LF character as the line separator.
    • Excel: format used by Microsoft Excel, the value delimiter depends on the locale of your system.
    • RFC4180: comma separated value format as defined by the RFC41870 specification.
    • TDF: tab delimited format.
    For more information about these options, see org.apache.commons.csv.CSVFormat.
  10. From the Header list, select No header in first record if your CSV file doesn’t contain headers, or Header is present in first record if your CSV file contains headers.
  11. Click the Start button located in the first section of this page.
Your import job starts, the status of your job changes to running and the Import Progress bar shows the percentage of the import job that was completed. When the job finishes, the status changes to completed if the import job was successful.
If your import job fails after importing a number of records, you can run the job again skipping the bytes that correspond to those records. To do this, set the Offset field to the number of processed bytes that appears in your failed message.