title: How do I load millisecond accuracy dates with SQLLDR
body: <p>I am trying to load date fields that have six decimal places using <code>sqlldr</code>. For example I have a date:<br> <code>"2020-01-05-16.32.02.070000"</code> in my csv import file.</p>
  
  <p>In my control file for sqlldr I tried:   <code>LASTMODIFIED DATE "YYYY-MM-DD-HH24.MI.SS.FF6",</code></p>
  
  <p>But the sqlldr throws the error:   <code>ORA-01821: date format not recognized</code></p>
  
  <p>So I can change my format string to <code>LASTMODIFIED DATE "YYYY-MM-DD-HH24.MI.SS",</code></p>
  
  <p>The of course if fails to load because:</p>
  
  <pre><code>Record 43: Rejected - Error on table ORA_TIO_OWNER.REPORTER_STATUS, column LASTMODIFIED.
  ORA-01830: format picture ends before converting entire input string
  </code></pre>
  
  <p>I can exclude the sub second accuracy from my data, then it imports just fine, but obviously that is sub-optimal. How do I get <code>sqlldr</code> to accept these data strings?</p>
  
  <p>PS. I have checked with SQL Developer and see the target table is configured to have the same number of decimals.</p>
  
  <p><strong>Updated with loader control file</strong></p>
  
  <pre><code> load data
    2   infile 'REPORTER_JOURNAL.csv'
    3   into table ORA_TIO_OWNER.REPORTER_JOURNAL
    4   fields terminated by "," optionally enclosed by '"'
    5   ( CHRONO DATE "YYYY-MM-DD-HH24.MI.SS.FF", SERIAL INTEGER EXTERNAL, SERVERNAME CHAR, SERVERSERIAL INTEGER EXTERNAL, TEXT1 CHAR, TEXT10 CHAR, TEXT11 CHAR, TEXT12 CHAR, TEXT13 CHAR, TEXT14 CHAR, TEXT15 CHAR, TEXT16 CHAR, TEXT2 CHAR, TEXT3 CHAR, TEXT4 CHAR, TEXT5 CHAR, TEXT6 CHAR, TEXT7 CHAR, TEXT8 CHAR, TEXT9 CHAR, USERID INTEGER EXTERNAL )
  </code></pre>
  
  <p>That is non-functioning and giving <code>ORA-01821: date format not recognized</code> If I hack off the <code>.FF</code> it will load the cut down version of dates.</p>
  
  <p>P.S. Don't worry about the differing table names. I am migrating a whole pile of data from DB2 to Oracle and there are many tables, but the problem is the same across them all</p>