title: Solution to run parallel runs using SQLLDR/SQL Loader
body: <p>I have a situation !</p>
  
  <p>10 Modules take about close to 2 hours each to process that includes loading data from external files, 20 hours of run is unreasonable and they must run sequentially because of the way it is coded. Each module has a same set of scripts but deals with different set of data.</p>
  
  <p>Components :</p>
  
  <p>a) Tables : TempTableA, FinalTableA, TempTableB, FinalTableB;
     Each of these tables are uniquely represented by a module Key.
     The module key is defaulted to '-99'
  b) External File (FileA,FileB) does not have a module key but only has a data.
  c) The script knows about the module key for that module.
  d) .ctr file</p>
  
  <p>The code inside each module more or less has following steps :</p>
  
  <p>Truncate Table TempTableA
  sqlldr $USER/$PASSWRD@$PRD_SID control=ctr/fileA.ctr log=log/fileA.log bad=log/fileA.bad skip=1 rows=10000 silent=FEEDBACK</p>
  
  <p>update table TempTableA set moduleKey = $moduleKey where moduleKey = '-99'
  insert into FinalTableA as select * from TempTableA;</p>
  
  <p>Now I cant run these modules in parallel because of these temporary tables being truncated.</p>
  
  <p>Is there a better solution ?</p>
  
  <p>I am aware of the external tables , but this isnt about using external tables it is about how I get around with the problem of using shared temporary tables. And this may not about running parallel loads either.</p>